routing

To automatically route a design.md spec, run the /implement command after generating your specification with /design. The skill parses the approved design content, detects domain indicators, and returns an ordered sequence of appropriate agents for execution.

If no approved spec exists during routing, the skill provides clear error handling and guidance. It requires an approved design.md or requirements.md file to parse content and determine the correct backend, frontend, docs, or evaluation agents.

Yes, you can route mixed-scope specs covering both backend and frontend work. The skill detects multi-domain specifications and routes tasks to multiple agents in the correct sequential order based on the detected domain indicators.

Spec analysis determines agent assignments by parsing approved design.md content to detect domain indicators across backend, frontend, documentation, and evaluation tasks. It then returns an ordered sequence of agents matching the detected spec scope.

Automated routing for ambiguous specifications is limited by the clarity of domain indicators in the design.md file. If the spec type is ambiguous, the skill returns clear errors instead of guessing, ensuring accurate agent assignment for spec-driven development.