workflow-status
Skill20 starsChanged 3 months agoMITView on GitHub
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).
4 other projects use a version of this.
Adopted by
Most recently taken up by
- ovargas/virtual-teamtheir own version, first seen Oct 25, 2026
- nurettincoban/ai-prd-workflowtheir own version, first seen Oct 1, 2026
- Yash-Sukhdeve/universal-workflow-systemtheir own version, first seen Oct 1, 2026
- gtrabanco/agentic-workflowtheir own version, first seen Sep 22, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- nurettincoban/ai-prd-workflow★ 300same name
- gtrabanco/agentic-workflow★ 23same name
- ovargas/virtual-team★ 14same name
- Yash-Sukhdeve/universal-workflow-system★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- add-repoSkill
- dev-workflowSkill
- init-workspaceSkill
- migrate-workspaceSkill
- repo-map-refreshSkill
- story-workflowSkill
- workspace-configSkill
The file
Files
workflow-status (read-only)
${CLAUDE_PLUGIN_ROOT}/bin/harness status— every run: cursor, mode, work item, task statuses, decided gates, flagged-event count, and ahealthverdict (HEALTHY|DEGRADED: did the run MACHINERY degrade — stalls, lost evidence; flagged events alone don't flip it, and neither do the several spawns a pipelineddevelopkeeps 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). Anabortedfield marks a run ended by the abort verb (terminal); anerrorfield marks a run whose state failed integrity verification (itsremediationnames the reseal command) — the rest of the dashboard still renders.- 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>— whoseoutstanding_spawnsnames each in-flight spawn's task, mode, agent id, launching step and launch time, so "which lane is still working" needs no ledger read (andlegacy_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. - Offer
${CLAUDE_PLUGIN_ROOT}/bin/harness metrics --run <run>— regeneratesreports/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. - 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

