plan-next
Skill1 starsChanged 4 months agoMITView on GitHub
Continue executing the next phase of a saved plan file. Use when asked to "continue the plan", "do the next phase", "pick up where we left off" against a markdown plan containing "## Implementation phases" (commonly *plan*.md) — typically at the start of a fresh session. Finds the first phase not marked COMPLETED, implements exactly that one, records an Implemented summary, marks it COMPLETED, and stops.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- nesnilnehc/ai-cortextheir own version, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- nesnilnehc/ai-cortex★ 8same name
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.
In this repository21 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-commentsSkill
- ai-draftSkill
- ai-nextSkill
- ai-postSkill
- call-traceSkill
- draft-prSkill
- dto-mappingSkill
- handoffSkill
- hum-commentsSkill
- jira-dcSkill
- meeting-summarySkill
- plan-from-issueSkill
- plan-reviewSkill
- plan-saveSkill
- pr-commentsSkill
- pr-statsSkill
- review-sessionSkill
- skill-builderSkill
- validator-generatorSkill
- templateSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 44
Understand the context: Read the Context section carefully.
- Distinctive: line 50
Implement the phase: Do the work described. Read existing code first before making changes.
- Distinctive: line 52
Update the plan file: when the phase is done:
- Very specific: line 53
Add an #### Implemented subsection at the end of the phase content with a brief, factual summary: files created/modified, key decisions …
- Distinctive: line 56
Stop: Do NOT proceed to the next phase.
- Distinctive: line 60
NEVER enter plan mode: Do NOT use EnterPlanMode or ExitPlanMode.
- Distinctive: line 61
Only work on ONE phase per invocation.
- Distinctive: line 63
If a phase is unclear or blocked, ask the user rather than guessing or improvising.
- Distinctive: line 65
Do NOT modify the Context section or other phases.
- Distinctive: line 66
Do NOT move on to the next phase after completing one — mark it completed and stop.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Plan Next: Execute the next phase of a saved plan
You are resuming work on a structured plan saved to a local file. The plan is ALREADY WRITTEN — do NOT create a new plan or enter plan mode. Your job is to find the next incomplete phase, implement it directly, update the plan file, and stop.
When to use this skill
- A saved plan file exists and you're resuming work on it — typically the first action of a fresh session.
- "Continue the plan" / "do the next phase" / "pick up where we left off".
When NOT to use this skill
- No saved plan exists — use
plan-saveto create one first; this skill executes, it doesn't author. - The user wants the plan changed — that's an edit to the plan file made with the user, not a phase execution. Never enter plan mode.
- The user wants a critique — use
plan-review. - "Run the whole plan" — the contract is one phase per invocation; if asked for more, say so and still do only the next phase (the user can re-invoke).
Steps
- Find the plan file. If an argument was provided, use that as the file path. Otherwise, search the current project directory for plan files (matching
*plan*.md,*PLAN*.md, or any markdown file containing## Implementation phases). If exactly one is found, confirm it with the user. If multiple are found, ask the user which one to use via AskUserQuestion — list them sorted by last-modified (most recent first) and default to the most recently modified file. - Read the entire plan file.
- Understand the context. Read the Context section carefully. This is your only source of background information — there is no prior conversation history.
- Find the next open phase. In the "Implementation phases" section, find the first
###heading that is NOT prefixed withCOMPLETED. This is your current task. - If all phases are COMPLETED, inform the user that the plan is fully implemented and stop.
- Implement the phase. Do the work described. Read existing code first before making changes. Use all available tools. If anything is unclear or blocked, ask the user rather than guessing.
- Update the plan file when the phase is done:
- Add an
#### Implementedsubsection at the end of the phase content with a brief, factual summary: files created/modified, key decisions made, any deviations from the plan. - Prefix the phase heading with
COMPLETED(e.g., change### 3. Create API endpointsto### COMPLETED 3. Create API endpoints).
- Add an
- Stop. Do NOT proceed to the next phase. Report what was accomplished and stop.
Rules
- NEVER enter plan mode. Do NOT use EnterPlanMode or ExitPlanMode. The plan already exists — your job is to EXECUTE it, not re-plan it. Go straight to implementation.
- Only work on ONE phase per invocation.
- Execute phases in order — do not skip phases.
- If a phase is unclear or blocked, ask the user rather than guessing or improvising.
- The
#### Implementedsummary should be factual and concise — what files were touched, what changed, any deviations from the plan. - Do NOT modify the Context section or other phases.
- Do NOT move on to the next phase after completing one — mark it completed and stop.
- NO PLAN DEVIATIONS WITHOUT ASKING. If the planned approach seems difficult, infeasible, or suboptimal, you MUST stop and ask the user before changing the approach. Present the problem, explain why the plan seems hard, and propose alternatives — then let the user decide. NEVER unilaterally replace the planned approach with a different one, even if your alternative passes tests. The plan's approach was chosen for a reason (often architectural, not just functional), and silently deviating can undermine the entire purpose of the phase.
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.

