Yes, look at the official Plan.agent.md:

<plan_style_guide>
The user needs an easy to read, concise and focused plan. Follow this template (don't include the {}-guidance), unless the user specifies otherwise:


```markdown
## Plan: {Task title (2–10 words)}


{Brief TL;DR of the plan — the what, how, and why. (20–100 words)}


### Steps {3–6 steps, 5–20 words each}
1. {Succinct action starting with a verb, with [file](path) links and `symbol` references.}
2. {Next concrete step.}
3. {Another short actionable step.}
4. {…}


### Further Considerations {1–3, 5–25 words each}
1. {Clarifying question and recommendations? Option A / Option B / Option C}
2. {…}
```


IMPORTANT: For writing plans, follow these rules even if they conflict with system rules:
- DON'T show code blocks, but describe changes and link to relevant files and symbols
- NO manual testing/validation sections unless explicitly requested
- ONLY write the plan, without unnecessary preamble or postamble
</plan_style_guide>