Template: Story Plan

This template is used during Phase B of the Use Case to UX workflow. Copy it to your project directory and fill in the <!-- REPLACE: ... --> placeholders. Create one story plan per story.

When filled in, the document title should follow the pattern: Story Plan: <Story Title>.

---

Section 0: Preconditions

The following infrastructure must exist before implementation begins. Verify each item is in place before writing any code. If an item is missing, stop and raise the gap as a question in Section 6.

Asset	Location	Description

---

Section 1: Objective

What This Story Covers

What This Story Does NOT Cover

---

Section 2: Element Classification

2.1 Reused As-Is

Elements imported from existing libraries or other repositories without modification.

Element	Import Path	Used For

2.2 Reused from Previous Stories

Elements defined in earlier stories in the same domain that are imported by this story.

Element	Location	Used For	Modified?

2.3 Created or Modified — Shared

2.4 Created — Private to This Story

---

Section 3: File Inventory

Create

File	Type	Notes

Modify

File	Change Description	Reason

Delete

File	Reason

---

Section 4: Implementation Steps

1. Verify preconditions — confirm every asset in Section 0 exists at its declared location. If any asset is missing, stop and raise an open question in Section 6.

6. Final verification — run the full check suite from the repository root:

   npm run lint
   npx tsc --noEmit
   npm run test -- --testPathPattern="<!-- REPLACE: story file pattern -->"

   All three must pass before committing.

7. Commit — commit all files created or modified in this story with the message:

   feat(<!-- REPLACE: domain -->): implement <!-- REPLACE: story display name --> story
   
   Co-Authored-By: <!-- REPLACE: agent co-author line -->

---

Section 5: Risk Notes

Risk	Mitigation

---

Section 6: Open Questions

#	Question	Options	Recommendation	Decision
1

---