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

package/Project/i18n/en/commands/batch-status.md

@@ -1,213 +1,9 @@
 ---
-description: Show batch processing queue status
-argument-hint: [--history]
+description: "Deprecated (removed in 9.0): use /workflow:status --queue"
+deprecated: true
+replaced-by: /workflow:status
 ---
 
-# Batch Status
+> ⚠️ `/project:batch-status` is deprecated and will be removed in 9.0. Use `/workflow:status --queue`.
 
-Display the current status of the batch processing queue.
-
-## Arguments
-
-$ARGUMENTS (format: [--history])
-- **--history** (optional): Show completed/failed stories history
-
-## Process
-
-### Step 1: Load queue
-
-1. Read `.bmad/batch-queue.yaml`
-2. Parse queue entries
-3. Load checkpoint data
-
-### Step 2: Categorize stories
-
-Group by status:
-- `pending` - Waiting to be processed
-- `running` - Currently being processed
-- `completed` - Successfully finished
-- `failed` - Encountered error
-- `skipped` - Skipped due to dependency failure
-
-### Step 3: Show queue state
-
-Display current queue status with details.
-
-### Step 4: Show history (if requested)
-
-Display completed and failed stories with timing.
-
-## Output Format
-
-### Active Queue
-
-```
-═══════════════════════════════════════════════════════
-              Batch Queue Status
-═══════════════════════════════════════════════════════
-
-Mode: Sequential
-Checkpoint: US-011 (2026-01-29 10:45:00)
-
-Queue Summary:
-──────────────────────────────────────────────────────
-⏳ Pending:   3
-🔄 Running:   1
-✅ Completed: 2
-❌ Failed:    0
-⏭️ Skipped:   0
-
-Total: 6 stories
-
-Running:
-──────────────────────────────────────────────────────
-🔄 US-012: Profile page
-   Priority: 3
-   Started: 2026-01-29 10:45:00 (15 min ago)
-   TDD Phase: green
-   Task: 2/4
-
-Pending:
-──────────────────────────────────────────────────────
-[4] US-013: Password reset
-    Dependencies: US-010 ✅, US-011 ✅
-
-[5] US-014: Email verification
-    Dependencies: US-010 ✅
-
-[6] US-015: Settings page
-    Dependencies: none
-
-Progress:
-──────────────────────────────────────────────────────
-██████████░░░░░░░░░░ 50% (3/6 stories)
-
-Estimated completion: ~1h 30m
-═══════════════════════════════════════════════════════
-```
-
-### With History
-
-```
-═══════════════════════════════════════════════════════
-              Batch Queue Status
-═══════════════════════════════════════════════════════
-
-Mode: Sequential
-Last checkpoint: US-014
-
-Queue Summary:
-──────────────────────────────────────────────────────
-⏳ Pending:   0
-🔄 Running:   0
-✅ Completed: 5
-❌ Failed:    1
-⏭️ Skipped:   1
-
-Completed History:
-──────────────────────────────────────────────────────
-| Story | Started | Completed | Duration |
-|-------|---------|-----------|----------|
-| US-010 | 10:00 | 10:42 | 42m |
-| US-011 | 10:42 | 11:18 | 36m |
-| US-012 | 11:18 | 12:05 | 47m |
-| US-014 | 12:05 | 12:38 | 33m |
-| US-015 | 12:38 | 13:10 | 32m |
-
-Failed:
-──────────────────────────────────────────────────────
-❌ US-013: Password reset
-   Started: 12:05
-   Failed: 12:22
-   Duration: 17m
-   Error: Test assertion failed in PasswordResetTest
-   TDD Phase: red
-
-Skipped:
-──────────────────────────────────────────────────────
-⏭️ US-016: Admin panel
-   Reason: Depends on failed US-013
-
-Statistics:
-──────────────────────────────────────────────────────
-Total time: 3h 10m
-Average per story: 38m
-Success rate: 83% (5/6)
-Points completed: 18/21
-
-Actions:
-──────────────────────────────────────────────────────
-To retry failed stories:
-  /project:queue-retry US-013
-
-To clear queue:
-  /project:queue-clear
-═══════════════════════════════════════════════════════
-```
-
-### Empty Queue
-
-```
-═══════════════════════════════════════════════════════
-              Batch Queue Status
-═══════════════════════════════════════════════════════
-
-Queue is empty.
-
-No stories are currently queued for processing.
-
-To add stories:
-  /project:run-epic EPIC-001    Queue an epic
-  /project:run-sprint           Queue sprint stories
-
-Or add individual story:
-  .bmad/lib/batch-executor.sh add US-001
-═══════════════════════════════════════════════════════
-```
-
-## Example
-
-```
-/project:batch-status
-/project:batch-status --history
-```
-
-## Queue Management
-
-### Add story to queue
-```bash
-.bmad/lib/batch-executor.sh add US-001 1
-```
-
-### Retry failed story
-```
-/project:queue-retry US-013
-```
-
-### Clear queue
-```
-/project:queue-clear --force
-```
-
-### Resume from checkpoint
-```
-/project:run-queue --resume
-```
-
-## Configuration
-
-Queue file: `.bmad/batch-queue.yaml`
-
-```yaml
-queue:
-  - story_id: "US-001"
-    priority: 1
-    status: "pending"
-    dependencies: []
-    added_at: "2026-01-29T10:00:00Z"
-
-checkpoints:
-  last_completed: "US-001"
-  timestamp: "2026-01-29T10:42:00Z"
-  stories_completed: 1
-```
+Run `/workflow:status --queue $ARGUMENTS`: read `.claude/commands/workflow/status.md` and follow it with these arguments.

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

@@ -1,134 +1,9 @@
 ---
-description: Display Kanban Board
-argument-hint: [arguments]
+description: "Deprecated (removed in 9.0): use /workflow:status --board"
+deprecated: true
+replaced-by: /workflow:status
 ---
 
-# Display Kanban Board
+> ⚠️ `/project:board` is deprecated and will be removed in 9.0. Use `/workflow:status --board`.
 
-Display the Kanban board of current sprint or a specific sprint.
-
-## Arguments
-
-$ARGUMENTS (optional, format: [sprint N])
-- **sprint N** (optional): Sprint number to display
-- If not specified, displays current sprint
-
-## Process
-
-### Step 1: Identify sprint
-
-1. If sprint specified, use that number
-2. Otherwise, find current sprint (with non-Done tasks)
-
-### Step 2: Read data
-
-1. Read file `project-management/sprints/sprint-XXX/board.md`
-2. Or regenerate from task files
-
-### Step 3: Group by status
-
-Organize tasks by column:
-- 🔴 To Do
-- 🟡 In Progress
-- ⏸️ Blocked
-- 🟢 Done
-
-### Step 4: Calculate metrics
-
-- Number of tasks per column
-- Estimated and completed hours
-- Progress percentage
-
-## Output Format
-
-```
-╔══════════════════════════════════════════════════════════════════╗
-║  📋 SPRINT 1 - Kanban Board                                      ║
-║  Goal: Walking Skeleton - Auth + First page                      ║
-║  Period: 2024-01-15 → 2024-01-29                                ║
-╚══════════════════════════════════════════════════════════════════╝
-
-┌─────────────────┬─────────────────┬─────────────────┬─────────────────┐
-│ 🔴 TO DO (4)    │ 🟡 IN PROGRESS  │ ⏸️ BLOCKED (1)  │ 🟢 DONE (8)     │
-│                 │ (3)             │                 │                 │
-├─────────────────┼─────────────────┼─────────────────┼─────────────────┤
-│                 │                 │                 │                 │
-│ TASK-009 [TEST] │ TASK-005 [BE]   │ TASK-008 [MOB]  │ TASK-001 [DB]   │
-│ E2E Tests       │ Auth Service    │ Login Screen    │ User Entity ✓   │
-│ 4h @US-001      │ 4h @US-001      │ 6h @US-001      │ 2h @US-001      │
-│                 │                 │ ⚠️ Waiting API  │                 │
-│ TASK-010 [DOC]  │ TASK-006 [WEB]  │                 │ TASK-002 [DB]   │
-│ Documentation   │ Auth Controller │                 │ Migration ✓     │
-│ 2h @US-001      │ 3h @US-001      │                 │ 1h @US-001      │
-│                 │                 │                 │                 │
-│ TASK-015 [BE]   │ TASK-012 [MOB]  │                 │ TASK-003 [BE]   │
-│ Products API    │ Products Bloc   │                 │ Repository ✓    │
-│ 4h @US-002      │ 5h @US-002      │                 │ 3h @US-001      │
-│                 │                 │                 │                 │
-│ TASK-016 [TEST] │                 │                 │ TASK-004 [BE]   │
-│ Products Tests  │                 │                 │ Login API ✓     │
-│ 3h @US-002      │                 │                 │ 4h @US-001      │
-│                 │                 │                 │                 │
-│                 │                 │                 │ ... +4 more     │
-│                 │                 │                 │                 │
-└─────────────────┴─────────────────┴─────────────────┴─────────────────┘
-
-══════════════════════════════════════════════════════════════════════════
-📊 METRICS
-
-Tasks:     ████████████████████░░░░░░░░░░ 8/16 (50%)
-Hours:     ████████████░░░░░░░░░░░░░░░░░░ 28h/62h (45%)
-Blocked:   1 task (6h)
-
-By type:
-[DB]  ██████████ 3/3 done
-[BE]  ████████░░ 4/5 (1 in progress)
-[WEB] ████░░░░░░ 1/3 (1 in progress)
-[MOB] ██░░░░░░░░ 0/3 (1 blocked, 1 in progress)
-[TEST]░░░░░░░░░░ 0/2
-
-══════════════════════════════════════════════════════════════════════════
-📖 USER STORIES
-
-│ US      │ Points │ Status          │ Tasks     │ Progress    │
-├─────────┼────────┼─────────────────┼───────────┼─────────────┤
-│ US-001  │ 5      │ 🟡 In Progress  │ 6/10      │ ██████░░░░  │
-│ US-002  │ 5      │ 🔴 To Do        │ 2/6       │ ███░░░░░░░  │
-
-Sprint: 10 points | Done: 0 pts
-══════════════════════════════════════════════════════════════════════════
-
-Actions:
-  /project:move-task TASK-XXX in-progress  # Start a task
-  /project:move-task TASK-XXX done         # Complete a task
-  /sprint:status                   # View more metrics
-```
-
-## Compact Format
-
-If many tasks, display summary:
-
-```
-📋 Sprint 1 - Kanban (32 tasks)
-
-🔴 To Do (12):      TASK-015, TASK-016, TASK-017, TASK-018...
-🟡 In Progress (5): TASK-005, TASK-006, TASK-012, TASK-019, TASK-020
-⏸️ Blocked (2):     TASK-008 (API), TASK-021 (config)
-🟢 Done (13):       TASK-001..TASK-004, TASK-007, TASK-009..TASK-014
-
-Progress: 13/32 (41%) | 45h/98h
-```
-
-## Examples
-
-```
-# Display current sprint board
-/project:board
-
-# Display sprint 2 board
-/project:board sprint 2
-```
-
-## Update board.md file
-
-After display, the sprint's `board.md` file is updated with current data.
+Run `/workflow:status --board $ARGUMENTS`: read `.claude/commands/workflow/status.md` and follow it with these arguments.

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

@@ -1,124 +1,9 @@
 ---
-name: burndown
-description: Generate sprint burndown chart in Mermaid format showing daily progress
-arguments:
-  - name: sprint
-    description: Sprint ID (e.g., Sprint-3). Default current sprint
-    required: false
-  - name: type
-    description: "Chart type: points (default), stories, tasks"
-    required: false
+description: "Deprecated (removed in 9.0): use /project:report burndown"
+deprecated: true
+replaced-by: /project:report
 ---
 
-# /project:burndown
+> ⚠️ `/project:burndown` is deprecated and will be removed in 9.0. Use `/project:report burndown`.
 
-## Mission
-
-Generate a sprint burndown chart in Mermaid format showing daily progress against the ideal burndown line. Track story points, stories, or tasks completed over time.
-
-## Prerequisites
-
-- `.bmad/sprint-status.yaml` exists with sprint data
-- Sprint has start/end dates defined
-- Stories have story points estimated
-
-## Plan Mode
-
-> **Plan mode is mandatory.** Before executing, Claude activates plan mode to analyze impacted code, propose an implementation plan, and wait for your validation before making any changes.
-
-## Workflow
-
-### Step 1: Load Sprint Data
-
-1. Read `.bmad/sprint-status.yaml` for current sprint
-2. Get sprint start/end dates
-3. Get total story points committed
-4. Read historical completion data from `.bmad/metrics/`
-
-### Step 2: Calculate Burndown
-
-1. Calculate ideal burndown (linear from total to 0)
-2. Calculate actual burndown (remaining points per day)
-3. Identify variance (ahead/behind schedule)
-4. Project completion date based on current velocity
-
-### Step 3: Generate Mermaid Chart
-
-```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]
-```
-
-### Step 4: Analysis Report
-
-```
-╔══════════════════════════════════════════════════════════╗
-║              SPRINT BURNDOWN REPORT                      ║
-╠══════════════════════════════════════════════════════════╣
-║ Sprint: Sprint-3 | Day 9/10                              ║
-╠══════════════════════════════════════════════════════════╣
-║                                                          ║
-║ Progress:                                                ║
-║ ──────────────────────────────────────────────────────── ║
-║ Total committed:    21 story points                      ║
-║ Remaining:          3 story points                       ║
-║ Completed:          18 story points (86%)                ║
-║                                                          ║
-║ Burndown Analysis:                                       ║
-║ ──────────────────────────────────────────────────────── ║
-║ Ideal remaining:    2.1 points                           ║
-║ Actual remaining:   3 points                             ║
-║ Variance:           -0.9 points (slightly behind)  ⚠️    ║
-║                                                          ║
-║ Daily Velocity:                                          ║
-║ ──────────────────────────────────────────────────────── ║
-║ Average:            2.0 pts/day                          ║
-║ Today:              3 pts completed                      ║
-║ Projected finish:   Day 10.5 (0.5 days late)       ⚠️    ║
-║                                                          ║
-║ Completion Trend:                                        ║
-║ ──────────────────────────────────────────────────────── ║
-║ Day 1-3:  ▓▓░░░░░░░░░░░░░░ 3pts  (slow start)          ║
-║ Day 4-6:  ▓▓▓▓▓▓░░░░░░░░░░ 6pts  (ramping up)          ║
-║ Day 7-9:  ▓▓▓▓▓▓▓▓▓░░░░░░░ 9pts  (strong finish)       ║
-║                                                          ║
-║ Risk Assessment:                                         ║
-║ ──────────────────────────────────────────────────────── ║
-║ ⚠️  1 story may carry over (US-015, 3pts, blocked)       ║
-║ ✅ All other stories on track                            ║
-╚══════════════════════════════════════════════════════════╝
-```
-
-### Step 5: Store Data
-
-Append daily burndown data to `.bmad/metrics/burndown-{sprint-id}.json`.
-
-## Example Session
-
-```
-User: /project:burndown --sprint=Sprint-3
-
-Claude: Generating burndown chart for Sprint-3...
-
-[Mermaid chart displayed]
-
-Sprint-3 Status (Day 9/10):
-- 18/21 story points completed (86%)
-- Slightly behind ideal (-0.9 points)
-- Average velocity: 2.0 pts/day
-- Projected completion: Day 10.5 (0.5 days late)
-
-The slow start (Days 1-3: only 3pts) was offset by strong
-execution in Days 7-9 (9pts). US-015 (3pts) is blocked and
-may carry over to Sprint-4.
-```
-
-## Related Commands
-
-- `/project:metrics` — Full metrics dashboard
-- `/sprint:status` — Sprint status overview
-- `/workflow:retro` — Sprint retrospective
+Run `/project:report burndown $ARGUMENTS`: read `.claude/commands/project/report.md` and follow it with these arguments.