sdd

You can automate spec-driven development by entering your feature request, which routes the input transparently to workflow agents for design, task breakdown, and implementation execution.

Workflow modes—express, standard, and deep—act as routing identifiers to drive corresponding workflow agents. You select a mode by passing an optional workflow flag to match the desired depth of design and implementation processing.

Routing a feature description to a development workflow agent requires submitting the request through the unified entry point. The system transparently forwards the input to routing, which coordinates with agents for end-to-end execution.

You do not need to specify a workflow mode to start the spec-driven routing process. Workflow flags are optional; without them, the system forwards the feature request directly to routing for default end-to-end execution.

Yes, you can coordinate design and task decomposition within a single automated workflow. The unified entry point routes feature requests to workflow agents that handle specification design, task breakdown, and implementation execution sequentially.

The unified entry point routes feature requests transparently but relies on workflow agents for downstream execution. Its limitation is that it coordinates the workflow without altering the input, meaning complex edge cases depend entirely on the selected agent's capabilities.