القائمة
Force-full Rolepod lifecycle — Define → Plan → Build → Verify → Review → Ship with no phase skips. Use only when the user explicitly invokes /rolepod-full or $rolepod-full for feature-scale work.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when executing an approved plan or a clear single-file edit — TDD for risky paths, surgical edits, bounded delegation, worktrees only when real filesystem isolation is needed. Phase = Build.
Use when executing an approved plan or a clear single-file edit — TDD for risky paths, surgical edits, bounded delegation, worktrees only when real filesystem isolation is needed. Phase = Build.
Use when executing an approved plan or a clear single-file edit — TDD for risky paths, surgical edits, bounded delegation, worktrees only when real filesystem isolation is needed. Phase = Build.
Use at the end of a development branch — pre-merge gate, CI lane discipline, 4-option finish menu (merge, PR, keep open, discard), release checklist for production launches. Phase = Ship.
Use at the start of every request to route work into Rolepod's workflow spine before planning, editing, delegating, verifying, reviewing, or shipping. Determines phase, required skills, skip rules, and evidence needed.
Use when turning an approved spec or a small clear goal into an executable implementation plan — ordered tasks, file list, test plan, agent routing, and parallel contracts if more than one agent will edit code. Phase = Plan.
| name | rolepod-full |
| description | Force-full Rolepod lifecycle — Define → Plan → Build → Verify → Review → Ship with no phase skips. Use only when the user explicitly invokes /rolepod-full or $rolepod-full for feature-scale work. |
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").
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.
Owns:
/rolepod-full intent and entering force-full mode.Does not own:
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./rolepod-full is for feature-scale work: new feature, major refactor, architecture change, product workflow, high-risk change. If the prompt is obviously trivial (/rolepod-full what time is it), ask the user whether they meant force-full mode before running the full ceremony.
using-rolepod not availableIf copied standalone, run the lifecycle directly as Lead:
This fallback is ~70% of the full behavior. With using-rolepod present it is router-backed; with a full Rolepod install it is best.