Prepare Implementation Plan

Produce an implementation plan whose every goal is verifiable (mapped to an acceptance criterion and a concrete check) and whose files-changed list is derived from the actual code, not guessed.

Step 1 — Ingest & classify the input

Get the work to be planned. Try sources in this order; stop at the first that works:

1. Azure DevOps MCP — if an ADO / Azure DevOps work-item MCP tool is connected, fetch by work-item ID.
2. az boards CLI — az boards work-item show --id <id> --output json. For a parent feature/epic, follow its child links and pull each child's fields.
3. What the user brings — a story pasted in, or a rough idea in their own words. Take it as-is.

Then classify it — the input varies from a formed story to a half-baked spark, and the next step routes on which:

• Formed — acceptance criteria exist (explicit or obvious). Capture ID (if any), title, description, and the acceptance criteria verbatim.
• Rough — an idea with no acceptance criteria. Capture the spark as-is; forging the criteria is the grill's first job in Step 2, not a blocker here.

Completion criterion: the input is captured and classified formed-or-rough; for a formed item, its full acceptance-criteria text is captured verbatim.