fr-progresslisted

# fr-progress In v2 there is no dedicated progress subcommand surface — queries decompose into one of three primitives: | Operator says | Command | |---|---| | "audit drift on this plan" | `fr apply <plan-dir>` (default dry-run lists what gh would change) | | "status of this spec" | `fr spec status <spec-path>` | | "status of every spec" | `fr spec status --all` | | "mark step done" | `fr plan edit <plan-dir> --tick P<n>.T<n>.S<n>` | | "mark phase done" | `fr plan edit <plan-dir> --complete-phase N [--note ...]` | **Announce at start:** "I'm using fr-progress for [capability]." ## Repo-state preflight (run before touching docs/superpowers/ by hand) First time in a repo with `docs/superpowers/` or fr config: **never** manually create, move, or archive files under it (#378). Run in order — `fr status`/`fr repair`/`fr migrate v1-to-v2` preview by default, no `--yes`: ```bash fr --help # confirm fr is installed / repo is fr-managed fr status # repo-wide sweep: four buckets, judged against origin/<default> fr acceptance check # matrix gate; exit 2 on failing rows fr repair # preview stale-ref rewrites ls docs/superpowers/plans/*.md 2>/dev/null || true # hits = legacy v1 plans (v2 is folders) fr migrate v1-to-v2 # if the ls above found hits fr spec status --all # per-spec rollup before deciding what's "done" fr archive docs/superpowers/plans/<name> # only now, one per plan