wtf.epic-to-features
Epic to Features
Break an Epic down into its full set of Features. Propose the complete feature list first. Then the planning mode decides the cadence. In guided mode, write each Feature one by one with full user control. In flow mode, draft the whole set in parallel and review it once.
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-trace).
Skip this step if gh-setup was already confirmed this session (e.g. when chained from wtf.write-epic).
0b. Resolve the planning mode and the feature scope
Run the Resolve the mode block from ../references/planning-mode.md. An explicit guided or flow argument in the invocation wins over config. $WTF_PLAN selects step 3 (guided) or step 3F (flow). Steps 0–2 and 4 run in both modes.
Then resolve $WTF_SCOPE with the read from wtf.write-feature step 0b: the feature_scope key in .wtf/config.json (single-story | grouped). If the key is missing, ask once per that step. $WTF_SCOPE shapes the proposed Feature list in step 2. Pass both $WTF_PLAN and $WTF_SCOPE down to every wtf.write-feature invocation, so it does not re-resolve them.