spec-builder

To generate a structured spec for task planning, provide your verbatim user ask and any known context. The spec-builder produces a formal document capturing problem definition, intent, constraints, phases, and success criteria ready for orchestration.

A task planning spec document includes the problem statement, intent, context summary, suggested skills, assumptions, success criteria, approach, phases, phase dependency graph, and pre-mortem analysis to guide downstream execution.

You need to create a spec before decomposing a complex task when planning new work across code, research, writing, or data flows. Generating a formal spec captures constraints and capability gaps to enable effective orchestration.

Yes, you can use this spec generation approach for research and browser flow planning. It is suitable for planning new tasks across diverse domains including code, research, writing, browser flows, and data work.

To identify capability gaps and assumptions during workflow planning, input your raw task request. The generated spec explicitly lists capability gaps, assumptions, and raw tools needed to highlight missing resources before execution.

Yes, the generated spec influences phase sequencing and resource needs. The output contains a phase dependency graph and pre-mortem analysis intended for plan-composer to execute and adjust sequencing accordingly.