Menu
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).
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle 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).
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).
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 | repo-map-refresh |
| description | 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). |
The repo map is a navigation aid, never hand-maintained — corrections go
through regeneration (design.md piece 5B). /init-workspace and
/add-repo both point here for the identical generate-or-regenerate
procedure (step 2 below) — this is the one place it's maintained; don't
fork a second copy of it elsewhere.
${CLAUDE_PLUGIN_ROOT}/bin/harness repo-map-check --repo-name <n> --repo <path> — report
missing / fresh / stale (+ commits behind) to the user.harness-mode: repo-map as
the prompt's FIRST line (the spawn guard regex-matches this exact
header — prose that merely mentions repo-map does not satisfy it; this
is a declared out-of-run spawn, pipeline/surfaces.yaml's
out_of_run_spawns, legal regardless of whether other runs exist in the
workspace) and the repo path. Do not guess the planner's subagent_type
string: check your currently available subagent types for whichever one
corresponds to this plugin's planner (agents/planner.md's frontmatter
name: planner is the identifying detail to match against) —
hooks/guards.py's spawn guard matches on this shape by the LAST
:-segment of whatever string you pass, and a wrong guess doesn't
error, it just silently skips the guard's enforcement (fail-closed
spawn gating, planner's write-confinement to ai//.claude/context/),
which is worse than the guess looking right. The planner can only write
under ai/<run>/ and .claude/context/ (guard-enforced — never repo
source), so point it at .claude/context/repo-map/<name>/. It follows
the map content contract
(${CLAUDE_PLUGIN_ROOT}/skills/dev-workflow/steps/repo-map-task.md):
index.md (purpose/stack/modules/cross-repo edges — intake's targeting
tier), areas/* detail files (each loadable alone), and
conventions.md (observed patterns with cited examples — what
plan-review checks plans against).${CLAUDE_PLUGIN_ROOT}/bin/harness repo-map-stamp --repo-name <n> --repo <path>
— stamping is the orchestrator's job, never the planner's own.