Technical spec before coding

★ 7.7 · documentation

spec is a Claude Code skill that generates a verifiable technical specification before any code is written. It enforces 6 mandatory sections: Interfaces (public APIs and type signatures), Behaviors (given-when-then scenarios), Invariants (irreducible constraints sourced from Aristotle Phase 2), File Plan (exact files to create or modify), Test Plan, and Exit Criteria — executable bash commands with expected results that define done unambiguously. Use it before implementing features with complexity above 4, as Step 1.5 in the orchestrator workflow, or whenever requirements need formalization. The specification is saved to `<feature-name>.spec.md` in the project root or `docs/specs/` directory. Trigger with `/spec`, "create spec", or "write specification".