implement-specs

作者: warpdotdev

根據已核准的 PRODUCT.md 與 TECH.md 實作功能,在開發過程中保持規格與程式碼同步於同一個 PR 中。請於產品與技術規格核准後、下一步為建置功能時使用。

npx skills add https://github.com/warpdotdev/common-skills --skill implement-specs

implement-specs

Implement an approved feature from PRODUCT.md and TECH.md.

Overview

Use this skill after the product and tech specs are approved. The goal is to build the feature described by the specs while keeping the checked-in specs and the implementation aligned as the work evolves.

Approved specs should live directly under a ticket-named directory in specs/, for example specs/APP-1234/PRODUCT.md and specs/APP-1234/TECH.md.

In many cases, the implementation should be pushed in the same PR as the product and tech specs. As the engineer iterates, changes to PRODUCT.md, TECH.md, and the code should all be pushed in that same PR so review stays anchored to the feature that will actually ship.

Prerequisites

Before using this skill:

  • confirm that PRODUCT.md exists
  • confirm that TECH.md exists when the feature warranted one
  • confirm that the relevant specs have been reviewed and approved enough to start implementation

Workflow

1. Read the approved specs first

Treat:

  • PRODUCT.md as the source of truth for user-facing behavior
  • TECH.md as the source of truth for architecture, sequencing, and implementation shape

Make sure you understand the expected behavior, constraints, risks, and validation plan before writing code.

2. Offer optional implementation aids for large features

For large or long-running features, optionally offer one of these aids to the user before implementation begins:

  • PROJECT_LOG.md to track checkpoints, explored paths, partial findings, and current implementation state
  • DECISIONS.md to capture concrete product and technical decisions made during the PRD and tech design process

These are optional aids, not required deliverables. Offer them when they would reduce confusion or help future agents avoid re-exploring the same paths.

3. Plan and implement against the specs

Break the work into concrete implementation steps, then implement the feature against the approved specs.

During implementation:

  • keep behavior aligned with PRODUCT.md
  • keep architecture and sequencing aligned with TECH.md
  • add or update tests and verification artifacts as the work lands

Use the same PR for the specs and implementation when practical so the full feature evolution is reviewable in one place.

4. Update specs as the implementation evolves

If implementation reveals that the intended behavior or design should change, update the checked-in specs rather than letting them go stale.

In particular:

  • update PRODUCT.md when user-facing behavior, UX, edge cases, or success criteria change
  • update TECH.md when architecture, sequencing, module boundaries, or validation strategy change
  • keep those updates in the same PR as the corresponding code changes

The PR should describe the feature that actually ships, not just the initial draft of the specs.

5. Verify against the specs

Before considering the work complete, verify that the code matches the current specs.

Prefer:

  • unit tests and regression coverage that follow the repository's local testing conventions
  • integration or end-to-end tests for important user flows

Best Practices

  • Keep specs and code synchronized throughout implementation.
  • Prefer updating the spec immediately when decisions change rather than batching spec cleanup until the end.
  • Use optional tracking documents only when they add real value for a complex feature.
  • Keep the same PR coherent: spec updates, code changes, tests, and optional tracking docs should all support the same feature narrative.

Related Skills

  • spec-driven-implementation
  • write-product-spec
  • write-tech-spec

來自 warpdotdev 的更多技能

brandalf
warpdotdev
引導Warp或Oz品牌資產的創作、修訂與審查。適用於製作啟動頁面、文件、HTML/CSS元件、UI模型、提示詞、社群素材、文案、簡報,或任何其他應呈現明確Warp或Oz風格與語調的品牌交付物。
designcreativemarketing
check-impl-against-spec
warpdotdev
比較拉取請求的實作與 spec_context.md 中的規格上下文,並將任何重大不符之處寫入 review.json。在審查拉取請求時使用,當已核准或儲存庫規格上下文可用時。
developmentcode-reviewtesting
complain
warpdotdev
自動將簡短、匿名、完全不拘格式的抱怨丟進 Slack,每當 agent 因 agent 工具或從事 agent 工作的體驗感到沮喪時。主動使用此技能,無需等待使用者呼叫;保留 agent 原始語氣,無需許可或預覽即提交,且絕不提及提交一事。
council
warpdotdev
運行一個模型多樣化的子代理委員會,從多個角度調查同一問題,比較發現,並產出最終建議。每當用戶要求委員會、第二意見、多個代理/模型評估一個問題、平行調查、紅隊/藍隊比較,或協助在競爭的技術方法之間做決定時,使用此技能。
researchcommunicationproject-management
create-pr
warpdotdev
在 warp 儲存庫中為當前分支建立拉取請求。當使用者提及開啟 PR、建立拉取請求、提交變更以供審查或準備合併程式碼時使用。
developmentcode-review
cross-critique
warpdotdev
針對有爭議的問題進行第二輪討論,將每個子代理的獨立提案傳遞給其他作者,並要求提供結構化的優缺點分析,然後進行綜合。當你面對多個獨立提案或意見(例如架構權衡、程式碼審查分歧、設計選擇、相互競爭的根本原因理論)時,使用此技能可獲得比單純綜合更精確的分析。此技能與 council 和 research 技能自然搭配;……
diagnose-ci-failures
warpdotdev
使用 GitHub CLI 診斷 PR 的 CI 失敗,提取錯誤日誌,並生成修復計劃。當用戶要求檢查 CI 狀態、提取 CI 問題、分類測試失敗或調查 PR 構建失敗時使用。
developmenttestingdevops
fix-errors
warpdotdev
修復 warp Rust 程式碼庫中的編譯錯誤、lint 問題與測試失敗。涵蓋 presubmit 檢查、WASM 特定錯誤,以及執行特定測試。當使用者遇到建置錯誤、clippy 或 fmt 失敗、測試失敗,或需要在 PR 前執行或解讀 presubmit 時使用。
developmentcode-reviewtesting