When you're about to build something non-trivial and want a human checkpoint before the AI starts writing code, this skill generates a structured technical spec in docs/<feature-slug>/spec.md and pauses. It covers what you're building, why, and how, with explicit sections for design decisions, invariants, error behavior, and testing strategy. The spec is written for an AI agent to execute, so it emphasizes specificity over prose: testable requirements, concrete interfaces, version pinning for dependencies, and explicit choices where multiple implementations would diverge. Useful when you say "spec this out" or when a task has enough moving parts that you want to review the approach before committing to an implementation path.
npx skills add https://github.com/owainlewis/blueprint --skill spec