plan

# `plan` — Feature Plan Creator Turns a feature description into a task-by-task implementation plan and writes it to `docs/superpowers/plans/<YYYY-MM-DD>-<feature-slug>/PLAN.md`. **Position in the gflow-cli workflow:** ``` /gflow:predict <proposal> → GO / CAUTION / STOP verdict /gflow:scenario <feature> → edge cases + BDD skeleton /gflow:plan <feature> → writes the task checklist ← this skill /gflow:status → surfaces next task during execution /gflow:check → before each commit ``` --- ## When to invoke - After `/gflow:predict` returns GO or CAUTION - When a backlog item in `PLAN.md` needs a concrete task breakdown before starting work - Any feature larger than a single isolated file change ## When not to invoke - Simple bug fixes (< 10 lines, no boundary crossing) — go straight to the fix - Pure doc changes - A task already fully specified in a superpowers plan — use `/gflow:status` to find it --- ## Protocol ### Phase 1 — Gather inputs from context **From `/gflow:predict` output in context (do not ask if already present):** - Verdict (GO / CAUTION) and confidence score - Architectural constraints and module placement - Security risks and mandatory mitigations - Devil's Advocate simplifications or sequencing blockers **From `/gflow:scenario` output in context (do not ask if already present):** - Critical and High scenarios → these become must-cover tests in the task checklist - BDD `Scenario:` blocks → seeds the BDD sca...