spec-driven-implementation

Drive a spec-first workflow for substantial features in Warp.

Overview

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.

Specs should usually live in:

• specs/<linear-ticket-number>/PRODUCT.md
• specs/<linear-ticket-number>/TECH.md

For example:

• specs/APP-1234/PRODUCT.md
• specs/APP-1234/TECH.md

specs/ should contain only ticket-named directories as direct children. Do not create engineer-named subdirectories or feature-slug directories there.