writing-plan
Overview
Write an execution-ready handoff for a skilled engineer unfamiliar with the repository. Ground tasks in repository evidence, dependencies, verification, and observable acceptance criteria. Preserve user requirements, overrides, and approved decisions; leave routine implementation choices to the implementer.
Output Mode
Honor an explicitly requested format or filename. Otherwise, default to Markdown. Produce both formats only when explicitly requested.
Write the plan artifact to the OS temporary directory by default, resolving that directory through the host environment (for example, tempfile.gettempdir() or os.tmpdir()). Use a directory requested by the human instead, including a directory supplied as part of the output path. A filename alone changes the name, not the default directory. Report the resolved artifact path in the handoff.
- For Markdown, write
plan-${implementation-task}.mdusing a kebab-case task slug. - For HTML, write
plan-${implementation-task}.htmlusing the same slug. Before writing, read HTML Plan Artifact Guidance, Plan Artifact Skeleton, and Plan Artifact Panel Reference, then use their contract and scaffold.
Required Plan Contract
Expose these sections in order: