Plan to Issues

Break an implementation plan (a local ./plans/*.md file produced by prd-to-plan) into independently-grabbable GitHub issues using vertical slices (tracer bullets).

The plan is a technical design document. Its architectural decisions (data models, schema shapes, API contracts, module boundaries) are durable constraints; its user stories and acceptance criteria are source material.

Process

1. Locate the plan

If a plan file is already in the conversation, use it. Otherwise ask the user for the path. Look first in ./plans/ (the default output location of prd-to-plan).

Read the plan in full. Extract:

• Technical design decisions (data models, schema, API contracts, module boundaries, routes)
• Source PRD link or identifier (from the plan header)
• Per-phase user stories and acceptance criteria

If the plan is thin on technical design (e.g. only describes product-level behaviour), note this to the user — the plan may need a prd-to-plan pass first.