recipe-agent-team-design-spec

Generating design-spec artifacts requires a locked design-brief.md containing an Output Description and a designated Output Path. If the brief is incomplete or missing, you must run recipe-agent-team-design-interview first to capture missing gaps before generating the spec.

Pattern hint automation works by consuming design-brief.md, reading its Output Description, and consulting pattern hints stored in the references/ directory to produce design-spec artifacts. The generated files are then routed and saved under the brief's specified Output Path.

Yes, you need a completed design brief to automate spec generation. The recipe requires a design-brief.md to seed artifact generation; if no brief exists, the orchestrator skips this step and runs recipe-agent-team-design-interview to capture missing requirements first.

No, you cannot use this design spec workflow for backend architecture, code generation, review, or post-run learning tasks. It is strictly a generic spec producer for locked design briefs and skips execution when it detects out-of-scope technical requirements.

The best way to handle incomplete design briefs in automated workflows is to route the process to recipe-agent-team-design-interview. This companion step captures the missing gaps and completes the brief before the design-spec recipe attempts to generate artifacts.