القائمة
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).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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 from conversation, and never from a subagent (guard-enforced).
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 autonomously, never from a subagent (guard-enforced).
Refine, analyze, improve, and groom user stories / work items for quality — readiness reports, template restructuring, adaptive gap-filling, and codebase-aware technical grooming. USER-ENTRY and HUMAN-ONLY — invoke only when the user explicitly runs /story-workflow <command>; never autonomously from conversation, never from a subagent (guard-enforced). Distinct from the /dev-workflow pipeline: this shapes the story itself, it does not build it.
Change one config section (overrides / provider / language / repos) on an already-bootstrapped workspace, without re-running the full /init-workspace interview. USER-ENTRY — invoke only when the user explicitly runs /workspace-config; never autonomously, never from a subagent (guard-enforced).
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 autonomously, never from a subagent (guard-enforced).
Register one new repo into an already-bootstrapped workspace, without disturbing repos already registered or re-running the full interview. USER-ENTRY — invoke only when the user explicitly runs /add-repo; 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). |
${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). 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.${CLAUDE_PLUGIN_ROOT}/bin/harness show --run <run> 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.${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.