بنقرة واحدة
ratchet-status
Show milestone and phase progress at a glance
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Show milestone and phase progress at a glance
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run agent pairs through phase-gated debates — guided by epic roadmap and current focus
Analyze project and generate tailored agent pairs through codebase analysis and human interview
Tighten the ratchet — analyze all improvement signals and sharpen the system
View or continue an ongoing debate
Manage guards — list, add, run, and override deterministic checks at phase boundaries
Add a new agent pair to an existing Ratchet configuration
| name | ratchet:status |
| description | Show milestone and phase progress at a glance |
State injected at startup so status skill renders immediately without file reads at runtime. All blocks fail gracefully with explicit fallback messages.
Plan:
$(cat .ratchet/plan.yaml 2>/dev/null || echo "No plan.yaml found — run /ratchet:init to create a project plan.")
Debate count:
$(if [ -d .ratchet/debates ] && ls .ratchet/debates/*/meta.json >/dev/null 2>&1; then
echo "Total debates: $(ls .ratchet/debates/*/meta.json 2>/dev/null | wc -l)"
else
echo "No debates found — run /ratchet:run to start your first debate."
fi)
Ratchet directory check:
$(if [ ! -d .ratchet ]; then
echo "Ratchet not initialized — run /ratchet:init to set up."
fi)
Fallback behavior summary:
| Condition | Fallback message |
|---|---|
.ratchet/ directory missing | "Ratchet not initialized — run /ratchet:init to set up." |
.ratchet/plan.yaml missing | "No plan.yaml found — run /ratchet:init to create a project plan." |
.ratchet/debates/ empty or missing | "No debates found — run /ratchet:run to start your first debate." |
Display snapshot of project progress through epic, milestones, and phases.
/ratchet:status # Full status overview (or workspace overview from root)
/ratchet:status [milestone] # Detailed view of a specific milestone
/ratchet:status [workspace] # Status for a specific workspace in a multi-project setup
.ratchet/ must exist.ratchet/plan.yaml must exist (for workspace-level status)If .ratchet/ or plan.yaml does not exist, inform user: "No epic found. Run /ratchet:init to set up a project, or /ratchet:run to start without an epic." Then AskUserQuestion with options: "Initialize (/ratchet:init) (Recommended)", "Done for now".
Workspace resolution: Same algorithm as /ratchet:run Step 1a. If at workspace root with no workspace specified, show workspace overview (Step 2b). If a workspace is resolved, show workspace-level status.
Read plan.yaml and workflow.yaml from resolved .ratchet/ directory. Also scan debates/*/meta.json to count active/resolved debates per milestone.
If at workspace root with no workspace specified, read each workspace's plan.yaml and show:
Workspaces: [N]
Shared policy: models=[generative:opus, adversarial:sonnet] escalation=[human]
┌───────────────────────────────────────────────────────────────┐
│ monitor │
│ Epic: [name] — [completed]/[total] milestones │
│ Current: [milestone name] — [phase] phase │
│ Pairs: [N] active, [N] total │
│ │
│ engine │
│ No active milestones │
└───────────────────────────────────────────────────────────────┘
Then AskUserQuestion:
"View [name] status", plus "Done for now"Present compact status view:
Epic: [project name] — [description]
Progress: [completed]/[total] milestones
┌─────────────────────────────────────────────────────────┐
│ Milestone 1: [name] [DONE] │
│ Issues: [N]/[N] complete │
│ Debates: [N] total, [N] consensus, [N] escalated │
│ │
│ Milestone 2: [name] [IN PROGRESS] │
│ Issues: │
│ [ref]: [title] [DONE] │
│ plan ✓ test ✓ build ✓ review ✓ harden ✓ │
│ [ref]: [title] [IN PROGRESS] │
│ plan ✓ test ✓ build ● review ○ harden ○ │
│ [ref]: [title] [PENDING — dep: [ref]] │
│ plan ○ test ○ build ○ review ○ harden ○ │
│ Debates: [N] active, [N] resolved │
│ │
│ Milestone 3: [name] [PENDING] │
│ Issues: [N] total │
└─────────────────────────────────────────────────────────┘
✓ = done ● = in progress ○ = pending ✗ = failed/blocked
If epic.discoveries exists in plan.yaml and has items with status == "pending", append:
Sidequests: [N] pending
[discovery-ref]: [title] ([category], [severity])
...
Run /ratchet:run to process sidequests.
Filters out discoveries that have been promoted, dismissed, or marked done. Only actionable pending discoveries shown.
Adapt phase display based on component's workflow preset:
tdd: show all 5 phasestraditional: show plan, build, review, harden (skip test)review-only: show only reviewIf specific milestone requested, show expanded detail:
Milestone [id]: [name]
Status: [status]
Description: [description]
Done when: [acceptance criteria]
Regressions: [N]/[max]
Issues:
[ref]: [title] [status]
Depends on: [dep-refs or "none"]
Branch: [branch name or "not started"]
PR: [URL or "none"]
Phase Progress:
plan ✓ test ✓ build ● review ○ harden ○
Pairs:
[pair-name] — [phase] — last debate: [debate-id]
Debates: [N] total ([N] consensus, [N] active)
[ref]: [title] [status]
...
Guards:
[guard-name] — phase: [phase] — blocking: [yes/no] — last result: [pass/fail/not run]
Unresolved Conditions:
[condition from CONDITIONAL_ACCEPT, if any]
After displaying status, AskUserQuestion: