ratchet:status

Summarize Ratchet project milestones, issues, debates, and phase states from plan.yaml and workflow files.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/netbrain/ratchet --skill ratchet-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ratchet:status
Source: https://github.com/netbrain/ratchet/tree/main/skills/status
Command: npx skills add https://github.com/netbrain/ratchet --skill ratchet-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a concise, human-readable snapshot of a Ratchet project's epic, milestones, issues, debates, and phase progress so teams can quickly understand current work, blockers, and debate activity without running the full pipeline. The Skill surfaces completed, in-progress, pending, and failed/blocked phases and highlights missing or uninitialized state with clear fallback messages.

Core Features & Use Cases

  • Workspace and Milestone Overviews: Summarizes epic progress, workspace counts, and per-milestone status across workspaces.
  • Issue and Phase Drilldowns: Shows issue-level phase progress (plan, test, build, review, harden) and adapts the display to the project's workflow preset.
  • Debate & Guard Visibility: Counts debates, highlights consensus/escalation state, and lists guards and last results to help triage blockers.
  • Robust Fallbacks: Detects missing .ratchet directories or plan.yaml and prompts users with clear next steps to initialize or run the system.
  • Use Case: A release manager uses this Skill to check which milestones are blocked, which issues are in-progress, and whether any debates or guard failures need human escalation before the next sprint.

Quick Start

Run /ratchet:status to display the current workspace's milestone and phase progress and identify active debates and missing plan files.

Frequently Asked Questions about ratchet:status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track project milestone and phase progress without running the full pipeline?

To track milestone and phase progress without running the full pipeline, use a status command that reads .ratchet/plan.yaml and workflow.yaml to summarize completed, in-progress, and blocked phases at a glance.

How do I check which issues are blocked by debates or guard failures before a release?

Checking which issues are blocked by debates or guard failures involves reading debates meta files to highlight consensus, escalation states, and last guard results for triage.

What happens if my .ratchet directory or plan.yaml is missing when checking status?

If your .ratchet directory or plan.yaml is missing when checking status, the system detects the uninitialized state and provides explicit fallback messages prompting you with clear next steps to initialize or run the system.

Can I view issue-level phase progress like plan, test, build, review, and harden for specific milestones?

Viewing issue-level phase progress for plan, test, build, review, and harden is supported by reading workflow.yaml, allowing you to drill down into per-milestone status and adapt displays to your project's workflow preset.

Does the status display adapt to different workflow presets and configurations?

The status display adapts to different workflow presets by reading the workflow.yaml configuration file, ensuring phase tracking accurately reflects the specific stages defined for your project environment.