Write specs before code
spec-driven-workflowskillsetup L1★17,464
alirezarezvani/claude-skills ↗What it does
Write specifications before code using RFC 2119 and acceptance criteria
Best for
Teams needing atomic, testable requirements and 1:1 traceability from spec to test to implementation.
Inputs
- · [object Object]
- · [object Object]
Outputs
- · [object Object]
Preconditions
- · Clear problem statement; stakeholder alignment on requirements
- · Time to write spec before code (adds 5-15% project time, saves 60-80% defect cost)
Failure modes
- · Scope creep if team ignores Out of Scope section
- · Ambiguous AC leads to rework if not enforced at code review
- · Bounded autonomy rules ignored → implementation diverges from spec
Trust signals
- · RFC 2119 keywords enforce unambiguous language
- · Every AC traces to FR/NFR; every code change references AC