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

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

@@ -1,116 +1,9 @@
 ---
-description: Add a User Story
-argument-hint: [arguments]
+description: "Deprecated (removed in 9.0): use /project:backlog add story"
+deprecated: true
+replaced-by: /project:backlog
 ---
 
-# Add a User Story
+> ⚠️ `/project:add-story` is deprecated and will be removed in 9.0. Use `/project:backlog add story`.
 
-Create a new User Story and associate it with an EPIC.
-
-## Arguments
-
-$ARGUMENTS (format: EPIC-XXX "US Name" [points])
-- **EPIC-ID** (required): Parent EPIC ID (e.g., EPIC-001)
-- **Name** (required): User Story title
-- **Points** (optional): Story points in Fibonacci (1, 2, 3, 5, 8)
-
-## 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 from $ARGUMENTS:
-- EPIC ID
-- User Story name
-- Story points (if provided)
-
-### Step 2: Validate EPIC
-
-1. Check that EPIC exists in `project-management/backlog/epics/`
-2. If not found, display error with available EPICs
-
-### Step 3: Generate ID
-
-1. Read files in `project-management/backlog/user-stories/`
-2. Find the last used ID (format US-XXX)
-3. Increment to get the new ID
-
-### Step 4: Collect information
-
-Ask the user:
-- **Persona**: Who is the user? (P-XXX or description)
-- **Action**: What do they want to do?
-- **Benefit**: Why do they want it?
-- **Acceptance criteria**: At least 2 in Gherkin format
-- **Points**: If not provided, estimate (Fibonacci: 1, 2, 3, 5, 8)
-
-### Step 5: Create the file
-
-1. Use template `Scrum/templates/user-story.md`
-2. Replace placeholders:
-   - `{ID}`: Generated ID
-   - `{NOM}`: US name
-   - `{EPIC_ID}`: Parent EPIC ID
-   - `{SPRINT}`: "Backlog" (unassigned)
-   - `{POINTS}`: Story points
-   - `{PERSONA}`: Identified persona
-   - `{PERSONA_ID}`: Persona ID
-   - `{ACTION}`: Desired action
-   - `{BENEFICE}`: Expected benefit
-   - `{DATE}`: Current date (YYYY-MM-DD)
-
-3. Add acceptance criteria in Gherkin format
-
-4. Create file: `project-management/backlog/user-stories/US-{ID}-{slug}.md`
-
-### Step 6: Update EPIC
-
-1. Read EPIC file
-2. Add US to User Stories table
-3. Update progress
-4. Save
-
-### Step 7: Update index
-
-1. Read `project-management/backlog/index.md`
-2. Add US to "Prioritized Backlog" section
-3. Update counters
-4. Save
-
-## Output Format
-
-```
-✅ User Story created successfully!
-
-📖 US-{ID}: {NAME}
-   EPIC: {EPIC_ID}
-   Status: 🔴 To Do
-   Points: {POINTS}
-   File: project-management/backlog/user-stories/US-{ID}-{slug}.md
-
-Next steps:
-  /sprint:transition US-{ID} sprint-X    # Assign to sprint
-  /project:add-task US-{ID} "[BE] ..." 4h # Add tasks
-```
-
-## Example
-
-```
-/project:add-story EPIC-001 "User login" 5
-```
-
-Creates:
-- `project-management/backlog/user-stories/US-001-user-login.md`
-
-## INVEST Validation
-
-Check that US follows INVEST:
-- **I**ndependent: Can be developed alone
-- **N**egotiable: Details can be discussed
-- **V**aluable: Brings value to persona
-- **E**stimable: Can be estimated (points provided)
-- **S**mall: ≤ 8 points (otherwise suggest splitting)
-- **T**estable: Has clear acceptance criteria
+Run `/project:backlog add story $ARGUMENTS`: read `.claude/commands/project/backlog.md` and follow it with these arguments.

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

@@ -1,131 +1,9 @@
 ---
-description: Add a Task
-argument-hint: [arguments]
+description: "Deprecated (removed in 9.0): use /project:backlog add task"
+deprecated: true
+replaced-by: /project:backlog
 ---
 
-# Add a Task
+> ⚠️ `/project:add-task` is deprecated and will be removed in 9.0. Use `/project:backlog add task`.
 
-Create a new technical task and associate it with a User Story.
-
-## Arguments
-
-$ARGUMENTS (format: US-XXX "[TYPE] Description" estimation)
-- **US-ID** (required): Parent User Story ID (e.g., US-001)
-- **Description** (required): Description with type in brackets
-- **Estimation** (required): Estimation in hours (e.g., 4h, 2h, 0.5h)
-
-## 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.
-
-## Task Types
-
-| Type | Prefix | Description |
-|------|---------|-------------|
-| Database | `[DB]` | Entity, Migration, Repository |
-| Backend | `[BE]` | Service, API Resource, Processor |
-| Frontend Web | `[FE-WEB]` | Controller, Twig, Stimulus |
-| Frontend Mobile | `[FE-MOB]` | Model, Repository, Bloc, Screen |
-| Tests | `[TEST]` | Unit, Integration, E2E |
-| Documentation | `[DOC]` | PHPDoc, DartDoc, README |
-| DevOps | `[OPS]` | Docker, CI/CD |
-| Review | `[REV]` | Code Review |
-
-## Process
-
-### Step 1: Analyze arguments
-
-Extract from $ARGUMENTS:
-- User Story ID
-- Type (in brackets)
-- Description
-- Estimation in hours
-
-### Step 2: Validate User Story
-
-1. Check that US exists in `project-management/backlog/user-stories/`
-2. Get assigned sprint (if applicable)
-3. If US not found, display error
-
-### Step 3: Validate estimation
-
-- Minimum: 0.5h
-- Maximum: 8h
-- Ideal: 2-4h
-- If > 8h, suggest splitting the task
-
-### Step 4: Generate ID
-
-1. Find last used task ID
-2. Increment to get new ID
-
-### Step 5: Create the file
-
-1. Use template `Scrum/templates/task.md`
-2. Replace placeholders:
-   - `{ID}`: Generated ID
-   - `{DESCRIPTION}`: Short description
-   - `{US_ID}`: User Story ID
-   - `{TYPE}`: Task type
-   - `{ESTIMATION}`: Estimation in hours
-   - `{DATE}`: Current date (YYYY-MM-DD)
-   - `{DESCRIPTION_DETAILLEE}`: Detailed description
-
-3. Determine path:
-   - If US in sprint: `project-management/sprints/sprint-XXX/tasks/TASK-{ID}.md`
-   - Otherwise: `project-management/backlog/tasks/TASK-{ID}.md`
-
-### Step 6: Update User Story
-
-1. Read US file
-2. Add task to Tasks table
-3. Update progress
-4. Save
-
-### Step 7: Update board (if sprint)
-
-If US is in a sprint:
-1. Read `project-management/sprints/sprint-XXX/board.md`
-2. Add task to "🔴 To Do"
-3. Update metrics
-4. Save
-
-## Output Format
-
-```
-✅ Task created successfully!
-
-🔧 TASK-{ID}: {DESCRIPTION}
-   US: {US_ID}
-   Type: {TYPE}
-   Status: 🔴 To Do
-   Estimation: {ESTIMATION}h
-   File: {PATH}
-
-Next steps:
-  /project:move-task TASK-{ID} in-progress  # Start task
-  /project:board                             # View Kanban
-```
-
-## Examples
-
-```
-# Backend task
-/project:add-task US-001 "[BE] Login API endpoint" 4h
-
-# Database task
-/project:add-task US-001 "[DB] User entity with email/password fields" 2h
-
-# Mobile frontend task
-/project:add-task US-001 "[FE-MOB] Login screen with validation" 6h
-
-# Test task
-/project:add-task US-001 "[TEST] AuthService unit tests" 3h
-```
-
-## Validation
-
-- [ ] Type is valid (DB, BE, FE-WEB, FE-MOB, TEST, DOC, OPS, REV)
-- [ ] Estimation is between 0.5h and 8h
-- [ ] User Story exists
-- [ ] ID is unique
+Run `/project:backlog add task $ARGUMENTS`: read `.claude/commands/project/backlog.md` and follow it with these arguments.

package/Project/i18n/en/commands/analyze-backlog.md

@@ -1,137 +1,9 @@
 ---
-description: Analyze existing backlog structure for BMAD migration
-argument-hint: [--format json|yaml|md]
+description: "Deprecated (removed in 9.0): use /project:migrate --analyze"
+deprecated: true
+replaced-by: /project:migrate
 ---
 
-# Analyze Backlog
+> ⚠️ `/project:analyze-backlog` is deprecated and will be removed in 9.0. Use `/project:migrate --analyze`.
 
-Analyze the current backlog structure to prepare for BMAD v6 migration.
-
-## Arguments
-
-$ARGUMENTS (format: [--format output_format])
-- **--format** (optional): Output format (json, yaml, md). Default: md
-
-## Process
-
-### Step 1: Detect backlog location
-
-Search for backlog files in common locations:
-1. `project-management/backlog/` (claude-craft standard)
-2. `docs/backlog/` (alternative)
-3. `backlog/` (simple)
-4. `.bmad/` (if already migrated)
-
-### Step 2: Analyze structure
-
-For each location found, identify:
-- **Epics**: Files matching `EPIC-*.md` or `epic*.md`
-- **User Stories**: Files matching `US-*.md` or `story*.md`
-- **Tasks**: Files matching `TASK-*.md` or embedded in stories
-- **Index files**: `index.md`, `backlog.md`, `README.md`
-
-### Step 3: Parse metadata
-
-For each file, extract:
-- ID (EPIC-XXX, US-XXX, TASK-XXX)
-- Title/Name
-- Status (🔴 To Do, 🟡 In Progress, 🟢 Done, ⏸️ Blocked)
-- Sprint assignment
-- Story points (for US)
-- Parent relationships (US → EPIC, TASK → US)
-- Acceptance criteria count
-- Task count and completion
-
-### Step 4: Validate INVEST compliance
-
-For each User Story, check:
-- [ ] **I**ndependent: No blocking dependencies
-- [ ] **N**egotiable: Has description (not just title)
-- [ ] **V**aluable: Has benefit/value statement
-- [ ] **E**stimable: Has story points
-- [ ] **S**mall: ≤ 8 points
-- [ ] **T**estable: Has acceptance criteria
-
-Score each story (0-6 checks passed).
-
-### Step 5: Identify migration gaps
-
-Check for BMAD v6 compatibility:
-- [ ] TDD phase tracking (red/green/refactor)
-- [ ] Task list with completion tracking
-- [ ] Status history
-- [ ] Sprint assignment
-- [ ] Acceptance criteria validation status
-
-### Step 6: Generate compatibility report
-
-Create report with:
-1. **Summary**: Total epics, stories, tasks found
-2. **Structure**: Current file organization
-3. **INVEST Scores**: Per-story compliance
-4. **Migration Gaps**: Missing BMAD v6 fields
-5. **Recommendations**: Suggested actions
-
-## Output Format
-
-```
-📊 Backlog Analysis Report
-========================
-
-## Summary
-- Location: project-management/backlog/
-- Format: Markdown (claude-craft standard)
-- Epics: {COUNT}
-- User Stories: {COUNT}
-- Tasks: {COUNT}
-
-## Structure
-```
-project-management/backlog/
-├── index.md
-├── epics/
-│   ├── EPIC-001-*.md
-│   └── EPIC-002-*.md
-└── user-stories/
-    ├── US-001-*.md
-    └── US-002-*.md
-```
-
-## INVEST Compliance
-
-| Story ID | Title | Score | Missing |
-|----------|-------|-------|---------|
-| US-001 | Login | 5/6 | Estimable |
-| US-002 | Signup | 6/6 | - |
-
-Average INVEST Score: {AVG}/6
-
-## Migration Gaps
-
-| Field | Stories Missing | Action Required |
-|-------|-----------------|-----------------|
-| tdd_phase | 100% | Add to all |
-| tasks.list | 60% | Decompose |
-| history | 100% | Initialize |
-
-## Recommendations
-
-1. ⚠️ {COUNT} stories missing story points
-2. ⚠️ {COUNT} stories without acceptance criteria
-3. ✅ Structure compatible with BMAD v6
-4. 📝 Run `/project:migrate-backlog` to upgrade
-```
-
-## Example
-
-```
-/project:analyze-backlog
-/project:analyze-backlog --format yaml
-```
-
-## Next Steps
-
-After analysis:
-- `/project:migrate-backlog` - Convert to BMAD v6 format
-- `/project:update-stories` - Add missing fields
-- `/project:sync-backlog` - Sync with sprint-status.yaml
+Run `/project:migrate --analyze $ARGUMENTS`: read `.claude/commands/project/migrate.md` and follow it with these arguments.