feature-initlisted

# feature-init Create a feature folder for the DAE pipeline — `feature.md` (the Ready contract), the folder, a branch, and a tracker entry. Checkpoint 1.5. ## When to use Three paths: - **From `discuss`** — receives a `feature_intake` payload in context (park or promote outcome). No interview. - **Standalone** — no payload; run the intake interview. - **Onboarding intake** — invoked by `onboard` (or directly) to formalize work that *already exists* in the codebase. The feature folder is reverse-engineered from an existing spec / branch / implementation. Enters at `status: in-progress` or `done`, not `ready`. Detect from-discuss vs standalone by whether a `feature_intake` payload is present; onboarding intake is signalled by `onboard` (or an explicit "formalize existing feature" request). **Not for:** brand-new ideas worth exploring first (`discuss`), or editing an existing feature (`feature-edit`). ## Workflow Before the steps below, create one TodoWrite todo per workflow step (the full list up front, as a roadmap). After Step 6 creates the feature folder, show the **pipeline breadcrumb**: run `${CLAUDE_PLUGIN_ROOT}/scripts/dae_progress.py <feature-dir>` and present its output — for a just-initialized feature (no `progress.md` yet) it renders the pipeline ahead. The breadcrumb is advisory and never blocks. See `${CLAUDE_PLUGIN_ROOT}/references/progress-indicator.md`. 1. **Resolve** — resolve the methodology root + manifest via `${CLAUDE_PLUGIN_ROOT}/scripts/dae_resolv