spec-driven-implementation
Installation
SKILL.md
spec-driven-implementation
Use a spec-first workflow when it materially improves implementation quality, reduces ambiguity, or makes review safer. This is a local shared skill; an issue workflow or wrapper may provide stricter paths and handoff rules.
Decide whether specs are needed
Strong signals include:
- product, workflow, or architectural ambiguity;
- work around 1k+ LOC or spanning multiple subsystems;
- deep or cross-cutting changes;
- risky behavior, migration, rollout, or compatibility concerns;
- agent-driven work that needs clearer inputs than an issue provides.