Skills warpdotdev common-skills Warp spec workflow
spec-driven-implementation
- Use it when:
- Starting a large, risky or ambiguous feature that an agent will build, such as one around 1k+ lines.
- It does:
- Decides whether specs are worth it, files a Linear issue if there's none, then has the agent write the product spec, the tech spec when warranted, and the code.
- You get:
- PRODUCT.md and TECH.md under specs/<ticket>/, usually in the same PR as the code, kept current so they describe what ships.
- Needs:
- The Linear MCP server, and the write-product-spec, write-tech-spec and implement-specs skills.
Skill 1 of 5 in the Warp spec workflow bundle, before write-product-spec.
Only works inside its bundle: Loads write-product-spec, write-tech-spec and implement-specs for its three main steps; on its own it only decides whether specs are needed and files the Linear issue. Install Warp spec workflow instead.
Needs the Linear MCP server: it creates a Linear issue before writing specs when none exists.
TL;DR
Warp's process for features where written specs will improve an agent's work and the review. Specs are for substantial work: product or architectural ambiguity, around 1k+ lines, deep or cross-cutting changes, risky behavior changes. Small bug fixes, straightforward refactors and narrow UI tweaks usually skip them. Specs live in specs/<Linear ticket>/, and if no Linear issue exists the agent creates one first with the Linear MCP tools, asking you when the team or labels aren't obvious. write-product-spec writes PRODUCT.md, the user-facing behavior, and the agent asks for a Figma mock when there's UI. write-tech-spec writes TECH.md when the work spans subsystems or has trade-offs worth reviewing, possibly after an end-to-end prototype. implement-specs builds from them once they're approved. For large features it may offer PROJECT_LOG.md and DECISIONS.md to record explored paths and decisions. When the implementation drifts, the specs are updated with the code, in the same PR whenever practical, and the work is verified against them with unit and integration tests, and walkthrough recordings or screenshots for UI-heavy work.
Summarizes the skill at 8792394.
npx skills add https://github.com/warpdotdev/common-skills --skill spec-driven-implementation skills.sh pageSource on GitHubAll skills from warpdotdev/common-skills
- Total Downloads
- 28,900 on skills.sh, Nov 9, 2026
- Repo stars
- 678 warpdotdev/common-skills
- First seen
- May 9, 2026 on skills.sh
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 648 |
| Sep 28 | 595 |
| Oct 5 | 930 |
| Oct 12 | 492 |
| Oct 19 | 362 |
| Oct 26 | 358 |
| Nov 2 | 112 |
| Nov 9 | 83 |
| Category |
Make the agent question you and write the plan down before it writes code. Test-first work, implementation from specs, git hygiene and scope control. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
A multi-step process the agent follows: interview, debug, run a TDD loop, review. |
| Effect |
Its own steps change something outside your machine: post, send, deploy, provision, file issues, drive a website, or upload data to a service. |
| Needs |
Needs an MCP server connected. Reads or writes an issue tracker, GitHub Issues by default. |
| Publisher |
Everyone else. Unverified vendor claims default to community. |
| Topics | |
| Stack |
SKILL.md
No copy of its SKILL.md yet.