next
Skill26 starsChanged 9 months agoMITView on GitHub
Analyze and pick the next task to work on. Reads MASTER_PLAN.md, scores tasks by priority and status, and presents interactive selection. Use when starting a session or deciding what to tackle next.
40 other projects use a version of this.
Adopted by
Most recently taken up by
- edwinidrus/dragonhoardtheir own version, first seen Nov 8, 2026
- buildomator/buildomatortheir own version, first seen Nov 4, 2026
- mag123c/toktracktheir own version, first seen Nov 3, 2026
- Hainrixz/claude-dbtheir own version, first seen Nov 1, 2026
- mandarzope/fullstack-swarmtheir own version, first seen Nov 1, 2026
- vercel-labs/emulatetheir own version, first seen Oct 29, 2026
Used with
Projects with it also use quick, project and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
codebycoreySkillquick
Quick start a change with minimal interaction. Use when fast-tracking a straightforward change that needs proposal, design, and tasks in one step.
Also in 3 projects that use this
BugRogerSkillproject
Project lifecycle management. Dispatches to Ada.
Also in 3 projects that use this
AnthropicSkillstatus
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Also in 9 projects that use this
MicrosoftSkillcleanup
Also in 4 projects that use this
ArvorCoSkillclarify
Identify and resolve ambiguities in feature specifications. Use when spec has unclear requirements. Triggers on: clarify spec, resolve ambiguities, clarify requirements.
Also in 3 projects that use this
genomewalkerSkillexplore
RLM-style recursive memory exploration - dynamically navigate the memory graph
Also in 3 projects that use this
Other versions40 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 40
- vercel-labs/json-render★ 19ksame name
- vercel-labs/emulate★ 2ksame name
- ericboy0224/learn-docker-and-k8s★ 472same name
- mag123c/toktrack★ 196same name
- buildomator/buildomator★ 102same name
- jantichy/claude★ 45same name
- howells/fiction★ 23same name
- kennethleungty/claude-music★ 23same name
- Hainrixz/claude-db★ 22same name
- grimoire-rs/grimoire★ 15same name
30 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 6 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 36 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
Search for the plan file in order:
- Very specific: line 38
If not found, tell the user: "No MASTER_PLAN.md found.
- Very specific: line 42
Read the file and extract tasks from ### headers matching this pattern:
- Very specific: line 59
Priority: Look in the lines following the header for Priority: P0-P3.
- Distinctive: line 63
Look for IN PROGRESS tasks first — these should be finished before starting new work.
- Very specific: line 70
If uncommitted changes exist, mention: "You have uncommitted changes — consider committing or running /master-plan:save first."
- Very specific: line 84
Use AskUserQuestion to let user pick from the top tasks:
- Distinctive: line 106
If there are IN PROGRESS tasks, always show them first with a note: "You have N task(s) in progress."
- Very specific: line 110
When user selects a task, show the full section from MASTER_PLAN.md:
- Distinctive: line 116
After showing task details, ask:
- Distinctive: line 133
If "Start working on this" is selected:
- Very specific: line 134
Update the task's status to IN PROGRESS in MASTER_PLAN.md (all locations — see update rules below)
- Distinctive: line 145
Always verify with a grep after updating.
“Common” is measured: kept by at least 6 in 10 of the 36 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
What's Next?
Analyze MASTER_PLAN.md tasks, score by priority/status, and let the user pick interactively.
Triggers
/master-plan:next- Main command- "what should I work on", "pick a task", "next task", "what's next"
Arguments
| Argument | Filter |
bugs | Only BUG-XXX tasks |
progress | Only IN PROGRESS tasks |
planned | Only PLANNED (backlog) tasks |
review | Only REVIEW tasks |
active | IN PROGRESS + REVIEW |
all | Include DONE tasks |
Example: /master-plan:next bugs or /master-plan:next planned
Workflow
Step 1: Find MASTER_PLAN.md
Search for the plan file in order:
docs/MASTER_PLAN.mdMASTER_PLAN.mdmaster-plan.mddocs/master-plan.md
If not found, tell the user: "No MASTER_PLAN.md found. Run /master-plan:task to create your first task, or create one from the template."
Step 2: Parse Tasks
Read the file and extract tasks from ### headers matching this pattern:
### [optional ~~]TASK-123[optional ~~]: Title (STATUS)Regex: ^###\s+(~~)?((TASK|BUG|FEATURE|ROAD|IDEA|ISSUE|INQUIRY)-\d+)(~~)?:\s*(.+?)\s*\(([^)]+)\)
For each match, extract:
- ID: e.g.,
TASK-123,BUG-456 - Title: The text after
:and before( - Status: Text in parentheses. Normalize:
- Contains "DONE", "COMPLETE", "FIXED", "✅", or has strikethrough →
DONE - Contains "IN PROGRESS", "🔄" →
IN PROGRESS - Contains "REVIEW", "👀" →
REVIEW - Contains "PAUSED", "⏸️" →
PAUSED - Otherwise →
PLANNED
- Contains "DONE", "COMPLETE", "FIXED", "✅", or has strikethrough →
- Priority: Look in the lines following the header for
**Priority**: P0-P3. Default to P2 if not found.
Step 3: Check for Active Work
Look for IN PROGRESS tasks first — these should be finished before starting new work.
Also check git status:
git status --shortIf uncommitted changes exist, mention: "You have uncommitted changes — consider committing or running /master-plan:save first."
Step 4: Sort and Filter
Default sort order (what to START next):
- PLANNED first, then REVIEW, IN PROGRESS, PAUSED, DONE last
- Within same status: P0 → P1 → P2 → P3
If $ARGUMENTS contains a filter (bugs, progress, planned, review, active), apply it before sorting.
Exclude DONE tasks unless $ARGUMENTS contains all.
Step 5: Present Interactive Selection
Use AskUserQuestion to let user pick from the top tasks:
AskUserQuestion({
questions: [{
question: "Which task would you like to work on?",
header: "Task",
multiSelect: false,
options: [
// Top 4 tasks, formatted as:
{ label: "TASK-XXX: Title here", description: "P0 · IN PROGRESS" },
{ label: "BUG-YYY: Another task", description: "P1 · PLANNED" },
// ...
]
}]
})Option formatting:
- Label:
{ID}: {title (max 40 chars)} - Description:
{priority} · {status}
If there are IN PROGRESS tasks, always show them first with a note: "You have N task(s) in progress."
Step 6: Show Task Details
When user selects a task, show the full section from MASTER_PLAN.md:
- ID, title, status, priority
- Description (everything between this
###header and the next###or##)
Step 7: Offer Actions
After showing task details, ask:
AskUserQuestion({
questions: [{
question: "What would you like to do?",
header: "Action",
multiSelect: false,
options: [
{ label: "Start working on this", description: "Update status to IN PROGRESS" },
{ label: "Pick a different task", description: "Go back to task list" },
{ label: "Just show context", description: "No status change" }
]
}]
})If "Start working on this" is selected:
- Update the task's status to
IN PROGRESSin MASTER_PLAN.md (all locations — see update rules below) - Confirm: "Started TASK-XXX. Ready to begin implementation."
MASTER_PLAN.md Update Rules
Tasks may appear in multiple locations. When updating status, check ALL of:
- Summary/Roadmap table — Update the status column
- Detailed
###section header — Update(STATUS)in parentheses - Subtask bullet points — Add strikethrough + ✅ if marking DONE
Always verify with a grep after updating.
Rules
- Finish before starting — Always highlight IN PROGRESS tasks first
- P0 trumps all — Critical issues come first regardless of status
- Interactive selection — Always use AskUserQuestion, never just print a list
- Context on selection — Always show full task details when picked
- Action oriented — Offer to start work immediately
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

