Menu
Pick the next task from the project's work-item source, plan its implementation, and execute the plan once approved.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Review a GitHub pull request against the shared review principles. Accepts "123" (current repo), "repo#123" (current repo's owner), "owner/repo#123", or a URL. Reports Issues and Notes locally, then optionally posts them to the PR as a review.
Review all outstanding changes — or, when the working tree is clean on a non-main branch, the branch's diff from the main branch. Reports Issues (anything that could cause user problems, security risk, or data inconsistency) and optional Notes for further improvement.
Commit all outstanding changes as standalone, logically coherent atomic commits using Conventional Commits.
Review outstanding changes and surface the single most worthwhile improvement to make before committing. Returns one finding — not a list — and only if it's in scope for the change at hand.
Create a GitHub release. Commits and pushes outstanding changes first, then drafts release notes for confirmation. Deployment is only triggered if the project has a release-triggered workflow.
Bootstrap or sync the tobilize approach in the current project — a thin CLAUDE.md that imports @docs/approach.md plus a docs/ tree (architecture/, design/, domain/, plan/) with INDEX.md in each. Discovers project tooling and layout to seed real build commands and an initial architecture overview, not generic placeholders. Also offers method-specific guidance files (DDD, TDD, Hexagonal, SOLID).
| name | next |
| description | Pick the next task from the project's work-item source, plan its implementation, and execute the plan once approved. |
| disable-model-invocation | true |
An optional argument may follow the command: $ARGUMENTS.
TODO.md, a per-task filename or its contents, an issue key or summary in the tracker).TODO.md, the lowest-numbered or lowest-sorting per-task file, or the top of the tracker's order.First consult the project's own Claude instructions and documentation (CLAUDE.md, AGENTS.md, docs/, READMEs). If they name a source for work items or describe how the next task is chosen, follow that — it takes precedence over everything below.
Otherwise, discover which of these sources the project uses and select the task from it:
A TODO.md file — content lines are the tasks. The first content line is:
!grep -v -e '^#' -e '^-' -e '^>' -e '^$' TODO.md 2>/dev/null | head -1
(- lines are completed/checklist items; #, >, and blank lines are structure.) With an argument, pick the content line that matches the hint instead.
A directory of per-task files (e.g. docs/plan/) — each file is one work item. Order them by the project's convention (filename prefix, date, or numeric order); if none is apparent, sort by filename. Take the first when no argument is given, or the file whose name/contents match the hint. Read the file to get the task.
An MCP connection to an issue tracker (e.g. Jira) — if such an MCP server is connected, query it for the top open issue in the tracker's order, or for the issue matching the hint when an argument is given.
These three are examples, not an exhaustive list. If more than one source exists and the project's documentation doesn't disambiguate, ask the user which to use. If no source yields an actionable task, tell the user there is nothing to do and stop.
Enter plan mode and plan the implementation of the selected task. The plan must include a final step that marks the task done in its source, matched to that source:
TODO.md — remove the task line itself and any adjacent blank lines so no double linebreaks are left behind. Do NOT commit TODO.md after removing the entry.done/ directory) if the documentation specifies one; otherwise delete it.Once the user approves the plan via ExitPlanMode, implement it — including the final step that marks the task done in its source.