add-repo
Register one new repo into an already-bootstrapped workspace, without disturbing repos already registered or re-running the full interview. USER-ENTRY — invoke…
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).
$ npx -y skills add MostAshraf/ai-sdlc-harness --skill workflow-status --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/workflow-statusContext 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).
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).
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.
A governed multi-agent SDLC pipeline for Claude Code and Qwen Code — a ground-up rewrite of ai-sdlc-harness.
Register one new repo into an already-bootstrapped workspace, without disturbing repos already registered or re-running the full interview. USER-ENTRY — invoke…
Run the governed SDLC pipeline for a work item. USER-ENTRY — invoke only when the user explicitly runs /dev-workflow <work-item-id>; never trigger autonomously…
One-time workspace setup for the ai-sdlc-harness pipeline. USER-ENTRY and HUMAN-ONLY — invoke only when the user explicitly runs /init-workspace; never…
Adopt a v2.x ai-sdlc-harness workspace into v3.0 — config carries over, run history stays archived in place. USER-ENTRY and HUMAN-ONLY — invoke only when the…
Regenerate the auto-generated repo map the planner grounds its plans in. USER-ENTRY — invoke only when the user explicitly runs /repo-map-refresh; never…
Refine, analyze, improve, and groom user stories / work items for quality — readiness reports, template restructuring, adaptive gap-filling, and codebase-aware…