warpdotdev/명세-주도-구현

중요한 기능을 구현하기 전에 PRODUCT.md를 작성하고, 필요시 TECH.md를 작성하여 명세를 먼저 정의하는 워크플로우를 제공합니다. 구현이 진행됨에 따라 두 명세를 업데이트하며, 에이전트 주도 개발이나 제품 및 기술 명세를 소스 제어에 포함하려는 경우에 사용합니다.

명세-주도-구현란 무엇인가요?

이 스킬은 명세 우선(spec-first) 워크플로우를 통해 대규모 기능 개발을 체계적으로 진행하도록 돕습니다. 개발자는 PRODUCT.md에 제품 요구사항과 사용자 스토리를, TECH.md에 기술 설계와 아키텍처 결정을 문서화하여 구현 전에 명확한 방향을 설정합니다. 이 스킬은 Claude Code, Cursor, Codex와 같은 AI 에이전트 플랫폼에서 사용할 수 있으며, 구현 과정에서 명세가 지속적으로 업데이트되도록 보장합니다. 주요 장점으로는 요구사항과 구현 간의 불일치를 줄이고, 코드 리뷰 및 협업을 위한 명확한 기준점을 제공하며, 모든 결정 사항을 소스 제어에 기록하여 프로젝트 히스토리를 투명하게 유지합니다.

지원 대상~Claude Code~Codex CLI~Cursor

Part ofAgent Workflows

npx skills add https://github.com/warpdotdev/common-skills/tree/main/skills/spec-driven-implementation

Installed? Explore more 생산성 & 협업 skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →

원본 보기→모든 스킬 둘러보기

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

ChatGPT Claude Gemini Grok Perplexity DeepSeek

문서

명세-주도-구현은(는) 무엇을 하나요?

Individual skills in this repo

This repo contains 16 individual skills — each has its own dedicated page.

warpdotdev/brandalf

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.

warpdotdev/check-impl-against-spec

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.

warpdotdev/council

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.

warpdotdev/create-pr

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.

warpdotdev/diagnose-ci-failures

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.

warpdotdev/fix-errors

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.

warpdotdev/implement-specs

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.

warpdotdev/pr-walkthrough

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.

warpdotdev/reproduce-bug-report

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.

warpdotdev/resolve-merge-conflicts

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.

warpdotdev/respond-to-pr-comments-in-blocklist

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.

warpdotdev/review-pr

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.

warpdotdev/update-skill

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.

warpdotdev/validate-changes-match-specs

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.

warpdotdev/write-product-spec

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.

warpdotdev/write-tech-spec

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.