prd-orchestratorlisted

# PRD Orchestrator ## Purpose Orchestrate the phased installation and execution of external PRD skills so the coding agent produces an execution-ready PRD rather than a shallow or generic document. This skill does not write the PRD itself. It prepares the agent, installs the right skills at the right time, runs quality gates, and hands off to PRD generation with the correct capabilities active. ## Why This Skill Exists A weak PRD usually fails in one of these ways: - too vague - too feature-list driven - ignores constraints - skips measurable success criteria - hides non-goals - cannot be turned cleanly into plan or issues This orchestrator prevents that by installing specialized skills in phases and enforcing quality gates between each phase. ## Core Principle Do not install every PRD skill at once. Different skills play different roles at different times: | Phase | Skills | Role | |-------|--------|------| | A | prd, write-a-prd | Discovery + drafting | | B | prd-development, breakdown-feature-prd | PM refinement + feature breakdown | | C | prd-to-plan, prd-to-issues | Execution conversion | VDD remains the orchestrator. External skills remain specialized helpers. ## Phase Definitions ### Phase A — PRD Foundation **Triggers:** project intent is clear, target user is clear, success direction is visible. **Skills to install:** 1. `github/awesome-copilot --skill prd` — Lead discovery skill. Forces problem clarification, success metrics, constraints, non-goals,