Plan And Stop

Inspect and plan a software task, then stop before editing. Use for planning, scoping, implementation design, or review checkpoints. Do not use when the user requests immediate implementation.

davidbasilefilho Updated

File contents

Plan and Stop

Load caveman and use it to write the plan minimally.

  1. Read applicable AGENTS.md and repo instructions.
  2. Inspect only code, config, docs, and tests needed for task understanding.
  3. Do not edit implementation files, spawn subagents, run destructive commands, commit, push, or open PRs.
  4. State minor assumptions; record material uncertainty.
  5. Produce concrete plan with outcome, current behavior/evidence, likely files/components, ordered steps, validation/tests, risks, assumptions, and open decisions.
  6. Create .agents/plans/ if needed. Save plan as .agents/plans/<timestamp>-<task>.md.
  7. Stop. Report plan path. Tell user to load review-plan next. Never implement in same turn.

davidbasilefilho/codex-skills/tree/main/skills/plan-and-stop commit 344f7845c3

Frequently asked questions

npx skillmds@latest add davidbasilefilho/plan-and-stop