implement-specs skill (Warp): build a feature from approved PRODUCT.md and TECH.md

Warp's skill that makes your agent build a feature from approved PRODUCT.md and TECH.md specs and keep the specs and code in sync.

Installs: 28.6K; on skills.sh
Stars: 644; on GitHub
Updated: Oct 2026; last repo commit

implement-specs loads after your product and tech specs are approved and the next step is building. Your agent first checks that PRODUCT.md exists, and TECH.md if the feature needed one, then reads both. PRODUCT.md is the source of truth for behavior and TECH.md for architecture and sequencing.

It then plans the work, implements it, updates the specs when the design changes, and verifies the code against the specs with tests. It bundles no scripts and expects specs under a ticket-named folder such as specs/APP-1234/.

Good for

Engineers who have approved specs and want an agent to build against them
Teams that keep specs in the repo and want them updated in the same PR
Reviewers who want specs, code and tests to tell one story

Install implement-specs

Claude Code

Copy this prompt.

Install the implement-specs skill in Claude Code. Run this command:

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

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

From its listing on skills.sh. Source.

What's in the skill

When it loads

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.

Sections in SKILL.md

Overview
Prerequisites
Workflow
1. Read the approved specs first
2. Offer optional implementation aids for large features
3. Plan and implement against the specs
4. Update specs as the implementation evolves
5. Verify against the specs
Best Practices
Related Skills

Key facts

Author: Warp (warpdotdev/common-skills repo)
Installs on skills.sh: 28,572 as of 2026-11-02
GitHub stars: 644 for the whole common-skills repo, 2026-11-02
License: MIT (from GitHub repo data)
Last repo commit: 2026-10-28
Files: 1 file: SKILL.md only
Part of: Warp's common-skills repo, shared skills the README says may still contain Warp-specific wording

What it includes

PRODUCT.md exists, TECH.md if needed, specs approved
Try: “The specs in specs/APP-1234 are approved. Implement them.”
Files · Prerequisites check
PRODUCT.md for behavior, TECH.md for architecture
Files · Read the approved specs first
Offers PROJECT_LOG.md and DECISIONS.md
For large or long-running work the agent may offer a project log of checkpoints and explored paths, or a decisions file. Both are optional.
Write · Optional aids for large features
Concrete steps; add tests as the work lands
Runs code · Plan and implement against the specs
Edit PRODUCT.md or TECH.md in the same PR when design changes
Write · Update specs as work evolves
Unit, regression and end-to-end tests for key flows
Runs code · Verify against the specs

From the official docs

Questions

What does the implement-specs skill do?

It has your agent build a feature from approved PRODUCT.md and TECH.md files and update those specs if the design changes. The specs and the code stay in the same PR.

How do I install it in Claude Code, the Claude app or Codex?

Use the install box at the top of this page. It works with specs written by the write-product-spec and write-tech-spec skills, which are separate installs.

Do I need the other spec skills?

Not to run it. SKILL.md lists spec-driven-implementation, write-product-spec and write-tech-spec as related skills, and expects PRODUCT.md and TECH.md to exist, however you wrote them.

Does it need an API key?

No key appears in SKILL.md. It bundles no scripts.

Is it safe?

It edits code, specs and tests in your repo and may run your test commands. SKILL.md talks about pushing spec and code changes in the same PR, so work on a branch and read the diff before anything is pushed.

Where should the specs live?

SKILL.md says approved specs should sit directly under a ticket-named folder in specs/, for example specs/APP-1234/PRODUCT.md.

Information

updated Nov 2, 2026

Repository: warpdotdev/common-skills
Folder: .agents/skills/implement-specs

warpdotdev/common-skills skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 3

implement-specs SKILL.md · github.com
common-skills README · github.com
skills.sh listing · skills.sh