docs: update CLAUDE.md and docs to new sequential phase/step IDs

- CLAUDE.md: Step 1b→6, Phase 5b→11, Phase 2.5→6, Phase 5→10
- docs/flowctl.md: worker-phase sequences, canonical order, TDD/review IDs
- docs/skill-anatomy.md: phase naming convention now integer-only

Task: fn-104.6

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: z23cc

CLAUDE.md

@@ -85,7 +85,7 @@ Rust: clippy for linting, cargo test for tests. No TypeScript, no npm. Skills an
 - **Review comparison**: `flowctl review-backend --compare <files>` or `--epic <id>` detects consensus/conflict across review receipts (auto-archived to `.flow/reviews/`)
 - **Domain tagging**: `flowctl task create --domain <domain>` tags tasks (frontend/backend/architecture/testing/docs/ops/general), filterable via `tasks --domain`
 - **Epic archival**: `flowctl epic archive <id>` moves closed epic + tasks + specs + reviews to `.flow/.archive/`; `flowctl epic clean` archives all closed epics at once
-- **Learning loop**: plan injects memory (Step 1b), worker saves lessons (Phase 5b, included in default sequence when memory.enabled is true), epic close prompts retro, retro verifies stale entries via `flowctl memory verify <id>`
+- **Learning loop**: plan injects memory (Step 6), worker saves lessons (Phase 11, included in default sequence when memory.enabled is true), epic close prompts retro, retro verifies stale entries via `flowctl memory verify <id>`
 - **Task duration**: `flowctl done` auto-tracks `duration_seconds` from start to completion, rendered in evidence
 - **File ownership**: `flowctl task create --files <paths>` declares owned files; `flowctl files --epic <id>` shows ownership map + conflict detection
 - **File locking (Teams)**: `flowctl lock --task <id> --files <paths>` acquires runtime file locks; `flowctl unlock --task <id>` releases on completion; `flowctl lock-check --file <path>` inspects lock state; `flowctl unlock --all` clears all locks between waves
@@ -95,9 +95,9 @@ Rust: clippy for linting, cargo test for tests. No TypeScript, no npm. Skills an
 - **Review circuit breaker**: impl-review fix loop capped at `MAX_REVIEW_ITERATIONS` (default 3) — prevents infinite NEEDS_WORK cycles
 - **Auto-improve analysis-driven**: generates custom program.md from codebase analysis (hotspots, lint, coverage, memory) with Action Catalog ranked by impact — not static templates
 - **Auto-improve quantitative**: captures before/after metrics per experiment, commit messages include delta `[lint:23→21]`
-- **Worker self-review**: Phase 2.5 runs guard + structured diff review (correctness, quality, performance, testing) before commit
+- **Worker self-review**: Phase 6 runs guard + structured diff review (correctness, quality, performance, testing) before commit
 - **Plan auto-execute**: `/flow-code:plan` defaults to auto-execute work after planning (Teams mode handles any task count); `--plan-only` to opt out
-- **Goal-backward verification**: worker Phase 5 re-reads acceptance criteria and verifies each is actually satisfied before completing
+- **Goal-backward verification**: worker Phase 10 re-reads acceptance criteria and verifies each is actually satisfied before completing
 - **Full-auto by default**: `/flow-code:plan` and `/flow-code:work` require zero interactive questions — AI reads git state, `.flow/` config, and request context to make branch, review, and research decisions autonomously. Default mode is Worktree + Teams + Phase-Gate (all three active). Work resumes from `.flow/` state on every startup (not a special "resume mode"). All tasks done → auto push + draft PR (`--no-pr` to skip)
 - **Cross-platform**: flowctl is a single Rust binary (macOS/Linux). RP plan-review auto-degrades to Codex on platforms where rp-cli is unavailable. Bash hooks degrade gracefully on Windows (skip, don't block)
 - **Session start**: CLAUDE.md instruction (not an enforced hook) — if `.flow/` exists, run `flowctl status --interrupted` to check for unfinished work from a previous session and resume with the suggested `/flow-code:work <id>` command

docs/flowctl.md

@@ -531,7 +531,7 @@ flowctl guard --layer frontend [--json]
 
 Exits non-zero if any guard fails. Output includes per-command pass/fail status.
 
-Workers use this for baseline check (Phase 1) and verification (Phase 5) — one command replaces manual test/lint/typecheck invocations.
+Workers use this for baseline check (Phase 2) and verification (Phase 10) — one command replaces manual test/lint/typecheck invocations.
 
 ### invariants
 
@@ -556,7 +556,7 @@ flowctl invariants check [--json]
 - **Fix:** [how to fix if violated]
 ```
 
-Workers check invariants in Phase 1 (baseline) and Phase 5 (verification). Planners check during Step 1 to ensure tasks don't violate constraints.
+Workers check invariants in Phase 2 (baseline) and Phase 10 (verification). Planners check during Step 4 to ensure tasks don't violate constraints.
 
 ### stack
 
@@ -842,7 +842,7 @@ flowctl worker-prompt --task fn-1.1 --bootstrap [--tdd] [--review rp|codex] [--j
 Options:
 - `--task ID` (required): Task ID for context
 - `--bootstrap`: Output minimal ~200 token prompt that instructs the worker to call `worker-phase next` in a loop
-- `--tdd`: Include TDD Phase 2a in the prompt
+- `--tdd`: Include TDD Phase 4 in the prompt
 - `--review rp|codex`: Include review Phase 4
 - `--team`: Include Teams mode instructions (default in phase-gate)
 - `--json`: JSON output with `prompt` and `estimated_tokens` fields
@@ -859,10 +859,10 @@ flowctl worker-phase next --task fn-1.1 [--tdd] [--review rp|codex] --json
 flowctl worker-phase done --task fn-1.1 --phase <PHASE_ID> [--tdd] [--review rp|codex] --json
 ```
 
-**Default phase sequence**: `0 → 1 → 2 → 2.5 → 3 → 5 → 6`
-- With `--tdd`: adds Phase 2a (test-first)
-- With `--review`: adds Phase 4 (impl-review)
-- Canonical order: `0, 1, 2a, 2, 2.5, 3, 4, 5, 5b, 6`
+**Default phase sequence**: `1 → 2 → 5 → 6 → 7 → 10 → 12`
+- With `--tdd`: adds Phase 4 (test-first)
+- With `--review`: adds Phase 8 (impl-review)
+- Canonical order: `1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12`
 
 Phase progress is stored per-task in runtime state. `next` returns `{"phase": "<id>", "content": "...", "all_done": false}`. When all phases are complete, returns `{"phase": null, "all_done": true}`.
 

docs/skill-anatomy.md

@@ -81,7 +81,7 @@ The heart of the skill. Step-by-step workflow the agent follows. Must be specifi
 **Good:** "Run `cargo test --all` and verify zero failures"
 **Bad:** "Make sure the tests work"
 
-For flow-code skills, phases follow the convention: Phase 1, Phase 2, Phase 2.5 (verify), Phase 3 (commit), etc. Reference `flowctl` commands where applicable:
+For flow-code skills, phases follow the convention: Phase 1, Phase 2, Phase 3, etc. (always integers). Reference `flowctl` commands where applicable:
 ```bash
 $FLOWCTL guard              # Run all guards
 $FLOWCTL invariants check   # Check architecture invariants
@@ -137,13 +137,13 @@ Flow-code workers produce evidence JSON. Skills should specify what evidence the
 ### Phase Naming
 Follow the worker agent convention:
 - Phase 1: Re-anchor (read spec)
-- Phase 2: Implement
-- Phase 2.5: Verify & Fix
-- Phase 3: Commit
-- Phase 4: Review
-- Phase 5: Complete
+- Phase 5: Implement
+- Phase 6: Verify & Fix
+- Phase 7: Commit
+- Phase 8: Review
+- Phase 10: Complete
 
-Skills that define their own phases should use this numbering style (Phase 1, Phase 1.5, Phase 2) for consistency with the worker pipeline.
+Phase IDs are always integers. Skills that define their own phases should use sequential integers (Phase 1, Phase 2, Phase 3) for consistency with the worker pipeline.
 
 ### Cross-Skill References
 Reference other skills by name, don't duplicate: