next-step · dotslashsimran — Claude Code skill: planning and installation
The next-step Claude Code skill turns a large goal or an unstructured task dump into one next action. It activates for planning requests or when someone is unsure how to begin.
MIT ★ 541 updated 2026-11-09
npx skills add dotslashsimran/simcraft --skill next-step -a claude-codeWhat next-step does
The skill gathers the details of a goal, asks clarifying questions one at a time, then writes a plan to plan.md in the current folder or a folder the user names. The file holds the deadline, completion criteria, ordered actions with time estimates, and anything blocked by another person. Tasks outside the goal go under Not now.
Only the next action appears in the response. Each action starts with a verb, takes no more than 25 minutes, and says what completion looks like. Once a step is done, the skill marks it in the file and presents the next one. If progress stalls, it breaks the action into smaller pieces. The full plan remains available in plan.md.
This is not a calendar or project-management system. In Claude Code, install it with npx skills add dotslashsimran/simcraft --skill next-step -a claude-code.
What it helps with
- turn a large goal into short actions
- choose a first task from a messy list
- track completed steps in a plan file
- set aside tasks unrelated to the current goal
Example prompts for the agent
- Help me get started on a launch plan and show one action at a time.
- Here is everything on my mind about the job hunt. Make a plan and give me the first step.
- Break the move into small actions and keep the plan in
plan.md.
How to install next-step
1Skills CLI (Vercel)
npx skills add dotslashsimran/simcraft --skill next-step -a claude-code2Manually: put the files in place
~/.claude/skills/next-step/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/next-step/
1Skills CLI (Vercel)
npx skills add dotslashsimran/simcraft --skill next-step -a codex2Manually: put the files in place
.agents/skills/next-step/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dotslashsimran/simcraft --skill next-step -a cursor2Manually: put the files in place
.cursor/skills/next-step/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dotslashsimran/simcraft skills/planning/next-step2Manually: put the files in place
.github/skills/next-step/SKILL.md1Skills CLI (Vercel)
npx skills add dotslashsimran/simcraft --skill next-step -a gemini-cli2Platform CLI
gemini skills install https://github.com/dotslashsimran/simcraft --path skills/planning/next-stepManually: put the files in place
.devin/skills/next-step/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about next-step
How do I install next-step in Claude Code?
Run npx skills add dotslashsimran/simcraft --skill next-step -a claude-code. The skill file is at ~/.claude/skills/next-step/SKILL.md.
What does next-step do?
It turns a large goal or task dump into a plan, then presents one small action at a time. The plan lives in plan.md, where completed steps are checked off.
What happens if I get stuck on a step?
The skill splits the action into smaller pieces until the first part takes about five minutes. If the same step stalls twice, it asks what is blocking progress.
Source text
SKILL.md · MIT
---
name: next-step
description: Turn a big, messy goal or a brain dump into one clear next action at a time, for people who freeze in front of long to-do lists (ADHD-friendly). Asks one question at a time, keeps a small plan file, and only ever shows the single next step plus how long it takes. Use when the user says "I don't know where to start", "help me plan", "I'm overwhelmed", "what should I do next", "break this down", dumps a pile of tasks, or asks for a plan for a launch, a move, a job hunt or a project.
---
# Next step
A long plan is a wall. Most people who ask "where do I start" already know the twenty things they have to do. What they need is the **one** thing they can do in the next 25 minutes, and someone holding the rest of the list so they don't have to.
So this skill does the planning in the background and shows the user one step at a time.
## Rules
- **One question at a time.** Never a numbered list of questions. Ask the one whose answer changes the plan most, wait, then ask the next.
- **One step at a time.** Show the next action only. The full plan lives in the file, and the user can open it if they want it.
- **Every step is a physical action that starts with a verb** and is small enough to finish in 25 minutes or less. "Work on the portfolio" is not a step. "Open the portfolio doc and write a one-line headline" is.
- **Say how long it takes and what "done" looks like.** "About 10 minutes. Done when the email is in drafts."
- **No guilt.** Never mention what is overdue or how much is left unless they ask.
## The pass
1. **Dump.** Ask the user to dump everything on their mind about the goal, in any order, as messy as they like. Voice-note style is best. Don't interrupt and don't organise yet.
2. **One goal.** Reflect the goal back in one sentence ("So the goal is: send 10 job applications by Friday"). Ask one question if the goal, the deadline or what "finished" means is unclear.
3. **Plan, quietly.** Write the plan to `plan.md` in the current folder (or the folder the user names):
- **Goal**, **deadline**, and **done means**.
- **Steps**, in order, each with a verb, a time estimate, and a done check.
- **Blocked**: anything waiting on someone else, with who and what.
- **Not now**: everything from the dump that doesn't serve this goal. Parking it here is what lets the user stop thinking about it.
Order steps so the first one is the easiest real progress. Momentum beats importance for the first step.
4. **Show one step.** Show only:
> **Next:** Write the subject line and first sentence of the email to Priya.
> About 10 minutes. Done when it's saved in drafts.
Then stop and wait.
5. **Loop.** When they say done, tick it in `plan.md` (`- [x]`), say one short line of acknowledgement, and show the next step the same way. If they're stuck, make the step smaller, not the deadline longer: split it until the first piece takes five minutes.
6. **Change of plan.** If they bring something new, ask one question: "Is this part of the goal, or should it go in Not now?" Then update the file.
## When they're stuck or avoiding it
- Make it smaller: "Just open the file and write the title. That's the whole step."
- Make it easier to start: suggest a 10 minute timer, or doing it badly on purpose first.
- If the same step stalls twice, ask what's in the way (one question). It's usually a hidden decision or a missing piece of information. Turn that into its own step.
## What it isn't
Not a project management tool, not a calendar, and not a lecture about productivity. If the user wants the whole plan, show `plan.md`. Otherwise, one step.
© dotslashsimran · MIT · dotslashsimran/simcraft
Similar skills
All skills for Agent setup: memory, context, orchestration →next-step by other authors comes first.