Ask OOAD — Router

User-invoked router over the ooad-workflow pack. Never fires autonomously — human must call /ask-ooad. Cures cognitive load of remembering 7 skill names (one router to remember instead of many).

When to Use (branches)

Lifecycle order — one trigger per branch (collapse synonyms):

0. Repo not bootstrapped → /setup-ooad (RUP/Waterfall/Agile + tracker + architecture) — once per repo.
1. No PRD / lost vision → /ooad-discover (RUP Inception + Vision + MoSCoW) → produces docs/01-discovery/PRD.md.
2. PRD exists, needs SRS or backlog → /ooad-requirements (IEEE 29148 + UC/INVEST/Gherkin + RDD/CRC + Fagan + RTM).
3. RE baselined, needs architecture → /ooad-architect (C4 + UML + RDD→GRASP + GoF + Clean 4 Layers + ADR-MADR).
4. Architecture approved, needs code → /ooad-build (Clean 4 Layers + TDD + OpenAPI) — slice by UC/US.
5. Code slice green, needs test plan → /ooad-verify (BDD/Gherkin + Test Pyramid 80/15/5) — 4 ↔ 5 iterates per UC/US until green.
6. QA green, needs release → /ooad-ship (Continuous Delivery + SRE).

• Brownfield gap → start at /ooad-architect with gap → US (documented in README.md:31).

Process