forge-status

Display a formatted dashboard of the current pipeline state.

When to Use

Use this skill whenever the user:

• Runs /forge:status
• Asks "what stage am I on?", "where are we?", "what's the current task?"
• Asks about blockers, progress, or pipeline state
• You need to orient before recommending the next step in a Forge project

Steps

1. Read state by running:

   python3 ${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.py --cwd . read

   If the command fails with exit code 1, the project is not initialized — tell the user to run /forge:init first.

2. Parse the JSON output and build the status dashboard:

   ## Forge Pipeline Status
   
   Project : <project_type>          Cycle: <cycle>
   Stage   : <current_stage> / 12   [████████░░░░] (<pct>%)
   Task    : <current_task or "(none)">
   Milestone: <current_milestone or "(none)">
   Updated : <last_updated>
   
   Blockers:
     <each blocker on its own line, or "(none)" if blockers is empty>

   Compute the progress bar: 8 filled blocks = current_stage / 12 * 8 blocks, remainder as empty blocks.

3. If scripts/check-gate.py exists, run:

   python3 ${CLAUDE_PLUGIN_ROOT}/scripts/check-gate.py --stage <current_stage> --cwd .

   and append a Gate section showing pass/fail per criterion. If the JSON has inconclusive: true or unimplemented > 0, surface a banner at the top of the Gate section — ⚠️ N criteria unimplemented — gate result is provisional — so a wedged pipeline is never rationalized as "warnings only" (REQ-GATESTUB-001). A provisional gate is not a pass. If check-gate.py does not exist yet, skip this step silently.
4. Append the Observer status line (Stage-9 daemon, T-142). Run:

   python3 ${CLAUDE_PLUGIN_ROOT}/scripts/observer.py --status --cwd .

   Show its one-line output verbatim under the dashboard, e.g. Observer: running · last poll 12m ago · 3 unread finding(s) or Observer: not running (/forge:watch to start). This command also marks the surfaced findings as read. If observer.py is absent, skip silently.
5. Print the dashboard to the user.
6. Suggest the obvious next action based on state:
   • current_stage == 0 → "Run /forge:srs to begin Stage 1 (Requirements)"
   • blockers non-empty → "Resolve blockers before advancing"
   • Otherwise → "Continue with /forge:<current-stage-command>"

Stage Names

Verification

The skill worked correctly if:

• The dashboard renders with correct stage number and project type
• Blockers list matches what is in pipeline/state.md
• The next-step suggestion matches the current stage

Example Output

## Forge Pipeline Status

Project : ml-pipeline          Cycle: 1
Stage   : 3 / 12   [████░░░░░░░░] (25%)
Task    : T-007
Milestone: M2
Updated : 2026-05-07T14:32:00Z

Blockers:
  (none)

Next: Continue with `/forge:spec` (Stage 4)