ds-plan-loop
/ds-plan-loop
Write a numbered plan with an acceptance check for each step, critique it once in a fresh pass, revise it, then execute one step at a time. Use when a task touches more than one file, has unclear scope, or failed before because steps were missed. Invoke as /ds-plan-loop.
- Author
- aicodeking ↗
- Repository
- deepseek-stack ↗
- Licence
- MIT
- Last repository change
- 28.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Write a numbered plan with an acceptance check for each step, critique it once in a fresh pass, revise it, then execute one step at a time. Use when a task touches more than one file, has unclear scope, or failed before because steps were missed. Invoke as /ds-plan-loop.
Original author description
Write a numbered plan with an acceptance check for each step, critique it once in a fresh pass, revise it, then execute one step at a time. Use when a task touches more than one file, has unclear scope, or failed before because steps were missed. Invoke as /ds-plan-loop.
How it works
- Steps
- Stop when
- Rules
SKILL.md preview
--- name: ds-plan-loop description: "Write a numbered plan with an acceptance check for each step, critique it once in a fresh pass, revise it, then execute one step at a time. Use when a task touches more than one file, has unclear scope, or failed before because steps were missed. Invoke as /ds-plan-loop." --- # ds-plan-loop Plan before coding, check the plan once, then build the task one verified step at a time. ## Steps 1. Restate the goal in one sentence. List the files and commands you expect to touch. Read those files before you plan. Do not plan from memory. 2. Write a numbered plan. Each step gets one action and one acceptance check that a command or a direct observation can confirm, for example "`npm test -- auth` passes" or "`GET /health` returns 200". Keep each step small enough to verify in a single diff. 3. Write the plan to a file (PLAN.md, or the PROGRESS.md from ds-context-reset) so later steps and fresh sessions can read it. 4. Critique the plan in a fresh pass. Reread only the goal and the plan, as a reviewer who did not write it. If you can, run the critique in a subagent or new session. Answer three questions: - Which step is missing (setup, migration, config, tests, cleanup)? - Which assumption has not been checked against the code or docs? - Is there a simpler path that reaches the same goal with fewer steps? 5. Revise the plan. Check each risky assumption now by reading code or running a command. Do not carry it forward as a guess. 6. Execute step 1 only. Run its acceptance check and read the real output. Use ds-verify-loop when the check fails. 7. Mark the step done in the plan file, along with the evidence (command and result). Then move to the next step. 8. If a step shows that the plan is wrong, stop and revise the remaining steps before continuing. Do not improvise around it. ## Stop when - Every step is marked done and its check passed, and the original goal holds when you check it end to end. - You have done 2 critique rounds. A third round almost never finds anything new, so execute. - A step fails its check twice in a row. Switch to ds-unstick. ## Rules - No step without a check. "Looks right" is not a check. - Do one step per diff. Do not batch steps to save time. - Do not add steps that the goal does not need. - Keep the plan short: about 3-10 steps. Split bigger work into separate plans.
Versions
The database has no other skills named ds-plan-loop.
Database snapshot: 13.11.2026 · package version a52988d33916 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100st-plan-loop
Write a numbered plan with an acceptance check for each step, critique it once in a fresh pass, revise it, then execute one step at a time. Use when a task touches more than one file, has unclear scope, or failed before because steps were missed. Invoke as /st-plan-loop. - 100execute-plan
Carry out an approved plan step by step, test first, with a check and a progress note per step and a review of the whole change at the end, also in goal mode or with workers. Use it whenever there is a written plan to build from or the user says to go ahead with one. - 92plan-execute
Execute the user's plan that has been iteratively refined, step by step, with resume on failure. Use when the user runs /plan-execute or asks to execute an existing plan. - 84execute-plan
Execute implementation plans step-by-step. Use when user says "execute the plan", "implement the plan we created", "start building based on the plan", "go ahead and implement it", "proceed with the implementation", "execute as a stack", "create a PR stack while implementing",… - 100plan-first
Use for any coding task with more than about three steps or touching more than one file — new features, refactors, migrations, multi-file changes, or vague requests like "build X" or "add Y to the app". Read the code, check memory, write a short plan, then execute step by step with checks. - 90implement
Execute an implementation plan step by step with verification checkpoints and progress tracking. Use when the user asks to "implement the plan", "execute the steps", "start implementing", or has an approved plan ready to implement.