Plan a feature before coding
Get an implementation plan with files, steps and tests to review before the agent writes code.
Free to use and change. Filling in and copying happen in your browser.
How it is built
- Goal: Plan how to add this feature: {{feature}}.
- Context: Users need it because {{reason}}. Related code: {{related_code}}.
- Task: Read the relevant code first. Do not edit any files yet.
- Format: A short plan: the approach in two sentences, the files to change and why, the steps in order, the tests to add, and open questions for me.
- Constraints: Prefer existing helpers and patterns over new abstractions. Point out anything that needs a schema or API change.
Tips
- Review the plan, then ask the agent to implement one step at a time.
Read how to write prompts for coding agents for the reasoning behind templates like this. Adapting it? Check your version with the prompt checker.
More coding-agent templates
- Bug fix brief for a coding agent
Find the root cause of a bug, fix it minimally and prove it with a regression test.
- Review a change before merging
A focused review of a diff for bugs, security and missing tests, ranked by severity.
- Write tests for existing code
Add tests that pin down current behaviour, following the project’s test conventions.
- Refactor without changing behaviour
Simplify code in small, safe steps while keeping the tests green.