aicodeking/deepseek-stack

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.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/aicodeking/deepseek-stack --skill ds-plan-loop

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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?
  1. Revise the plan. Check each risky assumption now by reading code or running a command. Do not carry it forward as a guess.
  2. Execute step 1 only. Run its acceptance check and read the real output. Use ds-verify-loop when the check fails.
  3. Mark the step done in the plan file, along with the evidence (command and result). Then move to the next step.
  4. 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.
同じリポジトリから

関連する Skills

すべての Skills
aicodeking
コミュニティ

ds-adopt

Takes over an existing PR, branch or agent thread and finishes its original goal while keeping credit for the first contributors. Use when the user says take over, adopt, pick up or finish this PR, or /ds-adopt.

1時間の導入数
2
GitHub Stars
75
更新日
10月28日
aicodeking
コミュニティ

ds-best-of-n

Run N independent attempts at the same task in parallel, pick the strongest as the base, and graft the best parts of the others into it. Use when one attempt at a non-trivial artifact could land on the wrong shape, or for /ds-best-of-n, 'try a few versions', 'best of 3'.

1時間の導入数
2
GitHub Stars
75
更新日
10月28日
aicodeking
コミュニティ

ds-blast-radius

Find what a change could break outside its own diff, then prove the key safety fact by running real code. Use before shipping a risky or untrusted change, for 'what could this break', 'blast radius of X', or /ds-blast-radius.

1時間の導入数
2
GitHub Stars
75
更新日
10月28日
aicodeking
コミュニティ

ds-blueprint

Design the types, function signatures and module layout first, agree on that shape, then implement against it. Use when work is non-trivial and coding straight away would lock in the wrong structure, or for /ds-blueprint, 'design this first', 'architect this'.

1時間の導入数
2
GitHub Stars
75
更新日
10月28日