fr-planlisted

# fr-plan Produce implementation plans through collaborative dialogue; conversational parts stay here, mechanical parts delegate to the `fr plan` CLI. **Announce at start:** "I'm using fr-plan to create the implementation plan." ## Format (v2 plan-as-folder) A plan is a directory under `docs/superpowers/plans/<slug>/` containing: - `_meta.yaml` — schema_version, plan slug, spec ref, target_repo, vk_version, created date, optional rework metadata (`parent_plan`, `prior_rework`, `origin_items`). - **`spec` ref notation:** a same-repo spec is a plain repo-relative path (`docs/superpowers/specs/<file>.md`); a spec in **another repo** MUST use the cross-repo form `<owner>/<repo>:<path-in-that-repo>` (e.g. `derio-net/frank:docs/superpowers/specs/<file>.md`). Without the `owner/repo:` prefix, `fr apply`'s reachability gate reads it as a missing same-repo file and refuses to dispatch. `fr plan self-review` warns when a same-repo-form spec doesn't resolve locally (#248). - `_prose.md` — the human-readable narrative. Tooling never parses this; it's for humans (and the implementing agent). - `NN.yaml` (one per phase, two-digit zero-padded: `01.yaml` … `99.yaml`) — phase header, tasks, steps, per-step state. Per-phase files prevent merge conflicts when parallel branches tick different phases. Phases number **from 1**; `00.yaml` fails parse — `fr plan create` rejects it pre-flight. Every step id follows `P<n>.T<n>.S<n>` (phase number, task number