메뉴
Show a combined work-status view across every repo that has workflow/ status folders. Use when the user says "/workflow:status", "board status", "what's in progress across my projects", or asks for a cross-repo overview of tracked work. Read-only; never edits or commits.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Refine a task in the repo's workflow/ status folders into an implementable spec. Use when the user says "/workflow:groom", "/groom", "groom 052", "refine this task", or hands a fuzzy ask that should enter the board. Requires an initialized framework (workflow/AGENTS.md exists); otherwise route to /workflow:framework-init first.
Implement one task from the repo's workflow/ status folders, or any small ad-hoc ask, with a minimal deliberate loop: read routed docs, brief plan, implement, validate, atomic completion commit. Use when the user says "/workflow:work", "/work", "/work 051", asks for the next task, or hands an implementation task. Requires an initialized framework (workflow/AGENTS.md exists); otherwise route to /workflow:framework-init first.
Run multiple Ready tasks from the repo's workflow/ status folders sequentially in isolated subagents, with a consolidated report. Use when the user asks to batch-run tasks, run work overnight, run the first N Ready tasks, or invokes /workflow:batch-work, /batch-work, or /batch.
Append a decision record with a stable D<N> handle to the repo's decision log. Use when the user says "/workflow:decision", "log this decision", "record why we chose X", or when /workflow:work surfaces an A/B/X choice a future agent might plausibly flip. Skip for choices that die with the task.
Validate a repo's workflow framework and migrate legacy layouts. Use when the user says "/workflow:framework-check", "check the board", "validate work tracking", "migrate to the workflow plugin", or when another workflow skill hits an inconsistent or legacy structure. Reports findings and a migration plan first; applies fixes only after the user approves.
Initialize the workflow framework in a repo that doesn't have one: create the workflow/ status folders, install the board-view script, write the repo contract, scaffold the docs skeleton, and route AGENTS.md to the plugin. Use when the user says "/workflow:framework-init", "init the workflow", "set up the board here", or when another workflow skill finds no workflow/AGENTS.md. For repos with an existing legacy board (docs/board.md or a workflow/board.md file), use /workflow:framework-check instead — it migrates.
| name | status |
| description | Show a combined work-status view across every repo that has workflow/ status folders. Use when the user says "/workflow:status", "board status", "what's in progress across my projects", or asks for a cross-repo overview of tracked work. Read-only; never edits or commits. |
One combined view over all boards. Read-only.
~/work/*/workflow/ plus the current repo for the status-folder layout../workflow/status when present (it prints all sections); otherwise list the status folders directly (first line of each file is # NNN — Title; priority:/gate:/done: lines carry the rest).| Repo | In progress | Next ready | Blocked | Done (7d) |
|------|-------------|------------|---------|-----------|
| rift-drifter | 051 — Title | 052 — Title (+4) | 1 (gate: …) | 3 |
Next ready = lowest priority: in ready/, ties by id. Done (7d) = files in done/ with a done: date in the last 7 days.
Follow the table with anything that needs attention: stale in-progress tasks (uncommitted move or older than the newest done), empty Ready queues, blocked gates that look satisfiable.
Keep it to the table + a few bullets. No edits, no commits, no fixing — point to /workflow:framework-check for inconsistencies.