Skip to content
Development
Skill

/workflow-status

Read-only dashboard of ai-sdlc-harness runs in this workspace. USER-ENTRY — invoke only when the user explicitly runs /workflow-status; never autonomously, never from a subagent (guard-enforced).

From plugin
ai-sdlc-harness
198 skills3 agents4 hooks
Install
$ npx -y skills add MostAshraf/ai-sdlc-harness --skill workflow-status --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/workflow-status

Context preview

The summary Claude sees to decide when to auto-load this skill.

Read-only dashboard of ai-sdlc-harness runs in this workspace. USER-ENTRY — invoke only when the user explicitly runs /workflow-status; never autonomously, never from a subagent (guard-enforced).

SKILL.md

workflow-status.SKILL.md
name: workflow-status
description: >
  Read-only dashboard of ai-sdlc-harness runs in this workspace. USER-ENTRY —
  invoke only when the user explicitly runs /workflow-status; never
  autonomously, never from a subagent (guard-enforced).

workflow-status (read-only)

1. `${CLAUDE_PLUGIN_ROOT}/bin/harness status` — every run: cursor, mode, work item, task statuses, decided gates, flagged-event count, and a `health` verdict (`HEALTHY` | `DEGRADED`: did the run MACHINERY degrade — stalls, lost evidence; flagged events alone don't flip it, and neither do the several spawns a pipelined `develop` keeps in flight — only one the run has moved PAST or launched in a round a gate has since closed out, whose evidence is never arriving). An `aborted` field marks a run ended by the abort verb (terminal); an `error` field marks a run whose state failed integrity verification (its `remediation` names the reseal command) — the rest of the dashboard still renders. 2. Render it as a compact table for the user; for a run they ask about, drill in with `${CLAUDE_PLUGIN_ROOT}/bin/harness show --run <run>` — whose `outstanding_spawns` names each in-flight spawn's task, mode, agent id, launching step and launch time, so "which lane is still working" needs no ledger read (and `legacy_spawn_pendings`, if non-empty, names spawns launched before an upgrade whose capture can no longer land) — plus the ledgers (`events.ndjson` — the "what happened" trail; `tokens.ndjson` — spend) and compose the per-task timeline: status + review rounds + stalls + flagged events + gate evidence. 3. Offer `${CLAUDE_PLUGIN_ROOT}/bin/harness metrics --run <run>` — regenerates `reports/metrics.md`, the human-readable table view of the same ledgers (run health, timings, tasks, verdicts, aggregated tokens, flagged events). Works at any live step, not just the terminal metrics step; it's a deterministic projection, so regenerating is always safe. 4. Otherwise STRICTLY read-only: no state changes, no cursor moves, no ledger writes — the report above is the one derived, regenerable output; everything else only reads what the authority already records.

Read more
Ships withai-sdlc-harness

A governed multi-agent SDLC pipeline for Claude Code and Qwen Code — a ground-up rewrite of ai-sdlc-harness.

Get the whole plugin
Stats
19
Stars
4
Forks
Active
Maintenance
Python
Language
MIT
License
20d ago
Last commit
4mo ago
Created

Repo: MostAshraf/ai-sdlc-harness

Other skills on ai-sdlc-harness.