speckit-blueprint-generate

To generate an implementation plan, you use a blueprint generator that parses tasks.md, spec.md, and plan.md to produce an ordered, traceable pre-implementation blueprint with file-by-file intent and verification checklists.

Spec-driven development scaffolding is the process of translating structured specification documents into a pre-implementation blueprint, optionally creating new files with TODO stubs on disk while maintaining zero TODOs inside the blueprint itself.

Yes, you can produce documentation-only output by default to create a blueprint.md from your current spec artifacts, allowing you to review the structured plan before executing any code generation or file modifications.

The blueprint generation process automatically classifies every task file path as new, modified, deleted, or already-complete, handling finished tasks via a pre-completed summary table to maintain 1:1 traceability with task IDs.

The best way to prevent blind implementation is converting spec artifacts into a pre-implementation blueprint that preserves code conventions and execution order, ensuring the next implementation step can execute directly from complete, copy-pastable code blocks.

Yes, prerequisite checks are required before generating a spec blueprint to validate the existence and structure of necessary spec artifacts, ensuring the resulting blueprint.md contains accurate, traceable implementation steps.