Skills warpdotdev common-skills
Warp spec workflow Bundle of 5 skills
- Use it when:
- A feature is big, risky or ambiguous enough that an agent will build it better from written specs.
- It does:
- Decides whether specs are worth it, writes a product spec and, when warranted, a tech spec, builds the feature from them, and finally checks code and specs agree.
- You get:
- specs/<ticket>/PRODUCT.md on what users see and, when warranted, TECH.md on how it's built, in the same PR as the code when practical, updated to match what ships.
- Needs:
- The Linear MCP server, for spec-driven-implementation, which files a Linear issue when there's none.
- Unlike Matt Pocock's to-spec:
- That one publishes the spec to an issue tracker; here the specs are files checked into the repo and reviewed with the code.
TL;DR
Five skills from Warp's shared repo that take a substantial feature from intent to checked code. spec-driven-implementation is the entry point: it decides whether the feature needs specs at all (small bug fixes, simple refactors and narrow UI tweaks usually don't), makes sure a Linear issue exists to name the specs folder after, and hands its three main steps to the next three skills. write-product-spec writes PRODUCT.md: the feature's behavior from its user's side, as numbered, testable rules with no implementation details, after asking for a Figma mock when there's UI. write-tech-spec reads that spec and the code, then writes TECH.md: the current system, the proposed changes and trade-offs, and a test or check for each important rule. implement-specs builds from the approved specs, updating them as soon as the implementation changes, in the same PR when practical, so they describe what ships. validate-changes-match-specs, which you run yourself near the end or in review, lists each material mismatch between the branch's specs and its code, checks what security specs allow and prevent, and asks whether to fix the code or the spec. They're written for Warp's own features; all but the entry point and implement-specs also work alone.
Summarizes the repo at 8792394.
Warp, with the skills CLI
npx skills@latest add warpdotdev/common-skills --skill spec-driven-implementation --skill write-product-spec --skill write-tech-spec --skill implement-specs --skill validate-changes-match-specs --agent warp --global Warp, with the repo's 24 other skills
npx skills@latest add warpdotdev/common-skills --skill '*' --agent warp --global Source on GitHubAll skills from warpdotdev/common-skills
- Total Downloads
- 28,900 of spec-driven-implementation, its most installed skill, on skills.sh, Nov 9, 2026
- Repo stars
- 678 warpdotdev/common-skills
- First seen
- May 9, 2026 on skills.sh, its first skill
Its skills, in the order they're used
The ones marked “Only in the bundle” need the rest of it. The others also work alone.
-
Runs a spec-first workflow for large features: product spec, tech spec when needed, then code, with specs kept current in the same PR.
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.
-
write-product-spec
28.9K total downloadsWrites a PRODUCT.md spec describing a feature's behavior from its user's side as numbered, testable rules, before implementation starts.
-
write-tech-spec
28.8K total downloadsResearches the codebase and writes a TECH.md implementation plan for a feature, with commit-pinned code links and tests mapped to the product spec.
-
Builds a feature from its approved PRODUCT.md and TECH.md, updating both specs in the same PR whenever the implementation changes course.
Starts only once PRODUCT.md, and TECH.md when warranted, exist and are approved: the specs that write-product-spec and write-tech-spec write.
-
validate-changes-match-specs
25.3K total downloadsChecks a branch's code against the product, tech and security specs it introduces, then resolves each mismatch the way you choose.