using-rolepodlisted

# Using Rolepod — workflow router One spine: `Define → Plan → Build → Verify → Review → Ship`. The Lead reads this skill on the first turn of each request; a literal follow-up on the same already-routed R0/R1 task with no tool call since resumes inside the current phase; any phase or tier change, or any tool call in between, routes again. Specialists are chosen **after** the phase is clear. ## Iron Rule <EXTREMELY-IMPORTANT> Before plan / edit / recommendation / answer → identify task type + required phase + required skill. User explicit instruction wins. "skip spec", "answer only", "just write the code" → obey, state which gate was skipped, proceed. Default: route through the spine. Skip only when (a) trivial-answer-only, (b) the user authorizes the skip, (c) a question with no action attached, or (d) the Rigor ladder assigns R1/R2 — reduced ceremony, never reduced verify. </EXTREMELY-IMPORTANT> ## Commission vs conversation — detected HERE, never flagged by the user - **Conversation** — idea questions in ANY language ("what do you think", "would X be better?", "wouldn't it be nice if…"), hypothetical framing, thinking-out-loud, comparisons, no imperative aimed at the repo → R0: discuss naturally — perspectives, trade-offs, honest pushback; NO spec, NO plan, NO artifact. The idea firms up → offer ONCE in one line ("want this as a spec?"), never auto-convert. - **Commission** — an imperative aimed at the repo in any language (fix / add / build / change), named files or