@the-bearded-bear/claude-craft 8.23.3 → 8.26.0-next.2a54921

package/Project/i18n/en/commands/migrate.md

@@ -0,0 +1,158 @@
+---
+description: "One-shot migration of an existing backlog to BMAD v6 (analyze, migrate, fill stories, resync)"
+argument-hint: "[--analyze|--dry-run|--resync|--stories] [--force]"
+---
+
+# Migrate Backlog
+
+One-shot migration of an existing backlog to the BMAD v6 layout, with `.bmad/sprint-status.yaml` as the single source of truth for story and task status (schema: `.claude/templates/project/sprint-status.md`). One command covers four modes: analysis, migration, filling missing story fields, and content resync.
+
+## Usage
+
+| Invocation | What it does | Replaces |
+|------------|--------------|----------|
+| `/project:migrate --analyze` | Report only: structure, INVEST scores, BMAD v6 gaps. Writes nothing | `analyze-backlog` |
+| `/project:migrate` | Default: migrate the backlog and create `.bmad/sprint-status.yaml` | `migrate-backlog` |
+| `/project:migrate --stories [story-id]` | Fill missing story fields (tasks, AC, history, INVEST) | `update-stories` |
+| `/project:migrate --resync` | Reconcile content and IDs between markdown and the YAML | `sync-backlog` |
+| `--dry-run` | Preview only, applies to every mode | - |
+| `--force` | Overwrite existing BMAD files (migration mode) | - |
+
+## Arguments
+
+$ARGUMENTS (format: [--analyze|--dry-run|--resync|--stories] [--force])
+- **--analyze**: analysis mode (read-only)
+- **--stories**: optional `story-id` (e.g. US-001); if omitted, all stories are processed
+- **--resync**: reconciliation mode
+- **--dry-run**: show what would change, write nothing
+- **--force**: overwrite an existing `sprint-status.yaml` and BMAD files
+- Modes are mutually exclusive; with none of them, the default migration runs.
+
+## Shared rules
+
+- **Backlog location**, searched in order: `project-management/backlog/` (standard), `docs/backlog/`, `backlog/`, `.bmad/` (already migrated).
+- **Single source of truth**: status lives only in `.bmad/sprint-status.yaml`. Markdown holds content only (title, description, AC, points, parents).
+- **Legacy statuses**: the initial migration is the ONLY moment legacy markdown statuses/emojis are read; they are moved into the YAML and then stripped from the markdown. `--resync` and `--stories` never copy a status from markdown.
+- **Plan mode is mandatory** for the default migration, `--stories` and `--resync` (unless `--dry-run`): Claude analyzes the impact, proposes a plan and waits for validation before changing anything.
+- **Order**: `--analyze` first, then the migration, then `--stories`; use `--resync` afterwards when content drifts.
+
+## --analyze
+
+Report only, no file is modified.
+
+1. **Detect** the backlog location (see shared rules).
+2. **Identify** epics (`EPIC-*.md`, `epic*.md`), user stories (`US-*.md`, `story*.md`), tasks (`TASK-*.md` or embedded in stories) and index files (`index.md`, `backlog.md`, `README.md`).
+3. **Parse** per file: ID, title, legacy status (🔴 To Do, 🟡 In Progress, 🟢 Done, ⏸️ Blocked), sprint, story points, parents (US → EPIC, TASK → US), AC count, task count and completion.
+4. **INVEST score** per story (0-6): Independent (no blocking dependency), Negotiable (has a description), Valuable (benefit stated), Estimable (has points), Small (≤ 8 points), Testable (has AC).
+5. **BMAD v6 gaps**: TDD phase tracking, task list with completion, status history, sprint assignment, AC validation status.
+6. **Report**: summary (counts), structure (tree), INVEST table, migration gaps table (field / % stories missing / action), recommendations.
+
+```
+📊 Backlog Analysis Report
+Location: project-management/backlog/ | Epics: {N} | Stories: {N} | Tasks: {N}
+
+| Story | Title  | INVEST | Missing   |
+|-------|--------|--------|-----------|
+| US-001 | Login | 5/6    | Estimable |
+
+Migration gaps: tdd_phase 100% | tasks.list 60% | history 100%
+Next: /project:migrate
+```
+
+## Default: migration
+
+1. **Validate**: create `.bmad/` if needed; warn if `sprint-status.yaml` exists and no `--force`; the analysis should have been run.
+2. **Create the structure**: `.bmad/sprint-status.yaml`, `batch-queue.yaml`, `gates/`, `hooks/`, `lib/`.
+3. **Parse** each story: metadata, AC (Gherkin), related tasks, legacy status, completion.
+4. **Map legacy statuses** into the YAML:
+
+   | Original | BMAD v6 status |
+   |----------|----------------|
+   | 🔴 To Do | backlog |
+   | 🟡 In Progress | in-progress |
+   | 🟢 Done | done |
+   | ⏸️ Blocked | blocked |
+   | Sprint-X assigned | ready-for-dev |
+
+5. **Initial TDD phase**: 0% tasks done → `red`; 1-99% → `green`; 100% → `refactor` or `done`.
+6. **Generate `sprint-status.yaml`**, one entry per story:
+
+   ```yaml
+   stories:
+     US-001:
+       title: "User login"
+       status: "in-progress"
+       previous_status: "ready-for-dev"
+       tdd_phase: "red"
+       current_task: "TASK-001"
+       story_points: 5
+       epic_id: "EPIC-001"
+       tasks:
+         total: 4
+         completed: 2
+         list:
+           - { id: "TASK-001", title: "Backend auth endpoint", status: "in-progress", type: "BE" }
+       acceptance_criteria: { total: 3, validated: 1 }
+       history:
+         - { timestamp: "2026-01-29T10:00:00Z", from: "backlog", to: "in-progress", by: "migration", reason: "BMAD v6 migration" }
+   ```
+
+7. **Backup** (unless `--dry-run`): copy the backlog to `.bmad/backup/` (timestamped) and log its location.
+8. **Apply** (unless `--dry-run`): write the YAML, strip status emojis/fields from the markdown files, create `.bmad/migration-log.md`.
+
+Dry run: lists the files that would be created (e.g. `.bmad/sprint-status.yaml`), the counts of stories/tasks/AC that would be migrated, and ends with "Run without --dry-run to apply changes."
+
+Rollback: `tar -xzf .bmad/backup/backlog-*.tar.gz -C project-management/ && rm .bmad/sprint-status.yaml`.
+
+Next steps: review the YAML, run `/workflow:status`, set sprint metadata (dates, goals), check quality gates with `/gate:check all`.
+
+## --stories
+
+Fill missing BMAD v6 fields of existing stories (all, or one `story-id`).
+
+1. **Load** `.bmad/sprint-status.yaml` and the story files; compare.
+2. **Missing fields** and defaults:
+
+   | Field | Required | Default if missing |
+   |-------|----------|--------------------|
+   | tdd_phase | Yes | "red" if in-progress, "" otherwise |
+   | tasks.list / total / completed | Yes | Extract from `## Tasks`, count, count done |
+   | current_task | No | First in-progress task |
+   | history | Yes | Initial entry with the current status (`by: "migrate"`) |
+   | acceptance_criteria.total / validated | Yes | Count from the AC section / 0 |
+   | story_points | Yes | Ask the user if missing |
+   | epic_id | No | Extract from the file |
+
+3. **Parse tasks** from the story's `## Tasks` table and **AC** from the Gherkin `### ACn:` blocks into `tasks.list` and `acceptance_criteria.list` (ids, titles). Task and AC statuses go to the YAML only for entries not yet tracked there; an existing YAML status is never overwritten by markdown.
+4. **INVEST**: add `invest_score` (independent, negotiable, valuable, estimable, small, testable, total).
+5. **Update** `sprint-status.yaml` by merging the fields; optionally add a metadata comment to story files (`<!-- BMAD v6 Metadata … -->` with `tdd_phase`, `invest_score`, `last_sync`).
+
+Output: table of updated stories (fields added, INVEST score), summary per field (added / skipped), warnings (e.g. "US-003: missing story points", "US-007: no acceptance criteria"), modified files. Then fix the warnings, run `/project:migrate --resync` and `/gate:check backlog`.
+
+## --resync
+
+Reconcile content and IDs between the markdown files and the YAML. Status is never synchronized: the YAML wins.
+
+1. **Load** both sources and build a comparison map by story ID.
+2. **Detect differences** in content: missing stories, titles, story points, task lists, AC, assignment.
+3. **Resolve**: the YAML is authoritative for status, TDD phase, history and task state; markdown is authoritative for titles, descriptions, AC text and points. Ask the user when both changed the same content field.
+4. **Files → YAML**: add stories found only in files; update titles, points, task and AC lists.
+5. **YAML → files**: refresh the metadata comment (TDD phase, history, INVEST score, sync timestamp); never write a status into markdown.
+6. **Orphans**: in YAML but not in files → mark `archived` or warn; in files but not in YAML → add to the YAML (status `backlog`).
+7. **Timestamps**: `last_sync` in the YAML and `<!-- last_sync: … -->` in story files.
+
+Output: changes files → YAML, changes YAML → files, conflicts resolved, orphans (archived / added), "Last sync" time. Then review `git diff` and run `/workflow:status`.
+
+Automation: a pre-commit hook may run `/project:migrate --resync` (`.bmad/hooks/pre-commit.sh`).
+
+## Examples
+
+```
+/project:migrate --analyze
+/project:migrate --dry-run
+/project:migrate
+/project:migrate --force
+/project:migrate --stories US-001
+/project:migrate --stories --dry-run
+/project:migrate --resync --dry-run
+```

package/Project/i18n/en/commands/move-task.md

@@ -1,204 +1,9 @@
 ---
-description: Move a Task
-argument-hint: [arguments]
+description: "Deprecated (removed in 9.0): use /project:backlog move task"
+deprecated: true
+replaced-by: /project:backlog
 ---
 
-# Move a Task
+> ⚠️ `/project:move-task` is deprecated and will be removed in 9.0. Use `/project:backlog move task`.
 
-Change a task's status following the strict workflow.
-
-## Arguments
-
-$ARGUMENTS (format: TASK-XXX destination)
-- **TASK-ID** (required): Task ID (e.g., TASK-001)
-- **Destination** (required):
-  - `in-progress`: Start task
-  - `blocked`: Mark as blocked
-  - `done`: Mark as completed
-
-## Strict Workflow
-
-```
-🔴 To Do ──→ 🟡 In Progress ──→ 🟢 Done
-     │              │
-     │              ↓
-     └────→ ⏸️ Blocked ←────┘
-                │
-                ↓
-           🟡 In Progress
-```
-
-### Allowed Transitions
-
-| From | To | Allowed |
-|--------|------|----------|
-| 🔴 To Do | 🟡 In Progress | ✅ |
-| 🔴 To Do | ⏸️ Blocked | ✅ |
-| 🔴 To Do | 🟢 Done | ❌ **Forbidden** |
-| 🟡 In Progress | 🟢 Done | ✅ |
-| 🟡 In Progress | ⏸️ Blocked | ✅ |
-| 🟡 In Progress | 🔴 To Do | ✅ (rollback) |
-| ⏸️ Blocked | 🟡 In Progress | ✅ |
-| 🟢 Done | 🟡 In Progress | ⚠️ (reopening) |
-
-## Process
-
-### Step 1: Validate Task
-
-1. Find task file
-2. Read current status
-3. Identify associated US and sprint
-
-### Step 2: Validate transition
-
-1. Check that transition is allowed
-2. If To Do → Done, block and suggest In Progress
-
-### Step 3: If transition to Blocked
-
-Ask for blocker:
-```
-What is the blocker for TASK-XXX?
-> [Blocker description]
-```
-
-### Step 4: If transition to Done
-
-Ask for time spent:
-```
-Time spent on TASK-XXX? (estimation: 4h)
-> [Actual time, e.g., 3.5h]
-```
-
-### Step 5: Update Task
-
-1. Modify status in metadata
-2. Add blocker if Blocked
-3. Update time spent if Done
-4. Update modification date
-
-### Step 6: Update Board
-
-1. Read sprint board
-2. Move task to new column
-3. Update metrics
-
-### Step 7: Update User Story
-
-1. Update task list
-2. Recalculate progress
-3. If all tasks Done, suggest completing US
-
-### Step 8: Update Index
-
-1. Update global counters
-
-## Output Format
-
-### Successful transition
-
-```
-✅ Task moved!
-
-🔧 TASK-003: Login API endpoint
-   Before: 🔴 To Do
-   After: 🟡 In Progress
-
-📖 US-001: User login
-   Progress: 2/6 → 3/6 (50%)
-
-Next steps:
-  /project:move-task TASK-003 done       # When completed
-  /project:move-task TASK-003 blocked    # If blocked
-```
-
-### Task completed
-
-```
-✅ Task completed!
-
-🔧 TASK-003: Login API endpoint
-   Status: 🟡 In Progress → 🟢 Done
-   Estimation: 4h
-   Actual time: 3.5h ✓
-
-📖 US-001: User login
-   Progress: 4/6 (67%) ████████░░░░
-
-Sprint 1:
-   Tasks done: 12/25 (48%)
-   Hours: 35h/77h completed
-```
-
-### All tasks Done
-
-```
-✅ Task completed!
-
-🔧 TASK-006: AuthService tests
-   Status: 🟢 Done
-
-🎉 All tasks of US-001 completed!
-
-📖 US-001: User login
-   Progress: 6/6 (100%) ██████████
-
-Recommended next step:
-  /sprint:transition US-001 done
-```
-
-### Workflow error
-
-```
-❌ Transition not allowed!
-
-🔧 TASK-004: Auth controller
-   Current status: 🔴 To Do
-   Requested transition: → 🟢 Done
-
-Rule: A task must go through "In Progress" before "Done"
-
-Correct action:
-  /project:move-task TASK-004 in-progress
-  # ... work on task ...
-  /project:move-task TASK-004 done
-```
-
-### Blocked task
-
-```
-✅ Task marked as blocked
-
-🔧 TASK-005: Login screen
-   Status: 🟡 In Progress → ⏸️ Blocked
-   Blocker: Waiting for auth API (TASK-003)
-
-To unblock:
-  1. Complete TASK-003
-  2. /project:move-task TASK-005 in-progress
-```
-
-## Examples
-
-```
-# Start a task
-/project:move-task TASK-001 in-progress
-
-# Complete a task
-/project:move-task TASK-001 done
-
-# Block a task
-/project:move-task TASK-001 blocked
-
-# Unblock a task
-/project:move-task TASK-001 in-progress
-```
-
-## Updated Metrics
-
-At each move:
-- Task count by status
-- Estimated vs actual hours
-- US progress
-- Sprint progress
-- Kanban board
+Run `/project:backlog move task $ARGUMENTS`: read `.claude/commands/project/backlog.md` and follow it with these arguments.

package/Project/i18n/en/commands/report.md

@@ -0,0 +1,156 @@
+---
+description: "Project analytics reports: sprint burndown, metrics dashboard, story dependency graph and critical path"
+argument-hint: "<burndown|metrics|deps> [--critical] [--sprint=Sprint-N] [--type=points|stories|tasks] [--format=...] [--velocity=N] [--output=path]"
+---
+
+# /project:report
+
+## Mission
+
+Single entry point for read-only project analytics. Each subcommand turns the backlog and sprint data into a report: a burndown chart, a metrics dashboard, or a dependency graph (with optional critical path).
+
+## Usage
+
+| Invocation | What it does | Replaces |
+|------------|--------------|----------|
+| `/project:report burndown` | Mermaid burndown chart + variance and projection | `/project:report burndown` |
+| `/project:report metrics` | Velocity, spec coverage, gates, health, regression dashboard | `/project:report metrics` |
+| `/project:report deps` | Story dependency graph, bottlenecks, parallel groups | `/project:report deps` |
+| `/project:report deps --critical` | Critical path, slack and parallel execution plan | `/project:report deps --critical` |
+
+## Arguments
+
+Parse `$ARGUMENTS`: the first positional word is the subcommand (`burndown`, `metrics` or `deps`). If missing or unknown, list the table above and ask which one to run.
+
+| Flag | Applies to | Description |
+|------|-----------|-------------|
+| `--sprint=Sprint-N` | all | Sprint to analyze (default: current sprint) |
+| `--type=points\|stories\|tasks` | burndown | Unit of the chart (default `points`) |
+| `--format=dashboard\|json\|markdown` | metrics | Output format (default `dashboard`) |
+| `--format=mermaid\|table\|json` | deps | Output format (default `mermaid`) |
+| `--output=path` | deps | Output path (default stdout) |
+| `--critical` | deps | Switch to critical-path analysis |
+| `--velocity=N` | deps --critical | Team velocity (points per sprint) for the timeline |
+
+## Shared rules
+
+- **Single source of truth:** story and task STATUS is read from `.bmad/sprint-status.yaml` only; markdown files (`project-management/backlog/`, `tasks/TASK-*.md`) provide content (titles, points, `Depends on:`), never status. Its `history` entries feed the burndown and the velocity trends.
+- Default paths: `project-management/` (`prd.md`, `backlog/`, `sprints/sprint-{N}-{slug}/`); templates in `.claude/templates/project/`.
+- Reports are read-only for project files; the only writes are the metrics snapshots in `.bmad/metrics/`.
+- **Plan mode is mandatory:** before executing, propose the plan (data read, files written) and wait for validation.
+- End each report with key observations and recommendations.
+
+## burndown
+
+Prerequisites: `.bmad/sprint-status.yaml` with sprint data, start/end dates and estimated story points.
+
+1. **Load**: read the current sprint in `.bmad/sprint-status.yaml` (dates, committed points, status `history` per day) and past data from `.bmad/metrics/`.
+2. **Calculate**: ideal line (linear from total to 0), actual remaining per day, variance (ahead/behind), projected finish from current velocity.
+3. **Chart** (Mermaid):
+
+```mermaid
+xychart-beta
+    title "Sprint-3 Burndown"
+    x-axis ["Day 1", "Day 2", "Day 3", "Day 4", "Day 5", "Day 6", "Day 7", "Day 8", "Day 9", "Day 10"]
+    y-axis "Story Points Remaining" 0 --> 25
+    line "Ideal" [21, 18.9, 16.8, 14.7, 12.6, 10.5, 8.4, 6.3, 4.2, 2.1, 0]
+    line "Actual" [21, 21, 18, 18, 15, 12, 12, 9, 6, 3]
+```
+
+4. **Analysis report**:
+
+```
+SPRINT BURNDOWN REPORT — Sprint-3 | Day 9/10
+Total committed: 21 pts | Remaining: 3 | Completed: 18 (86%)
+Ideal remaining: 2.1 | Actual: 3 | Variance: -0.9 pts (slightly behind)
+Average velocity: 2.0 pts/day | Projected finish: Day 10.5 (0.5 days late)
+Completion trend: Day 1-3: 3pts (slow start) | Day 4-6: 6pts | Day 7-9: 9pts
+Risk: 1 story may carry over (US-015, 3pts, blocked)
+```
+
+5. **Store**: append the daily data to `.bmad/metrics/burndown-{sprint-id}.json`.
+
+## metrics
+
+Prerequisites: `.bmad/sprint-status.yaml`; `project-management/backlog/` with stories; optional `.bmad/metrics/` history and `project-management/prd.md` for coverage.
+
+| Category | Metrics (source) |
+|----------|------------------|
+| Velocity | Points completed per sprint, rolling average (last 3), commitment ratio (completed / committed, target > 80%), carryover (`sprint-status.yaml`, metrics history) |
+| Spec coverage | % FR-xxx covered by stories, % stories with code references, % ACs with tests, % complete FR→US→Code→Test chains (PRD, stories, `/project:trace`) |
+| Quality gates | PRD gate (>= 80%), story DoD, sprint ready pass rates, first-pass rate (gate history from `/gate:check`) |
+| Sprint health | Stories and tasks done / total, blocked stories, TDD compliance (`sprint-status.yaml`) |
+| Regression | Bugs found / fixed per sprint, regression rate, escape rate (QA recette sessions, regression registry) |
+
+Process:
+1. **Collect**: read `.bmad/sprint-status.yaml`, `.bmad/metrics/`, trace data (`/project:trace`), gate history and QA recette sessions (if present).
+2. **Calculate**: all five categories plus trends versus the previous sprint (up / down / same).
+3. **Dashboard** (one line per metric with status icons, thresholds as above):
+
+```
+PROJECT METRICS DASHBOARD — Sprint-3 | 2026-02-19
+VELOCITY      Current 18/21 pts (86%) | Average 19 pts/sprint | Commitment 86% OK | Carryover 3 pts
+SPEC COVERAGE Requirements 12/15 (80%) WARN | Stories with code 8/10 | ACs with tests 24/28 (86%) OK | Full chains 7/10 (70%) WARN
+QUALITY GATES PRD 1/1 | Story DoD 6/8 (75%) WARN | Sprint ready 1/1 | First-pass 70% WARN
+SPRINT HEALTH Stories 6/8 | Tasks 22/28 | Blocked 1 (US-015) WARN | TDD compliance 100%
+REGRESSION    Bugs found 4 | fixed 3 | Regressions 0 | Escape rate 0%
+TRENDS        Velocity +2 pts | Spec coverage +10% | First-pass -5% | Blocked same
+```
+
+4. **Store** the snapshot in `.bmad/metrics/sprint-{id}.json`, with the keys `sprint_id`, `date`, `velocity` (`completed`, `committed`, `ratio`), `coverage` (`requirements`, `stories`, `tests`, `traceability`), `gates` (`prd_pass_rate`, `story_pass_rate`, `sprint_ready_rate`, `first_pass_rate`), `health` (`stories_done`, `stories_total`, `tasks_done`, `tasks_total`, `blocked`, `tdd_compliance`), `regression` (`bugs_found`, `bugs_fixed`, `regressions`, `escape_rate`).
+
+`--format=json` or `markdown` outputs the same data in that format.
+
+## deps
+
+Prerequisites: `project-management/backlog/` stories with `Depends on:` fields; optional `.bmad/sprint-status.yaml` (status colors) and `project-management/prd.md` (epic grouping).
+
+1. **Load**: scan `project-management/backlog/`, filter by `--sprint` if given, read `Depends on:` from each Traceability section, build the adjacency list. Status comes from `.bmad/sprint-status.yaml`.
+2. **Validate**: circular dependencies (A -> B -> C -> A), references to non-existent stories, self-references. Report every issue.
+3. **Graph** (Mermaid `graph TD`, default): one `subgraph` per epic (`EPIC-001: Authentication`), nodes `US-001[US-001: Login Page]`, edges `US-002 --> US-001` (depends on), and `classDef` colors by status: `done` #90EE90, `inProgress` #FFD700, `blocked` #FF6B6B, `ready` #87CEEB. `--format=table|json` for other outputs.
+4. **Analyze**: bottleneck stories (block 3+ others), independent stories, longest dependency chain, parallel groups.
+5. **Report**:
+
+```
+STORY DEPENDENCY GRAPH — Sprint-3 | Stories: 8 | Dependencies: 5
+Bottlenecks: US-001 Login Page (blocks 4 stories)
+Independent: US-006, US-007
+Longest chain (3 steps): US-001 -> US-002 -> US-003
+Parallel groups: [US-006, US-007] | [US-004, US-005] (after US-001)
+Issues: no circular dependencies, no missing references
+```
+
+### deps --critical
+
+Also requires story points. The critical path is the longest sequence of dependent stories; it sets the minimum duration regardless of team size.
+
+1. **Build the DAG** from the graph above (stop if a cycle exists).
+2. **Calculate**: topological sort, earliest/latest start and finish per story, zero-slack stories = critical path, points summed along it.
+3. **Slack**: total slack of non-critical stories, near-critical paths (slack < 2 pts), stories that could become critical if delayed.
+4. **Timeline** (use `--velocity` to fit phases into sprints):
+
+```
+CRITICAL PATH ANALYSIS — Sprint-3 | Velocity: 21 pts/sprint
+Critical path (13 pts): US-001 (5) -> US-002 (3) -> US-005 (5)
+Near-critical: US-001 (5) -> US-004 (3) [slack: 2pts]
+Phase 1: US-001 + US-006 + US-007 (8pts) | Phase 2: US-002 + US-004 (6pts) | Phase 3: US-003 + US-005 (7pts)
+Slack: US-003 5pts | US-004 2pts (monitor) | US-006, US-007 8pts
+```
+
+5. **Recommendations**: optimal execution order, parallelization, risk on critical stories (e.g. assign the strongest developer to US-001), ways to shorten the path (split stories).
+
+## Example
+
+```
+User: /project:report deps --critical --sprint=Sprint-3 --velocity=21
+
+Claude: Critical path: US-001 -> US-002 -> US-005 (13 pts), fits in 1 sprint.
+Risk: a 2+ day delay on US-001 puts the whole sprint at risk.
+```
+
+## Related Commands
+
+- `/project:trace` — Traceability matrix and coverage
+- `/workflow:status` — Sprint status overview
+- `/project:backlog next story` — Next story (considers dependencies)
+- `/workflow:retro` — Sprint retrospective (uses metrics)