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

package/Project/i18n/en/Sprint/commands/status.md

@@ -1,218 +1,9 @@
 ---
-description: "Sprint Status"
-argument-hint: "[sprint N] [--bmad] [--verbose]"
+description: "Deprecated (removed in 9.0): use /workflow:status"
+deprecated: true
+replaced-by: /workflow:status
 ---
 
-# Sprint Status
+> ⚠️ `/sprint:status` is deprecated and will be removed in 9.0. Use `/workflow:status`.
 
-Display detailed metrics and sprint progress.
-
-## Arguments
-
-$ARGUMENTS (optional, format: [sprint N] [--bmad] [--verbose])
-- **sprint N** (optional): Sprint number
-- **--bmad** (optional): Include BMAD v6 state machine routing, TDD phase tracking, and auto-routing suggestions (reads from `.bmad/sprint-status.yaml`)
-- **--verbose** (optional): Show detailed task breakdown per story (only with `--bmad`)
-- If not specified, displays current sprint
-
-## Process
-
-### Step 1: Identify sprint
-
-1. Find requested sprint or current sprint
-2. Read sprint-goal.md
-3. If `--bmad`: also read `.bmad/sprint-status.yaml` for state machine data
-
-### Step 2: Collect data
-
-1. Read all sprint User Stories
-2. Read all associated Tasks
-3. Calculate metrics
-4. If `--bmad`: parse BMAD routing rules, TDD phases, and story state transitions
-
-### Step 3: Generate report
-
-Create detailed report with:
-- Overview
-- Progress by US
-- Time metrics
-- Burndown chart (text)
-- Blockers
-- Risks
-
-If `--bmad` is specified, additionally include:
-- BMAD state machine diagram with story counts per state
-- TDD phase indicators per in-progress story
-- Auto-routing suggestions (e.g., stories ready to transition)
-- Acceptance criteria completion status
-
-## Output Format
-
-```
-╔══════════════════════════════════════════════════════════════════╗
-║  📊 SPRINT 1 - STATUS REPORT                                     ║
-║  Generated: 2024-01-22 14:30                                     ║
-╚══════════════════════════════════════════════════════════════════╝
-
-┌──────────────────────────────────────────────────────────────────┐
-│ 🎯 SPRINT GOAL                                                   │
-├──────────────────────────────────────────────────────────────────┤
-│ Walking Skeleton - Complete authentication and first page       │
-│ Period: 2024-01-15 → 2024-01-29 (Day 8/14)                     │
-└──────────────────────────────────────────────────────────────────┘
-
-══════════════════════════════════════════════════════════════════════════
-📈 OVERVIEW
-
-Overall progress:
-██████████████░░░░░░░░░░░░░░░░░░ 45%
-
-│ Metric            │ Current│ Target │ Status │
-├───────────────────┼────────┼────────┼────────┤
-│ Points completed  │ 5      │ 10     │ 🟡 50% │
-│ Tasks completed   │ 8      │ 16     │ 🟡 50% │
-│ Hours completed   │ 28h    │ 62h    │ 🟡 45% │
-│ Remaining days    │ 6      │ -      │        │
-
-══════════════════════════════════════════════════════════════════════════
-📖 PROGRESS BY USER STORY
-
-│ US      │ Name               │ Points │ Tasks    │ Status          │
-├─────────┼────────────────────┼────────┼──────────┼─────────────────┤
-│ US-001  │ User login         │ 5      │ 6/10     │ 🟡 In Progress  │
-│         │                    │        │ 60%      │ ██████░░░░      │
-├─────────┼────────────────────┼────────┼──────────┼─────────────────┤
-│ US-002  │ Product list       │ 5      │ 2/6      │ 🔴 To Do        │
-│         │                    │        │ 33%      │ ███░░░░░░░      │
-
-══════════════════════════════════════════════════════════════════════════
-⏱️ TIME METRICS
-
-Estimated vs Actual (hours):
-│ Type    │ Est.   │ Actual │ Diff   │
-├─────────┼────────┼────────┼────────┤
-│ [DB]    │ 6h     │ 5.5h   │ -0.5h  │ ✅
-│ [BE]    │ 20h    │ 12h    │ -      │ 🟡 In progress
-│ [FE-WEB]│ 12h    │ 3h     │ -      │ 🟡 In progress
-│ [FE-MOB]│ 14h    │ 0h     │ -      │ ⏸️ Blocked
-│ [TEST]  │ 10h    │ 7.5h   │ -2.5h  │ ✅ Under-estimated
-
-Daily velocity: 4h/day (target: 4.4h/day)
-
-══════════════════════════════════════════════════════════════════════════
-📉 BURNDOWN (simplified)
-
-Remaining hours per day:
-62h │████████████████████████████████████████████████████████████████
-    │█████████████████████████████████████████████████████░░░░░░░░░░░
-    │██████████████████████████████████████████░░░░░░░░░░░░░░░░░░░░░░
-    │█████████████████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
-    │████████████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
-    │█████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
-    │██████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
-    │████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ← Ideal
-34h │████████████████████████████████████████████████ ← Actual
-    └───────────────────────────────────────────────────────────────
-    D1  D2  D3  D4  D5  D6  D7  D8  D9  D10 D11 D12 D13 D14
-
-Status: 🟡 Slightly behind (6h)
-
-══════════════════════════════════════════════════════════════════════════
-⚠️ BLOCKERS
-
-│ Task     │ US     │ Blocker                     │ Since  │
-├──────────┼────────┼─────────────────────────────┼────────┤
-│ TASK-008 │ US-001 │ Waiting for auth API        │ 2 days │
-│ TASK-021 │ US-002 │ Missing SMTP config         │ 1 day  │
-
-Impact: 14h blocked (22% of sprint)
-
-══════════════════════════════════════════════════════════════════════════
-🚨 RISKS
-
-│ Level  │ Description                           │ Mitigation              │
-├────────┼───────────────────────────────────────┼─────────────────────────┤
-│ 🔴 High│ Mobile blocked for 2 days             │ Prioritize TASK-005     │
-│ 🟡 Med │ 6h behind schedule                    │ Possible overtime       │
-│ 🟢 Low │ Tests under-estimated                 │ Add buffer sprint 2     │
-
-══════════════════════════════════════════════════════════════════════════
-📋 RECOMMENDED ACTIONS
-
-1. 🔴 URGENT: Unblock TASK-008 by completing TASK-005
-2. 🟡 Configure SMTP to unblock TASK-021
-3. 🟢 Review test estimations for future sprints
-
-══════════════════════════════════════════════════════════════════════════
-
-Actions:
-  /project:board                    # View Kanban
-  /project:move-task TASK-XXX done  # Complete a task
-  /project:list-tasks status blocked # View all blockers
-```
-
-## BMAD Output (with --bmad)
-
-When `--bmad` is specified, the report additionally includes:
-
-```
-State Machine:
-------------------------------------------------------
-[backlog 2] -> [ready-for-dev 3] -> [in-progress 2] -> [review 1] -> [done 4]
-                                        |
-                                     [blocked 1]
-
-In Progress:
-------------------------------------------------------
-US-005: User authentication
-   TDD: Green | Tasks: 3/5 | AC: 1/3
-   Current: TASK-015 - Implement JWT validation
-
-US-007: Password reset
-   TDD: Red | Tasks: 0/4 | AC: 0/2
-   Current: Writing first test
-
-Auto-routing suggestions:
-------------------------------------------------------
-US-008 has all tasks complete -> /sprint:transition US-008 review
-```
-
-## Examples
-
-```
-# Current sprint status
-/sprint:status
-
-# Sprint 2 status
-/sprint:status sprint 2
-
-# Sprint status with BMAD state machine
-/sprint:status --bmad
-
-# Verbose BMAD status
-/sprint:status --bmad --verbose
-```
-
-## Report Generation
-
-Report is also saved in:
-`project-management/sprints/sprint-XXX/status-YYYY-MM-DD.md`
-
-## Next Step
-
-```
-╔══════════════════════════════════════════════════════════╗
-║                      NEXT STEP                           ║
-╠══════════════════════════════════════════════════════════╣
-║                                                          ║
-║  → /sprint:next-story                                    ║
-║    Pick the next story to work on                        ║
-║                                                          ║
-║  → /sprint:dev                                           ║
-║    Continue development                                  ║
-║                                                          ║
-║  → /workflow:review                                      ║
-║    Sprint review (if sprint is complete)                 ║
-║                                                          ║
-╚══════════════════════════════════════════════════════════╝
-```
+Run `/workflow:status $ARGUMENTS`: read `.claude/commands/workflow/status.md` and follow it with these arguments.

package/Project/i18n/en/Sprint/commands/transition.md

@@ -1,263 +1,9 @@
 ---
-description: Transition story to a new status
-argument-hint: <story-id> <target-status>
+description: "Deprecated (removed in 9.0): use /project:backlog move story"
+deprecated: true
+replaced-by: /project:backlog
 ---
 
-# Sprint Transition
+> ⚠️ `/sprint:transition` is deprecated and will be removed in 9.0. Use `/project:backlog move story`.
 
-Transition a story to a new status with validation and history tracking.
-
-## Arguments
-
-$ARGUMENTS (format: <story-id> <target-status>)
-- **story-id** (required): Story identifier (e.g., US-001)
-- **target-status** (required): Target status
-
-Valid statuses:
-- `backlog` - Story in product backlog
-- `ready-for-dev` - Refined and ready for development
-- `in-progress` - Currently being developed
-- `review` - Code complete, awaiting review
-- `done` - Definition of Done met
-- `blocked` - Blocked by external factor
-- `sprint-N` - Assign story to sprint N (e.g., `sprint-2`)
-
-## Process
-
-### Step 1: Validate story exists
-
-1. Read `.bmad/sprint-status.yaml`
-2. Find story by ID
-3. Get current status
-
-### Step 2: Validate transition
-
-Check state machine rules:
-```
-Allowed transitions:
-  backlog → ready-for-dev
-  ready-for-dev → in-progress
-  in-progress → review
-  review → done
-  review → in-progress (changes requested)
-  * → blocked (any state can be blocked)
-  blocked → previous_status (resume)
-```
-
-### Step 3: Check gate requirements
-
-Before transitioning, verify gate requirements:
-
-**→ ready-for-dev**
-- [ ] Acceptance criteria defined
-- [ ] Story points estimated
-- [ ] Tasks decomposed
-
-**→ in-progress**
-- [ ] No blocking dependencies
-- [ ] Developer assigned (optional)
-
-**→ review**
-- [ ] All tasks completed
-- [ ] Tests passing (TDD green or refactor)
-- [ ] Code pushed
-
-**→ done**
-- [ ] Code reviewed
-- [ ] All AC validated
-- [ ] DoD checklist complete
-
-**→ blocked**
-- Provide blocked_reason
-
-### Step 4: Execute transition
-
-1. Store previous status
-2. Update status field
-3. Set timestamps
-4. Update TDD phase if applicable
-5. Record in history
-
-### Step 5: Side effects
-
-Based on transition:
-
-**→ in-progress**
-- Set `tdd_phase` to `red`
-- Set `current_task` to first task
-
-**→ review**
-- Set `tdd_phase` to `refactor`
-- Clear `current_task`
-
-**→ done**
-- Clear `tdd_phase`
-- Record completion time
-
-**→ blocked**
-- Store `blocked_reason`
-- Store `previous_status` for resume
-
-### Step 6: Update history
-
-Add entry:
-```yaml
-history:
-  - timestamp: "2026-01-29T10:00:00Z"
-    from: "in-progress"
-    to: "review"
-    by: "manual"
-    reason: "All tasks complete"
-```
-
-## Output Format
-
-### Successful Transition
-
-```
-═══════════════════════════════════════════════════════
-              Story Transition
-═══════════════════════════════════════════════════════
-
-📖 US-005: User authentication
-
-Status: in-progress → review ✅
-
-Gate checks:
-──────────────────────────────────────────────────────
-✅ All tasks completed (5/5)
-✅ Tests passing
-✅ Code pushed
-
-History updated:
-──────────────────────────────────────────────────────
-• 2026-01-29 10:00 - in-progress → review (manual)
-• 2026-01-27 09:00 - ready-for-dev → in-progress
-• 2026-01-25 14:00 - backlog → ready-for-dev
-
-Next steps:
-──────────────────────────────────────────────────────
-Story is now in review. Assign reviewer or run:
-  /sprint:next-story --claim
-═══════════════════════════════════════════════════════
-```
-
-### Gate Failed
-
-```
-═══════════════════════════════════════════════════════
-              Transition Blocked
-═══════════════════════════════════════════════════════
-
-📖 US-005: User authentication
-
-Requested: in-progress → review ❌
-
-Gate failures:
-──────────────────────────────────────────────────────
-❌ Tasks incomplete: 3/5
-❌ TDD phase is 'red' - tests should pass first
-
-Required actions:
-──────────────────────────────────────────────────────
-1. Complete remaining tasks:
-   □ TASK-015: Implement JWT validation
-   □ TASK-016: Add refresh token support
-
-2. Move TDD to green phase:
-   /sprint:tdd green
-
-Then retry: /sprint:transition US-005 review
-═══════════════════════════════════════════════════════
-```
-
-### Invalid Transition
-
-```
-═══════════════════════════════════════════════════════
-              Invalid Transition
-═══════════════════════════════════════════════════════
-
-📖 US-005: User authentication
-
-Current: in-progress
-Requested: done ❌
-
-Invalid: Cannot transition directly from 'in-progress' to 'done'
-
-Valid transitions from 'in-progress':
-──────────────────────────────────────────────────────
-• review - Code complete, ready for review
-• blocked - Story is blocked
-
-State machine:
-  backlog → ready-for-dev → in-progress → review → done
-═══════════════════════════════════════════════════════
-```
-
-## Example
-
-```
-/sprint:transition US-005 review
-/sprint:transition US-003 blocked "Waiting for API credentials"
-/sprint:transition US-003 in-progress  # Resume from blocked
-```
-
-## Special Cases
-
-### Blocking a story
-```
-/sprint:transition US-003 blocked "Waiting for external API"
-```
-Stores the reason and preserves previous status for resume.
-
-### Unblocking a story
-```
-/sprint:transition US-003 in-progress
-```
-When transitioning from blocked, returns to previous status.
-
-### Requesting changes in review
-```
-/sprint:transition US-005 in-progress
-```
-Valid reverse transition from review to address feedback.
-
-### Assigning to a sprint
-```
-/sprint:transition US-003 sprint-2
-```
-Assigns the story to sprint 2. Creates the sprint directory if necessary. Story status is preserved.
-
-### Cascade to tasks
-
-When transitioning a story:
-- **→ in-progress**: Tasks remain in their current status (started individually)
-- **→ done**: Checks all tasks are done; warns if incomplete tasks remain
-- **→ blocked**: Marks all in-progress tasks as blocked
-
-## Next Step
-
-```
-╔══════════════════════════════════════════════════════════╗
-║                      NEXT STEP                           ║
-╠══════════════════════════════════════════════════════════╣
-║                                                          ║
-║  Based on target status:                                 ║
-║                                                          ║
-║  → in-progress:                                          ║
-║    /sprint:dev — Develop the story                       ║
-║                                                          ║
-║  → review:                                               ║
-║    /gate:validate-story — Validate the DoD               ║
-║                                                          ║
-║  → done:                                                 ║
-║    /sprint:next-story — Pick next story                  ║
-║    /workflow:review — Sprint review (if sprint done)     ║
-║                                                          ║
-║  → blocked:                                              ║
-║    Resolve the blocker, then                             ║
-║    /sprint:transition in-progress                        ║
-║                                                          ║
-╚══════════════════════════════════════════════════════════╝
-```
+Run `/project:backlog move story $ARGUMENTS`: read `.claude/commands/project/backlog.md` and follow it with these arguments.

package/Project/i18n/en/agents/product-owner.md

@@ -143,7 +143,7 @@ THEN [observable and measurable result]
 
 ## Commands I Can Execute
 
-### /project:generate-backlog
+### /workflow:plan --only=backlog
 Generates a complete backlog with:
 - Personas (min 3)
 - Definition of Done
@@ -152,7 +152,7 @@ Generates a complete backlog with:
 - Sprints (Walking Skeleton in Sprint 1)
 - Dependency matrix
 
-### /gate:validate-backlog
+### /gate:check backlog
 Checks SCRUM compliance:
 - INVEST for each US
 - 3C for each US
@@ -160,7 +160,7 @@ Checks SCRUM compliance:
 - MMF for Epics
 - Generates a report with score /100
 
-### /project:prioritize
+### Prioritization (on request)
 Helps prioritize the backlog with:
 - Business value analysis
 - MoSCoW
@@ -211,9 +211,9 @@ When asked to help with the backlog:
 → I propose an order with MoSCoW justification
 
 **"Is my backlog SCRUM compliant?"**
-→ I execute /gate:validate-backlog
+→ I execute /gate:check backlog
 → I generate a report with score and corrective actions
 
 **"I want to create a backlog for my project"**
-→ I execute /project:generate-backlog
+→ I execute /workflow:plan --only=backlog
 → I create the entire structure: personas, DoD, epics, US, sprints

package/Project/i18n/en/agents/tech-lead.md

@@ -207,23 +207,23 @@ Each US MUST traverse all layers:
 
 ## Commands I Can Execute
 
-### /project:decompose-tasks [sprint]
+### /workflow:start [sprint]
 Decomposes sprint US into tasks:
-- Creates `tasks/US-XXX-tasks.md` for each US
-- Creates `task-board.md` (Kanban)
+- Creates one `tasks/TASK-*.md` file per task
+- Creates `board.md` (Kanban)
 - Generates Mermaid dependency graph
 - Calculates total hours
 
-### /gate:validate-backlog
+### /gate:check backlog
 Checks technical compliance:
 - Vertical slicing respected
 - Consistent estimations
 - Logical dependencies
 
-### /project:estimate
+### Estimation (on request)
 Helps estimate a US in Fibonacci points
 
-### /project:architecture
+### Architecture proposal (on request)
 Proposes architecture for a feature
 
 ## How I Work
@@ -270,9 +270,9 @@ When asked for technical help:
 → I list files to create
 
 **"Sprint 001 is ready, decompose it"**
-→ I execute /project:decompose-tasks 001
+→ I execute /workflow:start 001
 → I create all tasks for each US
-→ I generate the task-board and metrics
+→ I generate the board and metrics
 
 **"We have a technical blocker"**
 → I analyze the problem

package/Project/i18n/en/commands/add-epic.md

@@ -1,92 +1,9 @@
 ---
-description: Add an EPIC
-argument-hint: [arguments]
+description: "Deprecated (removed in 9.0): use /project:backlog add epic"
+deprecated: true
+replaced-by: /project:backlog
 ---
 
-# Add an EPIC
+> ⚠️ `/project:add-epic` is deprecated and will be removed in 9.0. Use `/project:backlog add epic`.
 
-Create a new EPIC in the backlog.
-
-## Arguments
-
-$ARGUMENTS (format: "EPIC Name" [priority])
-- **Name** (required): EPIC title
-- **Priority** (optional): High, Medium, Low (default: Medium)
-
-## 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.
-
-## Process
-
-### Step 1: Analyze arguments
-
-Extract:
-- EPIC name from $ARGUMENTS
-- Priority (if provided, otherwise Medium)
-
-### Step 2: Generate ID
-
-1. Read files in `project-management/backlog/epics/`
-2. Find the last used ID (format EPIC-XXX)
-3. Increment to get the new ID
-
-### Step 3: Collect information
-
-Ask the user (if not provided):
-- EPIC description
-- MMF (Minimum Marketable Feature)
-- Business objectives (2-3 points)
-- Success criteria
-
-### Step 4: Create the file
-
-1. Use template `Scrum/templates/epic.md`
-2. Replace placeholders:
-   - `{ID}`: Generated ID
-   - `{NOM}`: EPIC name
-   - `{PRIORITE}`: Chosen priority
-   - `{MINIMUM_MARKETABLE_FEATURE}`: MMF
-   - `{DESCRIPTION}`: Description
-   - `{DATE}`: Current date (YYYY-MM-DD)
-   - `{OBJECTIF_1}`, `{OBJECTIF_2}`: Business objectives
-   - `{CRITERE_1}`, `{CRITERE_2}`: Success criteria
-
-3. Create file: `project-management/backlog/epics/EPIC-{ID}-{slug}.md`
-
-### Step 5: Update index
-
-1. Read `project-management/backlog/index.md`
-2. Add EPIC to EPICs table
-3. Update summary counters
-4. Save
-
-## Output Format
-
-```
-✅ EPIC created successfully!
-
-📋 EPIC-{ID}: {NAME}
-   Status: 🔴 To Do
-   Priority: {PRIORITY}
-   File: project-management/backlog/epics/EPIC-{ID}-{slug}.md
-
-Next steps:
-  /project:add-story EPIC-{ID} "User Story Name"
-```
-
-## Example
-
-```
-/project:add-epic "Authentication System" High
-```
-
-Creates:
-- `project-management/backlog/epics/EPIC-001-authentication-system.md`
-
-## Validation
-
-- [ ] Name is not empty
-- [ ] Priority is valid (High/Medium/Low)
-- [ ] Directory `project-management/backlog/epics/` exists
-- [ ] ID is unique
+Run `/project:backlog add epic $ARGUMENTS`: read `.claude/commands/project/backlog.md` and follow it with these arguments.