spec-driven-implementation skill (Warp): write specs first, then build from them

Warp's skill that makes your agent write specs first for big features, then build from them and keep the specs current.

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

spec-driven-implementation is the workflow skill of a set of four. It helps your agent decide whether a feature needs specs at all, then calls write-product-spec for PRODUCT.md, write-tech-spec for TECH.md when warranted, and implement-specs to build once the specs are approved. Specs live under specs/<linear-ticket-number>/.

If no Linear issue exists, SKILL.md tells the agent to create one first with the Linear MCP tools (list_teams, list_issue_labels, save_issue). Install all four skills together; the install box above does this. The text is written for Warp.

Good for

Engineers starting a feature of roughly 1,000+ lines or with unclear behavior
Teams that want PRODUCT.md and TECH.md reviewed in the same PR as the code
Agent users who get better results from clearer written input

Install spec-driven-implementation

Claude Code

Copy this prompt.

Install the spec-driven-implementation skill in Claude Code. Run this command:

npx skills@latest add warpdotdev/common-skills --skill spec-driven-implementation --skill write-product-spec --skill write-tech-spec --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.

Warp's README documents installing one skill with the skills CLI. This skill tells the agent to use write-product-spec, write-tech-spec and implement-specs, so install all four together.

From the project README. Source.

What's in the skill

When it loads

Drive a spec-first workflow for substantial features by writing PRODUCT.md before implementation, writing TECH.md when warranted, and keeping both specs updated as implementation evolves. Use when starting a significant feature, planning agent-driven implementation, or when the user wants product and tech specs checked into source control.

Sections in SKILL.md

Overview
When specs are required
Workflow
1. Decide whether the feature needs specs
2. Write the product spec first
3. Write the tech spec when warranted
4. Implement approved specs
5. Keep specs current during implementation
6. Verify behavior against the spec
Best Practices
Related Skills

Key facts

Author: Warp (warpdotdev/common-skills repo)
Installs on skills.sh: 28,812 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

Size, ambiguity and risk; skip for small local fixes
Try: “We are adding offline sync. Use spec-driven-implementation to plan it.”
Read · 1. Decide if specs are needed
Uses list_teams, list_issue_labels and save_issue if none exists
SKILL.md says to create the issue before writing specs and to ask you when the team or labels are not obvious.
Write · Create a Linear issue
Calls write-product-spec for PRODUCT.md first
Write · 2. Write the product spec
Calls write-tech-spec for substantial or ambiguous work
Write · 3. Write the tech spec when warranted
Calls implement-specs; specs and code can share one PR
For large features it may offer PROJECT_LOG.md and DECISIONS.md as optional aids.
Runs code · 4. Implement approved specs
Update PRODUCT.md and TECH.md when the shipped design changes
Write · 5. Keep specs current
Tests, integration tests, walkthroughs or screenshots
Runs code · 6. Verify against the specs

From the official docs

Permissions

Medium risk

It writes specs and code in your repo and may create a Linear issue. Work on a branch and check the issue it files.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

It can create a Linear issue
SKILL.md says to create an issue if a relevant one does not exist. It asks you when the team or labels are unclear; check what it files. github.com
It edits code through the sibling skills
The build step runs implement-specs, which changes code, specs and tests. Use a branch and read the diff. github.com

Technical details

Talks to	Linear (through the Linear MCP server, if you have it connected)
Scopes	Writes specs/<ticket>/PRODUCT.md and TECH.md and implementation code in your repo Creates a Linear issue through the Linear MCP tools if none exists

Questions

What does the spec-driven-implementation skill do?

It runs a spec-first workflow for substantial features. Your agent decides if specs are worth it, writes PRODUCT.md, writes TECH.md if needed, builds from the approved specs and keeps them updated.

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

Use the install box at the top of this page. It installs spec-driven-implementation together with write-product-spec, write-tech-spec and implement-specs, because the workflow tells the agent to use all three.

Does it need Linear?

Specs go under specs/<linear-ticket-number>/ and SKILL.md says to create a Linear issue with the Linear MCP tools if none exists. The sibling skills also accept a GitHub issue id or a short feature name, so a different ticket system works if you say so.

When should I not use it?

SKILL.md says specs are often unnecessary for small local bug fixes, straightforward refactors and narrow UI tweaks. It asks the agent to be pragmatic.

Is it safe?

It writes spec files and code in your repo and, if no issue exists, tells the agent to create a Linear issue in your workspace. Check which team and labels it picks, and work on a branch.

Is it only for Warp?

Its text says Warp and uses Linear ticket ids in examples. The workflow itself (specs first, then code, with specs kept current) is not tied to the Warp app, and the repo README says shared skills may still contain Warp-specific wording. It also names an ask_user_question tool, which your agent may not have.

Information

updated Nov 2, 2026

Repository: warpdotdev/common-skills
Folder: .agents/skills/spec-driven-implementation

warpdotdev/common-skills skills.sh

Sources

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

Show all 4

common-skills README · github.com
spec-driven-implementation SKILL.md · github.com
skills.sh listing · skills.sh
SKILL.md · github.com