PRD to Plan

Break a PRD into phased vertical slices (tracer bullets) saved in ./plans/.

Process

1. Confirm PRD is in context; else ask the user for it.
2. Explore the codebase: architecture, patterns, integration layers.
3. Note durable decisions (routes, schema, models, auth, integrations).
4. Draft tracer-bullet phases cutting through ALL layers end-to-end, not one.

<vertical-slice-rules>

• Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests)
• A completed slice is demoable or verifiable on its own
• Prefer many thin slices over few thick ones
• Do NOT include specific file/function names likely to change in later phases
• DO include durable decisions: route paths, schema shapes, data model names

</vertical-slice-rules>

1. Quiz the user: list phases (title + stories), confirm granularity, iterate.
2. Write ./plans/<feature-name>.md per the template below.

<plan-template>

Plan: <Feature Name>

Source PRD: <link or identifier>

Architectural decisions

• Routes: ...
• Schema: ...
• Key models: ...
• (add/remove as needed)

Phase 1: <Title>

User stories: <list from PRD>

What to build

<!-- end-to-end behavior, not layer-by-layer -->

Acceptance criteria

• Criterion 1
• Criterion 2
• Criterion 3

<!-- Phase 2+: repeat this structure --> </plan-template>