Agent skill

Dr Plan Steps

by AHepi in AHepi/DeepReason

Convert an approved SPEC.md into an ordered, checkable step list (CHECKLIST.md) where each step has one done-criterion.

MITAuto-check passed

Install Dr Plan Steps

skills CLI
$ npx skills add AHepi/DeepReason --skill dr-plan-steps -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install AHepi/DeepReason dr-plan-steps --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/AHepi/DeepReason.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/dr-plan-steps .claude/skills/dr-plan-steps && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
dr-plan-steps
GitHub stars
141
Token cost
~981 tokens
SKILL.md length
542 words
Files
1
Skills in repo
30
Repo updated
First seen
Licence
MIT

At a glance

Convert an approved SPEC.md into an ordered, checkable step list (CHECKLIST.md) where each step has one done-criterion.

  • Works in 7 steps: Dependencies first, verification… → One step = one action with ONE… → Include the boring steps that get… → …
  • SKILL.md covers Ordering rules, CHECKLIST.md template, Re-planning after a validation… and Exit criteria
  • Calls pytest and git

What it does

Dr Plan Steps is an agent skill from AHepi/DeepReason. Convert an approved SPEC.md into an ordered, checkable step list (CHECKLIST.md) where each step has one done-criterion. Use after SPEC.md, and again (partial re-plan) after a validation failure.

Its SKILL.md is about 980 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The licence is MIT.

Example prompts

  • “/dr-plan-steps”

Requirements

  • Python 3

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Dependencies first, verification interleaved: a step that writes a
  2. One step = one action with ONE done-criterion (a command and its
  3. Include the boring steps that get forgotten — they are the point of
  4. Every step cites its spec item (S-number). A step with no S-number
  5. Scope from the map before planning steps. Open
  6. Plan the map update as part of the step that changes behaviour,
  7. Mark checkpoint steps [COMMIT] at natural boundaries (at minimum

What it can do on your machine

Read from SKILL.md and the folder at commit 9607fba. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pytest
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Dr Plan Steps loads about 981 tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 542 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~52
When it runs · the whole SKILL.md, loaded when a task matches
~981

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from AHepi/DeepReason at commit 9607fba, republished under its MIT licence (© AHepi). 542 words, ~981 tokens.

Download SKILL.mdSave it as .claude/skills/dr-plan-steps/SKILL.md (or your agent's skills folder).
name
dr-plan-steps
description
Convert an approved SPEC.md into an ordered, checkable step list (CHECKLIST.md) where each step has one done-criterion. Use after SPEC.md, and again (partial re-plan) after a validation failure.

Plan the steps

Input: SPEC.md (re-read REQUEST.md and SPEC.md in full first). Output: CHECKLIST.md — the complete ordered path from the current tree to the accepted change. Execution will do NOTHING that is not a step here, so missing steps here means missed work later. Plan against that.

Ordering rules

  1. Dependencies first, verification interleaved: a step that writes a test precedes the step whose change it guards; a step that runs a check follows immediately after the change it checks — not batched at the end where failures lose their cause.
  2. One step = one action with ONE done-criterion (a command and its expected output, or "file exists containing <marker>"). If a step needs the word "and", split it.
  3. Include the boring steps that get forgotten — they are the point of this skill: creating directories, chmod +x, updating the ladder or docs SPEC says to update, retiring an occupied run root (rename commit FIRST), the subsystem test ring, the FULL gate (pytest tests/ -q -n 4, expect 0 failed), the tranche commit with its message, the push with retry, and the final git status --porcelain cleanliness check.
  4. Every step cites its spec item (S-number). A step with no S-number is scope creep — delete it or send it to PARKED.md.
  5. Scope from the map before planning steps. Open docs/map/INDEX.md, resolve the change to DR-SUB-/DR-CON-/ DR-SEAM- ids, and read the seam document before the subsystem ones — the file is docs/map/SEAM-<a>-x-<b>.md, sides in alphabetical order, and the worked recipe for a seam change is docs/map/REC-change-a-seam.md. Name those ids in CHECKLIST.md's header so execution starts from the same map the plan was built on. A change whose ids you cannot name is a change you have not scoped.
  6. Plan the map update as part of the step that changes behaviour, never as a trailing "update docs" step. A trailing documentation step is the one that gets dropped when a tranche runs long. If a seam document must be CREATED, that is its own step, and it comes BEFORE the code steps — writing down the agreement is how you find out whether you understand it.
  7. Mark checkpoint steps [COMMIT] at natural boundaries (at minimum: after tests-written, after each spec item lands, after the gate) — rationale canonical in dr-drive-harness §1.
Show full SKILL.md (62 more words)Show less

CHECKLIST.md template

# Checklist for: <request headline>
State: next=<step n> blockers=<none | one line>   <- refreshed at
every commit; a fresh session resumes from this line alone
Re-read REQUEST.md + SPEC.md before every step. Execute strictly
in order. One step per dr-execute-step invocation.

- [ ] 1. (S1) <action>
      done-when: <command> -> <expected>
- [ ] 2. (S1) [COMMIT] <action>
      done-when: ...
- [ ] 3. (S2) ...
...
- [ ] N-2. (all) Map check: python tools/docs_verify.py
      done-when: 0 failed, and --audit reports 0 findings
- [ ] N-1. (all) Full gate: pytest tests/ -q -n 4
      done-when: output ends "N passed, 0 failed" (paste it)
- [ ] N. (all) [COMMIT] push and confirm clean tree
      done-when: git status --porcelain is empty AND branch head
      is on origin

Re-planning after a validation failure

Touch only the steps implicated by the failure: append new steps (N+1...) that correct course; never rewrite history of checked steps — their pasted outputs are the audit trail.

Exit criteria

  • CHECKLIST.md committed and pushed; every S-number covered by >=1 step; every step has a done-criterion.
  • No code changed in this phase.
  • Return to the orchestrator.

© AHepi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/dr-plan-steps of AHepi/DeepReason.

Open the folder on GitHubat commit 9607fba

Compare with similar skills

Dr Plan Steps next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Dr Plan Steps compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dr Plan Steps this skillAHepi/DeepReason141—~981Automated safety check: PassMIT
Convertremotion-dev/remotion62k—~247Automated safety check: PassCustom licence
Os Step By Stepkharmanskyi/open-steps1.2k—~1.9kAutomated safety check: PassMIT
Structured Step By Step Reasoningaiming-lab/MetaClaw3.5k—~212Automated safety check: PassMIT
Operator Approval Loopaffaan-m/ECC274k—~3.3kAutomated safety check: PassMIT
CSS Orderthedaviddias/Front-End-Checklist74k—~404Automated safety check: PassMIT

Similar skills

  • Convert

    remotion-dev/remotion

    Official

    Start the local @remotion/convert app and open it in the Codex browser.

    62k GitHub stars~247 tokensUpdated today
    Media & CreativeAuto-check passed
  • Os Step By Step

    kharmanskyi/open-steps

    ALWAYS invoke this skill when you need the user to act - run a command, paste a secret, click, approve - and whenever they ask how to do something or say they do not know what to do: "step by step"…

    1.2k GitHub stars~1.9k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed
  • A skill your agent uses for any problem that involves multiple steps, tradeoffs, or non-trivial logic.

    3.5k GitHub stars~212 tokensUpdated 4 mo ago
    AI & LLM EngineeringAuto-check passed
  • Operator approval contract with internal filing notices for agent-drafted outbound messages, hashed drafts, epoch-keyed decisions, durable delivery claims and receipts, and a pre-draft baseline gate.

    274k GitHub stars~3.3k tokensUpdated 2 days ago
    Auto-check passed
  • CSS Order

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Order CSS files correctly.

    74k GitHub stars~404 tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Focus Order

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure logical focus order.

    74k GitHub stars~519 tokensUpdated yesterday
    Frontend & DesignAuto-check passed

More from AHepi/DeepReason

All 30 skills in this repo
  • Pinker Clarity Workflow

    AHepi/DeepReason

    Orchestrate a Steven Pinker-grounded workflow for teaching, explanatory writing, or material that must do both.

    141 GitHub stars~1.5k tokensUpdated 27 days ago
    Auto-check passed
  • Design, deliver, or audit explanations and lessons with a Pinker-informed focus on phenomena, the curse of knowledge, concrete models, active reasoning, feedback, and revision.

    141 GitHub stars~1.8k tokensUpdated 27 days ago
    Auto-check passed
  • Pinker Write For Readers

    AHepi/DeepReason

    Draft, revise, teach, or audit expository prose using Pinker's cognitive approach to style: classic presentation, reader modeling, curse-of-knowledge repair, coherent information order, deliberate…

    141 GitHub stars~2.1k tokensUpdated 27 days ago
    Auto-check passed
  • Example Battery

    AHepi/DeepReason

    Build a battery of concrete instances BEFORE writing or evaluating any definition, pin, or semantic clause (Reed step 1).

    141 GitHub stars~811 tokensUpdated 27 days ago
    Auto-check passed
  • Authoring Skills

    AHepi/DeepReason

    Rules for writing, editing, and retiring skill and workflow files for LLM agents.

    141 GitHub stars~1.7k tokensUpdated 27 days ago
    Auto-check passed
  • Deepreason Orchestrator

    AHepi/DeepReason

    Entry point for any DeepReason problem. An agent skill from AHepi/DeepReason.

    141 GitHub stars~1.1k tokensUpdated 27 days ago
    Auto-check passed

Questions about Dr Plan Steps

What does Dr Plan Steps do?

Convert an approved SPEC.md into an ordered, checkable step list (CHECKLIST.md) where each step has one done-criterion. Dr Plan Steps is an agent skill from AHepi/DeepReason.md) where each step has one done-criterion.

How do I install Dr Plan Steps in Claude Code?

Run `npx skills add AHepi/DeepReason --skill dr-plan-steps -a claude-code`. Or copy the skill folder (.claude/skills/dr-plan-steps in AHepi/DeepReason) into .claude/skills/dr-plan-steps in your project. Claude Code loads it when a task matches its description.

How do I install Dr Plan Steps in Codex?

Run `npx skills add AHepi/DeepReason --skill dr-plan-steps -a codex`. Or copy the skill folder (.claude/skills/dr-plan-steps in AHepi/DeepReason) into .agents/skills/dr-plan-steps in your project. Codex loads it when a task matches its description.

Can I use Dr Plan Steps in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AHepi/DeepReason --skill dr-plan-steps -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dr-plan-steps, .gemini/skills/dr-plan-steps, .github/skills/dr-plan-steps and .opencode/skills/dr-plan-steps in your project.

What does Dr Plan Steps need to run?

Going by SKILL.md and its folder, Dr Plan Steps needs the command-line tools its instructions call (pytest and git). Our summary lists: Python 3.

Does Dr Plan Steps access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Dr Plan Steps safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Dr Plan Steps use?

Dr Plan Steps is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Dr Plan Steps use?

About 981 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Dr Plan Steps?

Skills that share tags, products or a category with Dr Plan Steps: Convert (remotion-dev/remotion, 62k stars), Os Step By Step (kharmanskyi/open-steps, 1.2k stars), Structured Step By Step Reasoning (aiming-lab/MetaClaw, 3.5k stars) and Operator Approval Loop (affaan-m/ECC, 274k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dr Plan Steps?

AHepi (a GitHub user) maintains it in AHepi/DeepReason, which has 141 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on September 10, 2026.

Source: AHepi/DeepReason on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.