Epic to Features

Break an Epic down into its full set of Features and create them one by one. Core value: proposes the complete feature list upfront, then walks through writing each Feature with full user control.

Process

0. GitHub CLI setup

Run the setup check from ../references/gh-setup.md. Stop if gh is not installed or not authenticated. Note whether the extensions are available — this determines whether native sub-issue and dependency links are created downstream (via wtf.write-feature and wtf.write-task).

Skip this step if gh-setup was already confirmed this session (e.g. when chained from wtf.write-epic).

1. Identify the Epic

If an Epic number was passed in as context, use it directly. Otherwise call AskUserQuestion (per ../references/questioning-style.md):

• question: "Which Epic are you breaking into Features?"
• header: "Epic"
• options: from recent open Epics via gh issue list --label epic

Fetch the Epic with gh issue view <epic_number> and extract: Goal, Context, and Success Metrics.

List Features already created under this Epic via gh sub-issue list <epic_number> per the cookbook in ../references/gh-setup.md. Note which Features already exist — do not re-propose or re-create them.

2. Propose the full Feature list

Based on the Epic's Goal, Context, and Success Metrics, derive a proposed list of Features that together deliver the Epic's outcome. Each Feature must follow the pattern: [Domain Actor] can [domain verb] [domain object].

If the Epic already has partially-created Features (found via gh sub-issue list), open the list with a note: "Epic #N already has [X] Features created: [list with issue numbers]. Here are the remaining Features I'd propose:"

Present the remaining (or full, if none exist yet) list as plain numbered text, for example:

Here are the Features I'd propose for this Epic:

1. Merchant can view settlement status for a completed payment
2. Merchant can filter settlements by date range
3. Finance Manager can export settlement report as CSV
4. System notifies Merchant when settlement is delayed

Then call AskUserQuestion (per ../references/questioning-style.md):

• question: "Does this list look complete? You can add, remove, or rename any Feature before we start."
• header: "Feature list"
• options:
  • Looks good → proceed with this list
  • Make changes → add, remove, or rename a Feature

Wait for the user to confirm or adjust the list. Apply any changes.

3. Walk through Features one by one

For each Feature in the confirmed list, in order:

1. Announce: "Creating Feature [N/total]: [capability name]"
2. Follow the wtf.write-feature process, passing:
   • The Epic number (skip step 1 of write-feature — Epic is already fetched)
   • The capability name as the pre-filled answer to step 2 of write-feature
   • Abbreviated clarification: because the capability name already follows the [Actor] can [verb] [object] pattern and the Epic context is already in hand, skip write-feature step 3 (clarification questions) unless something is genuinely ambiguous from the Epic. Write-feature step 4 (user story derivation) and step 5 (DDD Language Guard) should still run silently. Resume from write-feature step 6 (vertical slice assessment).
3. Before moving to the next Feature, call AskUserQuestion (per ../references/questioning-style.md):
   • question: "Feature [N] created. Ready to continue to Feature [N+1]: [next capability name]?"
   • header: "Continue?"
   • options:
     • Yes, continue → proceed to the next Feature (default)
     • Pause here → exit; print a summary of which Features were created and which remain; suggest /clear before resuming
     • Skip this feature → mark as skipped in the list and move to the next
     • Add a new feature → call AskUserQuestion with question "What is the new feature capability?", header "New feature", options from capability names inferred from the Epic's Goal or Success Metrics not yet in the list; add the confirmed feature, then continue

4. Completion

When all Features have been created (or skipped), print a summary:

"Epic #<epic_number> Feature breakdown complete. Created: [list with issue numbers] Skipped: [list if any]"

Then call AskUserQuestion (per ../references/questioning-style.md):

• question: "What's next?"
• header: "Next step"
• options:
  • Break down first Feature → follow wtf.feature-to-tasks with the first created Feature number (default)
  • Break down next Feature → follow wtf.feature-to-tasks with a different Feature number
  • Stop here → exit, no further action

Suggest /clear before continuing if the conversation has grown long.