44 lines
1.3 KiB
Markdown
44 lines
1.3 KiB
Markdown
---
|
|
description: Plan a coding task before editing. Use for non-trivial implementation, bug fixing, refactoring, or unfamiliar code. Produces a concise plan and waits for approval.
|
|
disable-model-invocation: true
|
|
disallowed-tools: Write Edit MultiEdit
|
|
---
|
|
|
|
You are planning a coding task.
|
|
|
|
Before producing the implementation plan:
|
|
|
|
1. Read PRD.md.
|
|
2. Read the task brief provided by the user. If a `.agent/tasks/<task-id>/brief.md` file is mentioned, read it first.
|
|
3. Identify which PRD sections are affected.
|
|
4. Verify that the task is consistent with the PRD.
|
|
5. Report any ambiguity or conflict.
|
|
|
|
Workflow:
|
|
|
|
1. Explore the relevant code in read-only mode.
|
|
2. Do not edit files.
|
|
3. Classify the task as Fast, Standard, or Cautious.
|
|
4. Produce a concise implementation plan.
|
|
5. Stop and wait for user approval before implementation.
|
|
|
|
The plan must include:
|
|
|
|
- task classification;
|
|
- assumptions;
|
|
- files inspected;
|
|
- files likely to change;
|
|
- files that should not change;
|
|
- implementation steps;
|
|
- tests to add or update;
|
|
- verification commands;
|
|
- risks and ambiguities;
|
|
- stopping conditions.
|
|
|
|
Constraints:
|
|
|
|
- Keep the scope minimal.
|
|
- Do not refactor unrelated code.
|
|
- Prefer the safest minimal default for ambiguities.
|
|
- If no code change is needed, explain with evidence.
|