spec-driven-workflow
Installation
SKILL.md
Spec-Driven Workflow
Adopt this workflow as the standard software engineering process for any non-trivial change. Do not jump straight into writing code; follow the gated lifecycle below using the workflow/ directory to separate why/value (BACKLOG.md), what needs to change (SPEC.md), how it will be built (PLAN.md), who executes independent pieces (TASKS.md), what needs attention after implementation (REVIEW.md), and whether the delivered value meets product expectations (VALIDATION.md).
Standard Operating Flow
Follow these phases in order:
- Discover & Frame (
BACKLOG.md, conditional) — Capture product intent, user value, priority, or a prioritized mini-backlog of evolutions/bugs (typically owned by theproduct-ownerrole) before technical specification. - Specify (
SPEC.md) — Define the problem, scope, constraints, and acceptance criteria (consumingBACKLOG.mdwhen present) before designing or coding. - Plan (
PLAN.md) — Map the technical approach, affected files, ordered steps, and verification strategy. - Shard (
TASKS.md, conditional) — Break the plan into trackable tasks only when complexity, multi-scope work, or parallel execution warrants it. - Implement — Execute against
PLAN.md(orTASKS.md), keeping artifact statuses current as work progresses. - Review (
REVIEW.md) — Record code review findings (human or agent) and resolve blockers/major issues before completion. - Validate (
VALIDATION.md, conditional) — Hand the approved delivery back to the Product Owner (or stakeholder) with plain-language summary and validation scenarios to confirm product value before cleanup.
Trivial changes exception: Skip
workflow/artifacts only for trivial, self-contained edits (e.g., typo fixes, single-line formatting, or minor comment updates) where specification and planning add no value.