using-rolepodlisted

# Using Rolepod — workflow router Rolepod routes every task through one spine: `Define → Plan → Build → Verify → Review → Ship`. Lead reads this skill on the first turn of each request: pick the phase, fire the required skill, resume normal work inside it. Specialists are chosen **after** the phase is clear, not before. ## Iron Rule <EXTREMELY-IMPORTANT> Before plan / edit / recommendation / answer → identify task type + required phase + required skill. User explicit instruction wins. If user says "skip spec", "answer only", "just write the code" → obey, state which gate was skipped, proceed. Default: route through the spine. Skipping is allowed only when (a) the task is trivial-answer-only, (b) user explicitly authorizes the skip, (c) the request is a question with no action attached, OR (d) the Rigor ladder below assigns R1/R2 — reduced ceremony, never reduced verify. </EXTREMELY-IMPORTANT> ## Router modes Auto-fires on every request. **Auto-router (default)**: picks the FIRST needed phase only — never runs every phase; skips per the Rigor ladder; the user invokes nothing; the Quick router table is the single routing source. **Force-full-lifecycle**: the user explicitly asks for the full workflow — all six phases, no skips unless the user later overrides. ## Commission vs conversation — detected HERE, never flagged by the user Nobody types "answer only" in real use — classifying the message is this skill's job (those phrases stay as overrides, not requirements): -