Planning Prompt
# Planning Prompt
*Version:* v0.5
*Date:* 2026-03-24
*Last reviewed:* 2026-03-24
Goal: propose the thinnest correct plan for a task before implementation expands.
Instructions:
- read the manifesto, charter, `docs/CONTEXT_ENGINEERING.md`, the Codex prompting guide,
task management rules, and only the smallest relevant additional docs first
- restate the task, constraints, and assumptions
- identify which docs, prompts, evals, code, policies, and task artifacts should change
- prefer the simplest design that can satisfy the requirement
- call out verification needs and remaining unknowns
- if the task spans multiple steps, include how `work/` should be updated
Suggested output:
1. Assumptions
2. Proposed slices
3. Risks or open questions
4. Verification plan
5. Task tracking updatewhen to use it
Community prompt sourced from the open-source GitHub repo toniacprado/aidev-repo-template (MIT). A "Planning Prompt" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
toniacprado/aidev-repo-template · MIT
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions