spec-driven-implementation

spec driven implementation

warpdotdev 146 ↓ 15k MIT updated 27d ago

Claude Code

View source ↗

What it does

specs/<linear-ticket-number>/PRODUCT.md
specs/<linear-ticket-number>/TECH.md
specs/APP-1234/PRODUCT.md
specs/APP-1234/TECH.md
listteams to find the appropriate team
listissuelabels to inspect the expected labels/tags
saveissue to create the issue with the appropriate team and labels

Requirements & configuration

Use this skill for significant features where a written spec will improve implementation quality, reduce ambiguity, or make review easier. Be pragmatic: not every change needs specs.
1. Decide whether the feature needs specs

Configuration: PRODUCTTECHPROJECT_LOGDECISIONS

Derived from the skill's own SKILL.md documentation · extracted 2026-07-23

spec driven implementation

Source

Repository: https://github.com/warpdotdev/common-skills

spec-driven-implementation FAQ

What does the spec-driven-implementation skill do?

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. specs/<linear-ticket-number>/PRODUCT.md specs/<linear-ticket-number>/TECH.md

What does spec-driven-implementation require?

Use this skill for significant features where a written spec will improve implementation quality, reduce ambiguity, or make review easier. Be pragmatic: not every change needs specs. 1. Decide whether the feature needs specs Configuration keys: PRODUCT, TECH, PROJECT_LOG, DECISIONS.

How do I install spec-driven-implementation?

Run: npx -y skills add https://github.com/warpdotdev/common-skills --skill spec-driven-implementation --agent claude-code — the source lives at github.com/warpdotdev/common-skills.

Maintain spec-driven-implementation?

Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.

[![spec-driven-implementation on getagentictools](https://getagentictools.com/badge/skills/warpdotdev-common-skills-spec-driven-implementation.svg)](https://getagentictools.com/skills/warpdotdev-common-skills-spec-driven-implementation?ref=badge)

npx agentictools info skills/warpdotdev-common-skills-spec-driven-implementation

The second line is the CLI lookup for this page — handy in READMEs and docs.