Workflow

Implement one selected task from an initialized workflow board with a minimal deliberate loop: read routed docs, plan, implement, validate, and commit. Use when the user explicitly invokes "/workflow:work", "/work", "/work 051", or "use $work". When workflow/AGENTS.md exists, also use for an unmistakable request to implement the next, numbered, or Ready workflow-board task. Do not use for generic implementation requests. If explicitly invoked in an uninitialized repo, stop and suggest /workflow:framework-init; never invoke it automatically.

Refine tasks in the repo's workflow/ status folders into implementable specs, and capture concrete work items found during exploration onto that board. Use when the user explicitly invokes "/workflow:groom", "/groom", "groom 052", or "use $groom". In an initialized repo (workflow/AGENTS.md exists), also use without being asked when an exploration, investigation, audit, or review — by you or by an agent reporting back — has produced concrete work items the user wants tracked, and for an unmistakable request to put an ask onto that board. Do not use for generic planning or task-refinement requests, and do not use in a repo that has no workflow/AGENTS.md. If explicitly invoked in an uninitialized repo, stop and suggest /workflow:framework-init; never invoke it automatically.

Show a decision-oriented overview of tracked workflow-board work in the current repo, or a one-line-per-repo table with "all". Always use when the user explicitly invokes "/workflow:status" or "use $status", including when that invocation carries a follow-up question (scoped to a tag, which tasks can run in parallel, what a chain waits on) — the question is the request, not a reason to skip the skill. When workflow/AGENTS.md exists in this initialized repo, also use for an unmistakable question about that board's queue, progress, dependencies, or gates. Do not use for generic project-status questions unrelated to that board. Read-only; never edits, moves, commits, or initializes the framework.

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.

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.

Explicit invocation only. Initialize the workflow framework in a repo that does not 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 only when the user explicitly invokes "/workflow:framework-init", says "init the workflow" or "set up the board here", or invokes "use $framework-init". Never invoke this skill because a different workflow skill found no workflow/AGENTS.md. A repo with an existing legacy markdown board must be migrated to status folders by hand first.

Validate an initialized workflow repo and keep its shipped files and task metadata current. Use when the user says "/workflow:framework-doctor", "check the board", "validate work tracking", or when another workflow skill hits an inconsistent structure. Reports findings first; refreshes drifted files only after the user approves. Not a migrator — for a repo with no board use /workflow:framework-init.