rough-draft-blueprint

To create a blueprint document for a complex software feature, provide a work item brief to automatically generate structure enumeration, function blueprints, and a YAML task graph. This reduces planning time and miscommunication by producing a coherent design before coding.

You need to generate a task dependency graph when starting multi-file software features, refactors, or complex enhancements requiring coordinated changes. It guides execution by visualizing dependencies through a Mermaid diagram and YAML task graph.

The best way to plan structure and function interfaces for multi-file software engineering tasks is to enumerate required files, modules, and public interfaces in a blueprint. This process specifies function signatures, pseudocode, and stub implementations for coordinated changes.

Yes, you can generate pseudocode and stub implementations directly from a work item brief. The blueprinting process specifies function signatures and provides guidance for stubs and tests, translating a brief into structured pseudocode for development.

Yes, this blueprinting process works for refactoring existing software features. It applies to multi-file refactors and complex enhancements requiring coordinated changes and dependency planning, enumerating affected files and public interfaces.