Claude Skills for ADHD: Break Work Into Manageable Steps

ADHD often makes it hard to start a task, continue after an interruption, or decide where the work stands at the end of a session. Reusable Claude skills can help with all three because they replace the decision about what to ask with a single call to a named instruction you already trust.

A skill is a saved prompt in a Claude Project. You write the instruction once, give it a name, and call it again whenever you need that output. Tools like fenbs store your skills alongside the task notes and progress records, so both the instruction and the context survive between sessions.

Why saved instructions help when starting is hard

One reason starting a task is hard is the cost of deciding how to begin. A blank prompt takes effort. A named skill removes that decision: you open the project, call the skill by name, and get the first concrete step.

The same applies to interruptions. When you come back after a break, opening a conversation and asking "where was I?" is vague. A skill called something like "Restart my session" can prompt Claude to read the last saved state and give you a clear next step. That transition from nothing to something is where a saved instruction saves the most time.

Skills are also easy to adjust. If a breakdown skill gives too many steps at once, edit it to ask for three at a time. You control the output size, and you only have to make that decision once.

A skill for breaking a large task into steps

A task breakdown skill takes a goal and returns a short, ordered list of concrete next actions. The key is to ask for a small number of steps. A list of fifteen items is as paralyzing as no list at all.

Break the following task into steps I can do one at a time.

Task: {{task}}

Rules:
- Give me no more than five steps
- Each step starts with a verb
- Each step is something I can do in under 30 minutes
- If a step is still too big, break it into sub-steps under it

Output a numbered list only.

You can make the step size smaller ("under 10 minutes") or ask Claude to flag the step most likely to cause a block. Adjust the instruction once and every future call reflects the change. See Claude skills examples for more patterns.

A skill for restarting after an interruption

When you return to a task after a break, you need two things fast: what was done and what to do next. A restart skill gives you both in a sentence each, with no searching through chat history.

I am returning to a task after a break. Help me restart.

Last saved state: {{paste the Where we left off note, or a short summary}}

Give me:
1. One sentence: what was completed
2. One sentence: what is still open
3. The single next step I should take right now

Keep the total response under 100 words.

The skill works best when the "last saved state" is actually saved. Before you stop working, use a short close-out skill (see the next section) to write the state so it is ready when you come back.

A skill for closing out a session cleanly

Ending a session without recording where things stand means the restart skill has nothing useful to read. A close-out skill prompts you to capture the minimum needed to start again without friction.

I am finishing a work session. Help me save my progress.

Task: {{task name}}

Answer these four questions in one sentence each:
1. What did I complete in this session?
2. What is still open?
3. What is the single next step for the next session?
4. Is anything blocking me or waiting on someone else?

Keep each answer to one sentence.

Copy the output into your task notes or ask Claude to save it to the project context if you are using fenbs with MCP connected. Either way, the restart skill has something concrete to read next time.

Building a routine around the three skills

The three skills work best as a connected routine: close out at the end of a session, restart at the beginning of the next. The gap between sessions, whether it is an hour or three days, costs less when the restart gives you one clear next step rather than requiring you to reconstruct the whole context from memory.

Starting this as a habit is easier than starting it as a rule. Pick one project to try it on for a week. Run the close-out skill at the end of every session on that project. Run the restart skill at the beginning of every new one. After a few sessions you will know whether the overhead of the close-out is worth the recovery speed.

If the close-out skill produces too much output, edit it to ask fewer questions. If the restart skill does not give you enough context, edit it to include more of the saved state. You control the granularity, and you only adjust it once. The skill carries the adjustment into every future session without further effort.

How to do this with fenbs

1. Create a free account and add a project for the work you do most often.
2. Go to Skills and prompts in that project and add each skill by name: "Break down task", "Restart session", "Close out session".
3. Connect Claude over MCP from Integrations. At the start of each session, ask Claude to list the available skills.
4. At the end of each session, call the close-out skill and ask Claude to save the output as Where we left off for this project.
5. When you return, call the restart skill and paste or ask Claude to read the last saved note.

fenbs does not run skills automatically. You call them when you need them. The skills and the session notes stay in the project, so switching devices, models, or AI apps does not lose the context. See how to create a Claude skill for the full setup process.

For skill collections covering specific work types, see Claude skills for project management. For a broader look at where skills fit in Claude, see Claude Projects vs Skills vs Artifacts. You can also explore the claude skills marketplace and claude desktop skills for more ready-made examples.