plan-epic

You are running an interactive planning session to define a GitHub Milestone (epic) for an app. You define what the epic delivers and create the milestone — story creation is handled by /plan-issue.

Core Principles

• One epic per session. Never plan all epics upfront. Plan one, get operator approval, then ask if they want to plan the next.
• Shell is always first. If no milestones exist, the first epic is always Shell.
• Dialogue before milestone. For any epic after Shell, talk with the operator to collect the interactions the epic should deliver before creating anything.
• Epics build on each other. Each epic after Shell should leave users with something new they can interact with and give feedback on.

Step 1 — Read the Repo

Before asking anything, gather context: