plan

/plan - Create Phased Execution Plan

You must create a phased plan document immediately.

Before creating or updating the plan or any supporting Markdown deliverable, apply .github/instructions/document-frontmatter.instructions.md. The YAML frontmatter block must be the first content in the file. New documents require Original Author, Creation Date, and Creating Model; updated documents must preserve those fields and add or update Last Author, Last Updated, and Last Model Used.

Input

User's request: {{input}}

If {{input}} is empty, ask: "What feature or task do you need a phased plan for?"

---

Step 1: Analyze Scope

Quickly assess the work:

1. Read relevant files to understand current state
2. Identify components that need creation/modification
3. Estimate complexity - is this truly multi-session work?

If work can be completed in ONE session (< 1 hour):
  → Tell user: "This is single-session work. Proceeding directly."
  → Do the work instead of creating a plan.

If work requires MULTIPLE sessions:
  → Continue to Step 2.

---

Step 1b: Requirements & Constraints

Before designing phases, capture key requirements and constraints that shape the plan:

- REQ-001: [Functional requirement]
- SEC-001: [Security requirement]
- CON-001: [Constraint - tech, time, infrastructure]
- PAT-001: [Pattern to follow from existing codebase]

This ensures nothing is missed during phase design.

---

Step 2: Design Phases

Break work into independently completable phases:

Phase Sizing Rules

Phase Size	Guideline
Too small	Combined into previous phase
Ideal	30-60 minutes work, clear completion point
Too large	Split into sub-phases

Phase Types (Common Patterns)

Foundation Phase:  Data models, adapters, configuration
Core Phase:        Business logic, services, main functionality  
UI Phase:          Pages, components, styling
Integration Phase: Connecting pieces, end-to-end testing
Polish Phase:      Error handling, edge cases, documentation