Spec Driven Implementation

This enforces a spec-first workflow for substantial features, creating PRODUCT.md and TECH.md files under specs/<ticket-number>/ before you write code. It's pragmatic about when specs actually help: think 1k+ LOC changes, cross-cutting work, or anything with meaningful ambiguity where an agent or reviewer benefits from reading the plan before the implementation. The workflow ties directly into Linear for issue tracking and keeps specs updated in the same PR as code changes, so they don't go stale. Skip it for small bug fixes or straightforward refactors. The honest take: this is useful if you're working in a team context where checked-in specs become the shared source of truth, less so if you just want to move fast on solo work.

Install to Claude Code

npx -y skills add warpdotdev/common-skills --skill spec-driven-implementation --agent claude-code