rolepod-fulllisted

# Rolepod Full — force-full lifecycle entrypoint The user typed `/rolepod-full` (or `$rolepod-full`). This is a **command alias**, not a new workflow. It forces Rolepod's complete 6-phase lifecycle with no phase skips: ``` Define → Plan → Build → Verify → Review → Ship ``` Run every phase even if the task looks trivial — the user opted out of the auto-router's skip rules. They can still override mid-flow ("skip review", "just ship"). ## Step 1 — defer to the router If `using-rolepod` is available, load `using-rolepod` and `using-rolepod/references/force-full-lifecycle.md`, then enter **force-full-lifecycle mode**. The phase-by-phase detail, the execution backend table, the start banner, and careful-mode rigor all live in that reference — this alias does not duplicate them. If `using-rolepod` is not available (this skill was copied standalone), run the embedded fallback below. ## Boundary Owns: - Detecting the explicit `/rolepod-full` intent and entering force-full mode. Does not own: - Phase definitions, the execution backend, the Router table, agent roster — `using-rolepod` and its `using-rolepod/references/force-full-lifecycle.md` reference own these. Hand off: - `using-rolepod` force-full mode when available; the embedded fallback when standalone. ## Sanity check — is this feature-scale work? `/rolepod-full` is for feature-scale work: new feature, major refactor, architecture change, product workflow, high-risk change. If the prompt is obviously trivial (`/role