using-agent-skills

To route ambiguous agent requests, apply minimal binary routing to determine whether the primary output requires project-definition artifacts like specs or project-implementation artifacts like code, then immediately hand off control to the selected workflow.

Use workflow handoff for ambiguous project prompts when a user request is too unclear to reliably decide whether the agent should produce a definition-style deliverable like a spec or an implementation-style deliverable like code.

The best way to decide between creating a PRD or writing code is using a fast clarification loop that asks or determines the required output type, then transfers control to project-definition or project-implementation without producing full downstream artifacts.

No, this ambiguity resolution approach includes guardrails for handoff and avoids taking over when users explicitly ask for PRD, spec, roadmap, scope, architecture proposal, implementation plan, code, debug, review, testing, CI, CD, or release.

Binary routing for mixed or early-stage prompts requires a minimal two-way decision and immediately hands off without producing full downstream artifacts, meaning it only selects the destination workflow rather than generating the complete deliverables itself.