Implementation Plan Creation

Create an implementation plan in docs/plans/yyyymmdd-<task-name>.md with interactive context gathering.

Up Front: End Result Summary (Required)

Before parsing intent or asking detailed questions, require a high-level explanation of the end result with enough detail and specifics for reviewing. This summary must cover:

• What the user will have when the work is done — deliverables, artifacts, and observable behavior
• Key outcomes and how they will be verified or validated
• Concrete specifics that define scope or acceptance — e.g. APIs, UI elements, files, data flows, error handling, edge cases

If the initial request is vague, use the first AskUserQuestion to elicit this summary. Do not proceed to implementation planning until the end-result picture is clear and documented. Use this summary as the reference for reviewing the plan and implementation.

Step 0: Parse Intent and Gather Context

Before asking questions, understand what the user is working on: