spec-driven-implementation は何をしますか？
重要な機能開発において、仕様駆動型ワークフローを推進します。実装前にPRODUCT.mdを作成し、必要に応じてTECH.mdを作成し、実装の進行に合わせて両方の仕様書を最新の状態に保ちます。大規模な機能の開始、エージェント駆動型実装の計画、または製品仕様と技術仕様をソース管理にチェックインしたい場合に使用します。
仕様駆動型ワークフローを推進します。重要な機能開発では、実装前にPRODUCT.mdを作成し、必要に応じてTECH.mdを作成し、実装の進行に合わせて両方の仕様書を最新の状態に保ちます。大規模な機能の開始、エージェント駆動型実装の計画、または製品仕様と技術仕様をソース管理にチェックインしたい場合に使用します。
このスキルは、大規模な機能開発において、実装前に製品仕様書（PRODUCT.md）を作成し、必要に応じて技術仕様書（TECH.md）を作成する、仕様駆動型のワークフローを実現します。これにより、開発プロセス全体を通じて明確な方向性を維持し、エージェント駆動型の実装を効率的に進めることができます。製品仕様と技術仕様は実装の進行に合わせて常に最新の状態に保たれ、ソース管理にチェックインされるため、チーム全体で共有可能です。このスキルは、Claude CodeやCursor、CodexなどのAIエージェントと連携して動作し、開発者が仕様から実装までの一貫したプロセスを管理するのに役立ちます。
npx skills add https://github.com/warpdotdev/common-skills/tree/main/skills/spec-driven-implementationInstalled? Explore more 生産性＆コラボレーション skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →
重要な機能開発において、仕様駆動型ワークフローを推進します。実装前にPRODUCT.mdを作成し、必要に応じてTECH.mdを作成し、実装の進行に合わせて両方の仕様書を最新の状態に保ちます。大規模な機能の開始、エージェント駆動型実装の計画、または製品仕様と技術仕様をソース管理にチェックインしたい場合に使用します。
This repo contains 16 individual skills — each has its own dedicated page.
Guides creation, revision, and review of Warp- or Oz-branded assets. Use when working on launch pages, docs, HTML/CSS components, UI mockups, prompts, social assets, copy, presentations, or any other branded deliverable that should look and sound unmistakably Warp or Oz.
Compare a pull request's implementation against spec context in spec_context.md and feed any material mismatches into review.json. Use during PR review when approved or repository spec context is available.
Run a model-diverse subagent council to investigate the same problem from multiple perspectives, compare findings, and produce a final recommendation. Use this skill whenever the user asks for a council, second opinions, multiple agents/models to evaluate one question, parallel investigation, red-team/blue-team comparison, or help deciding between competing technical approaches.
Create a pull request in the warp repository for the current branch. Use when the user mentions opening a PR, creating a pull request, submitting changes for review, or preparing code for merge.
Diagnose CI failures for a PR using the GitHub CLI, extract error logs, and generate a plan to fix them. Use when the user asks to check CI status, pull CI issues, triage test failures, or investigate PR build failures.
Fix compilation errors, linting issues, and test failures in the warp Rust codebase. Covers presubmit checks, WASM-specific errors, and running specific tests. Use when the user hits build errors, clippy or fmt failures, test failures, or needs to run or interpret presubmit before a PR.
Implement an approved feature from PRODUCT.md and TECH.md, keeping specs and code aligned in the same PR as implementation evolves. Use after the product and tech specs are approved and the next step is building the feature.
Generate a static interactive D3 walkthrough of a pull request. Use when the user wants a zoomable PR map, graph/canvas PR orientation, or alternate visualization of PR system components, data flow, code dependencies, and user actions.
Launch Oz cloud agents with computer use to reproduce UI-focused bug reports, capture visual evidence, and report reproduction findings. Use when investigating a specific interactive or visual bug from an issue, ticket, support report, or prompt.
Resolve Git merge conflicts by extracting only unresolved paths, conflict hunks, and compact diffs instead of loading whole files into context. Use when a merge, rebase, cherry-pick, or stash pop stops on conflicts, when `git status` shows unmerged paths, or when files contain conflict markers.
Walk users through PR review comments, fetching and displaying them first when needed, collect per-comment response decisions, apply requested fixes, and preview GitHub replies and resolutions before posting. Use when responding to PR review comments on the current branch.
Review a pull request diff and write structured feedback to review.json for the workflow to publish. Use when reviewing a checked-out PR from local artifacts like pr_diff.txt and pr_description.txt and producing machine-readable review output instead of posting directly to GitHub.
Create or update skills by generating, editing, or refining SKILL.md files in this repository. Use when authoring new skills or revising the structure, frontmatter, or guidance for existing ones.
Validate that a branch or pull request implementation matches introduced product, technical, security, and related specs. Use when reviewing or finishing a spec-driven change and resolving mismatches between checked-in specs and implementation.
Write a PRODUCT.md spec for a significant user-facing feature in Warp, focused on detailed behavior and validation. Use when the user asks for a product spec, desired behavior doc, or PRD, wants to define feature behavior before implementation, or when the feature is substantial or behaviorally ambiguous enough that a written spec would improve implementation or review.
Write a TECH.md spec for a significant Warp feature after researching the current codebase and implementation constraints. Use when the user asks for a technical spec, implementation plan, or architecture doc tied to a product spec.
Gemini CLI one-shot prompts, summaries, generation, skills, hooks, MCP, or Gemma routing.
Fetch GitHub issues, select candidates, spawn background fix agents, open PRs, and optionally process PR review comments.
Create, edit, audit, tidy, validate, or restructure AgentSkills and SKILL.md files.
Search, install, update, sync, or publish agent skills with the ClawHub CLI and registry.
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
List, configure, authenticate, call, and inspect MCP servers/tools with mcporter over HTTP or stdio.