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

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

@@ -1,243 +1,9 @@
 ---
-name: checkpoint
-description: Run spec verification checkpoints before and after implementation phases
-arguments:
-  - name: phase
-    description: "Checkpoint phase: pre-sprint, pre-impl, post-impl, pre-merge"
-    required: true
-  - name: story
-    description: Story ID to validate (e.g., US-001)
-    required: false
-  - name: sprint
-    description: Sprint ID to validate (e.g., Sprint-3)
-    required: false
+description: "Deprecated (removed in 9.0): use /gate:check --phase="
+deprecated: true
+replaced-by: /gate:check
 ---
 
-# /project:checkpoint
+> ⚠️ `/project:checkpoint` is deprecated and will be removed in 9.0. Use `/gate:check --phase=`.
 
-## Mission
-
-Run automated verification checkpoints at critical phases of the development lifecycle to ensure specs are coherent, complete, and aligned with implementation. Each phase validates different aspects of spec-code alignment.
-
-## Prerequisites
-
-- `project-management/prd.md` exists with FR-xxx requirement IDs
-- `project-management/backlog/` contains user stories
-- `.bmad/sprint-status.yaml` exists for sprint context
-- Optional: `project-management/constitution.md` for constitution checks
-
-## 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.
-
-## Checkpoint Phases
-
-### Phase 1: Pre-Sprint Checkpoint
-
-**When:** Before starting a sprint (after `/workflow:start`)
-**What it validates:**
-
-```
-╔══════════════════════════════════════════════════════════╗
-║           CHECKPOINT: PRE-SPRINT                         ║
-╠══════════════════════════════════════════════════════════╣
-║ Validating sprint readiness...                           ║
-╚══════════════════════════════════════════════════════════╝
-```
-
-| Check | Description | Required |
-|-------|-------------|----------|
-| Story AC completeness | Every story has Gherkin AC | Yes |
-| Story estimation | All stories have story points | Yes |
-| PRD traceability | Every story references FR-xxx IDs | Yes |
-| Task decomposition | Stories have decomposed tasks | Yes |
-| Dependency check | No circular or unresolved dependencies | Yes |
-| Constitution alignment | Stories don't contradict constitution | No |
-
-**Process:**
-1. Load all stories assigned to the sprint
-2. For each story, verify AC are in Gherkin format
-3. Verify `Implements:` field references valid FR-xxx IDs from PRD
-4. Check task decomposition (at least 1 task per story)
-5. Verify no circular dependencies in `Depends on:` fields
-6. If constitution exists, verify no contradictions
-7. Generate pass/fail report
-
-### Phase 2: Pre-Implementation Checkpoint
-
-**When:** Before coding a specific story (after `/sprint:next-story --claim`)
-**What it validates:**
-
-```
-╔══════════════════════════════════════════════════════════╗
-║           CHECKPOINT: PRE-IMPLEMENTATION                 ║
-╠══════════════════════════════════════════════════════════╣
-║ Validating story readiness for coding...                 ║
-╚══════════════════════════════════════════════════════════╝
-```
-
-| Check | Description | Required |
-|-------|-------------|----------|
-| Tech spec coverage | Tech spec covers all story requirements | Yes |
-| AC testability | Each AC can be converted to a test | Yes |
-| Dependencies resolved | All `Depends on` stories are done | Yes |
-| Task clarity | Tasks have clear descriptions | Yes |
-| NFR alignment | Implementation respects NFRs from constitution | No |
-
-**Process:**
-1. Load the specific story
-2. Find corresponding tech spec sections (via `Tech Spec:` reference)
-3. Verify tech spec covers each FR-xxx referenced by the story
-4. Verify each AC is testable (has GIVEN/WHEN/THEN structure)
-5. Check that all blocking stories (`Depends on`) are in status `done`
-6. Generate readiness report
-
-### Phase 3: Post-Implementation Checkpoint
-
-**When:** After completing a story (before `/sprint:transition US-xxx review`)
-**What it validates:**
-
-```
-╔══════════════════════════════════════════════════════════╗
-║           CHECKPOINT: POST-IMPLEMENTATION                ║
-╠══════════════════════════════════════════════════════════╣
-║ Validating implementation completeness...                ║
-╚══════════════════════════════════════════════════════════╝
-```
-
-| Check | Description | Required |
-|-------|-------------|----------|
-| Code traceability | Code files reference `// Story: US-xxx` | Yes |
-| Test coverage | Tests exist for each AC | Yes |
-| All tasks done | Every task in the story is completed | Yes |
-| TDD phase | Story is in `refactor` or `done` TDD phase | Yes |
-| No regressions | Existing tests still pass | Yes |
-| Spec drift | Implementation matches spec (no scope creep) | No |
-
-**Process:**
-1. Load the story and its tasks
-2. Search codebase for `// Story: US-xxx` or `# Story: US-xxx` references
-3. Verify test files exist covering each AC
-4. Check all tasks are marked done
-5. Verify TDD phase is `refactor` or `done`
-6. Run test suite to check for regressions
-7. Compare implemented scope with spec scope
-
-### Phase 4: Pre-Merge Checkpoint
-
-**When:** Before merging to main (integrates with `/common:pre-merge-check`)
-**What it validates:**
-
-```
-╔══════════════════════════════════════════════════════════╗
-║           CHECKPOINT: PRE-MERGE                          ║
-╠══════════════════════════════════════════════════════════╣
-║ Final validation before merge...                         ║
-╚══════════════════════════════════════════════════════════╝
-```
-
-| Check | Description | Required |
-|-------|-------------|----------|
-| AC validation | All acceptance criteria are validated | Yes |
-| Code review | Code has been reviewed | Yes |
-| Test suite green | All tests pass | Yes |
-| Constitution respect | Code respects project constitution | Yes |
-| Traceability complete | Full chain FR → US → Code → Test exists | Yes |
-| Documentation | Relevant docs updated | No |
-
-**Process:**
-1. Run all previous checkpoint validations
-2. Verify code review status
-3. Run full test suite
-4. Verify traceability chain completeness using `/project:trace`
-5. Check constitution compliance
-6. Generate final merge readiness report
-
-## Output Format
-
-### Passing Checkpoint
-
-```
-╔══════════════════════════════════════════════════════════╗
-║              CHECKPOINT PASSED ✅                         ║
-╠══════════════════════════════════════════════════════════╣
-║ Phase: pre-sprint                                        ║
-║ Sprint: Sprint-3                                         ║
-║ Score: 100% (6/6 checks passed)                          ║
-║                                                          ║
-║ ✅ Story AC completeness          All 5 stories have AC  ║
-║ ✅ Story estimation               All stories estimated   ║
-║ ✅ PRD traceability               All stories linked      ║
-║ ✅ Task decomposition             All stories decomposed  ║
-║ ✅ Dependency check               No circular deps        ║
-║ ✅ Constitution alignment         No contradictions       ║
-║                                                          ║
-║ → Ready to proceed                                       ║
-╚══════════════════════════════════════════════════════════╝
-```
-
-### Failing Checkpoint
-
-```
-╔══════════════════════════════════════════════════════════╗
-║              CHECKPOINT FAILED ❌                         ║
-╠══════════════════════════════════════════════════════════╣
-║ Phase: pre-impl                                          ║
-║ Story: US-012                                            ║
-║ Score: 60% (3/5 checks passed)                           ║
-║                                                          ║
-║ ✅ AC testability                 3/3 ACs testable        ║
-║ ✅ Dependencies resolved          No blockers             ║
-║ ✅ Task clarity                   4/4 tasks clear         ║
-║ ❌ Tech spec coverage             Missing FR-003 mapping  ║
-║ ❌ NFR alignment                  Perf target undefined   ║
-║                                                          ║
-║ Actions required:                                        ║
-║ 1. Add FR-003 coverage to tech spec section 3.2          ║
-║ 2. Define performance targets for profile API             ║
-║                                                          ║
-║ → Fix issues before proceeding                           ║
-╚══════════════════════════════════════════════════════════╝
-```
-
-## Integration
-
-This command integrates with the existing workflow:
-
-```
-/workflow:start       → triggers pre-sprint checkpoint
-/sprint:next-story    → suggests pre-impl checkpoint
-/sprint:transition    → triggers post-impl checkpoint (to review)
-/common:pre-merge-check → triggers pre-merge checkpoint
-```
-
-## Example Session
-
-```
-User: /project:checkpoint --phase=pre-sprint --sprint=Sprint-3
-
-Claude: Running pre-sprint checkpoint for Sprint-3...
-
-Loading 5 stories assigned to Sprint-3...
-
-✅ AC Completeness: 5/5 stories have Gherkin AC
-✅ Estimation: All stories estimated (total: 21 points)
-✅ PRD Traceability: All stories linked to FR-xxx IDs
-⚠️  Task Decomposition: US-015 has no tasks yet
-✅ Dependencies: No circular dependencies
-✅ Constitution: No contradictions found
-
-Score: 83% (5/6 passed)
-Status: WARNING — 1 issue needs attention
-
-Action: Decompose US-015 into tasks before starting sprint.
-```
-
-## Related Commands
-
-- `/project:trace` — View traceability matrix
-- `/project:coverage-map` — Check requirement coverage
-- `/gate:validate-prd` — Validate PRD quality
-- `/gate:validate-story` — Validate story completeness
-- `/common:pre-merge-check` — Pre-merge validation
-- `/workflow:start` — Start sprint (includes pre-sprint checkpoint)
+Run `/gate:check --phase=$ARGUMENTS`: read `.claude/commands/gate/check.md` and follow it with these arguments.

package/Project/i18n/en/commands/coverage-map.md

@@ -1,221 +1,9 @@
 ---
-name: coverage-map
-description: Identify requirements not covered by stories, code, or tests
-arguments:
-  - name: level
-    description: Coverage level to check (story, code, test, all)
-    required: false
-  - name: format
-    description: Output format (table, mermaid)
-    required: false
+description: "Deprecated (removed in 9.0): use /project:trace --gaps"
+deprecated: true
+replaced-by: /project:trace
 ---
 
-# /project:coverage-map
+> ⚠️ `/project:coverage-map` is deprecated and will be removed in 9.0. Use `/project:trace --gaps`.
 
-## Mission
-
-Analyze requirement coverage across all project layers (stories, code, tests) and generate a visual coverage report highlighting gaps and suggesting next actions. This command provides a quick health check of project traceability.
-
-## Prerequisites
-
-- `project-management/prd.md` exists with FR-xxx requirement IDs
-- `project-management/backlog/` contains user stories
-- Codebase and test files (optional, for deeper analysis)
-
-## 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: Inventory Requirements
-
-```
-╔══════════════════════════════════════════════════════════╗
-║              COVERAGE MAP - SCANNING                      ║
-╠══════════════════════════════════════════════════════════╣
-║ Building requirement inventory...                         ║
-╚══════════════════════════════════════════════════════════╝
-```
-
-1. Parse `project-management/prd.md` for all FR-xxx entries
-2. Categorize by priority: P0 (Must Have), P1 (Should Have), P2 (Nice to Have)
-3. Count total requirements per priority level
-
-### Step 2: Check Story Coverage
-
-For each requirement FR-xxx:
-1. Search user stories for `Implements:` references containing FR-xxx
-2. Mark requirement as "Covered by Story" or "No Story"
-3. Calculate story coverage percentage per priority level
-
-### Step 3: Check Code Coverage
-
-For each user story US-xxx that implements a requirement:
-1. Search codebase for `// Story: US-xxx` references
-2. Mark story as "Has Code" or "No Code"
-3. Calculate code coverage percentage
-
-### Step 4: Check Test Coverage
-
-For each user story US-xxx with code:
-1. Search test files for US-xxx or FR-xxx references
-2. Mark story as "Has Tests" or "No Tests"
-3. Calculate test coverage percentage
-
-### Step 5: Generate Coverage Report
-
-```
-╔══════════════════════════════════════════════════════════╗
-║              COVERAGE MAP GENERATED                       ║
-╠══════════════════════════════════════════════════════════╣
-║ Overall Coverage: {n}%                                    ║
-╚══════════════════════════════════════════════════════════╝
-```
-
-## Output Format
-
-### Table Format (default)
-
-```
-Requirement Coverage Map
-========================
-
-Overall Coverage
-────────────────
-
-| Layer | Covered | Total | Coverage | Status |
-|-------|---------|-------|----------|--------|
-| Stories | 8 | 10 | 80% | ⚠️ |
-| Code | 7 | 8 | 87% | ⚠️ |
-| Tests | 6 | 8 | 75% | ❌ |
-| End-to-End | 6 | 10 | 60% | ❌ |
-
-Coverage by Priority
-────────────────────
-
-| Priority | Requirements | Story Coverage | Code Coverage | Test Coverage |
-|----------|-------------|----------------|---------------|---------------|
-| P0 (Must Have) | 5 | 100% ✅ | 100% ✅ | 80% ⚠️ |
-| P1 (Should Have) | 3 | 66% ⚠️ | 50% ❌ | 33% ❌ |
-| P2 (Nice to Have) | 2 | 0% ❌ | 0% ❌ | 0% ❌ |
-
-Uncovered Requirements
-──────────────────────
-
-| ID | Requirement | Priority | Missing |
-|----|-------------|----------|---------|
-| FR-005 | Bulk export | P0 | Tests |
-| FR-010 | CSV import | P1 | Story, Code, Tests |
-| FR-011 | PDF export | P1 | Story, Code, Tests |
-| FR-020 | Analytics dashboard | P2 | Story, Code, Tests |
-| FR-021 | Custom reports | P2 | Story, Code, Tests |
-
-Recommended Actions
-───────────────────
-
-1. 🔴 CRITICAL: FR-005 (P0) has code but no tests — add test coverage
-2. ⚠️ HIGH: FR-010, FR-011 (P1) have no stories — create user stories
-3. 📝 LOW: FR-020, FR-021 (P2) not started — plan for future sprints
-
-Next Commands
-─────────────
-
-- /project:trace --id FR-005      → Deep trace for specific requirement
-- /project:add-story              → Create missing user stories
-- /project:generate-backlog       → Regenerate backlog with gaps
-```
-
-### Mermaid Format (--format mermaid)
-
-```mermaid
-graph TD
-    subgraph "P0 - Must Have"
-        FR001[FR-001 ✅]
-        FR002[FR-002 ✅]
-        FR003[FR-003 ✅]
-        FR004[FR-004 ✅]
-        FR005[FR-005 ⚠️ No Tests]
-    end
-
-    subgraph "P1 - Should Have"
-        FR010[FR-010 ❌ No Story]
-        FR011[FR-011 ❌ No Story]
-        FR012[FR-012 ✅]
-    end
-
-    subgraph "P2 - Nice to Have"
-        FR020[FR-020 ❌]
-        FR021[FR-021 ❌]
-    end
-
-    style FR001 fill:#4caf50
-    style FR002 fill:#4caf50
-    style FR003 fill:#4caf50
-    style FR004 fill:#4caf50
-    style FR005 fill:#ff9800
-    style FR010 fill:#f44336
-    style FR011 fill:#f44336
-    style FR012 fill:#4caf50
-    style FR020 fill:#f44336
-    style FR021 fill:#f44336
-```
-
-## Coverage Thresholds
-
-| Threshold | Status | Action |
-|-----------|--------|--------|
-| >= 90% | ✅ Excellent | Maintain |
-| 80-89% | ⚠️ Good | Review gaps |
-| 60-79% | ⚠️ Needs Work | Prioritize coverage |
-| < 60% | ❌ Critical | Immediate action required |
-
-## Example Session
-
-```
-User: /project:coverage-map
-
-Claude: Scanning requirement coverage...
-
-📋 Found 10 requirements in PRD (5 P0, 3 P1, 2 P2)
-📖 Checking story coverage... 80% (8/10)
-💻 Checking code coverage... 87% (7/8)
-🧪 Checking test coverage... 75% (6/8)
-
-Requirement Coverage Map
-========================
-[... full report ...]
-
-End-to-End Coverage: 60%
-
-🔴 2 P0 requirements need attention
-⚠️ 2 P1 requirements have no stories
-
-User: /project:coverage-map --level test
-
-Claude: Focusing on test coverage only...
-
-Test Coverage Report
-====================
-
-| Story | Has Tests | Test Files | Test Count |
-|-------|-----------|------------|------------|
-| US-001 | ✅ | 2 files | 20 tests |
-| US-002 | ✅ | 1 file | 6 tests |
-| US-003 | ❌ | 0 files | 0 tests |
-| US-004 | ✅ | 1 file | 8 tests |
-
-Stories without tests: US-003 (Register with email)
-Action: Create tests/RegistrationServiceTest.php
-
-User: /project:coverage-map --format mermaid
-
-Claude: [generates Mermaid coverage diagram]
-```
-
-## Related Commands
-
-- `/project:trace` - Full bidirectional traceability matrix
-- `/project:generate-prd` - Generate PRD with requirement IDs
-- `/project:generate-backlog` - Create backlog from PRD
-- `/project:update-stories` - Add missing fields to stories
+Run `/project:trace --gaps $ARGUMENTS`: read `.claude/commands/project/trace.md` and follow it with these arguments.

package/Project/i18n/en/commands/critical-path.md

@@ -1,127 +1,9 @@
 ---
-name: critical-path
-description: Identify the critical path through story dependencies to optimize sprint execution
-arguments:
-  - name: sprint
-    description: Sprint ID to analyze (e.g., Sprint-3)
-    required: false
-  - name: velocity
-    description: Team velocity in points per sprint for timeline estimation
-    required: false
+description: "Deprecated (removed in 9.0): use /project:report deps --critical"
+deprecated: true
+replaced-by: /project:report
 ---
 
-# /project:critical-path
+> ⚠️ `/project:critical-path` is deprecated and will be removed in 9.0. Use `/project:report deps --critical`.
 
-## Mission
-
-Identify the critical path through story dependencies — the longest sequence of dependent stories that determines the minimum time to complete all work. Use this to optimize sprint planning and identify where delays would cascade.
-
-## Prerequisites
-
-- `project-management/backlog/` contains user stories with `Depends on:` fields
-- Stories have story points estimated
-- Optional: `.bmad/sprint-status.yaml` for current progress
-
-## 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: Build Dependency Graph
-
-1. Load all stories (or filter by sprint)
-2. Extract `Depends on:` relationships
-3. Build a directed acyclic graph (DAG)
-4. Validate no circular dependencies exist
-
-### Step 2: Calculate Critical Path
-
-1. Apply topological sort to the dependency graph
-2. Calculate earliest start and finish times for each story
-3. Calculate latest start and finish times
-4. Identify stories with zero slack (critical path)
-5. Sum story points along the critical path
-
-### Step 3: Identify Slack
-
-For non-critical stories:
-- Calculate total slack (how much delay is acceptable)
-- Identify near-critical paths (slack < 2 story points)
-- Flag stories that could become critical if delayed
-
-### Step 4: Generate Timeline
-
-```
-+==========================================================+
-|           CRITICAL PATH ANALYSIS                         |
-+==========================================================+
-| Sprint: Sprint-3 | Velocity: 21 pts/sprint               |
-+==========================================================+
-|                                                          |
-| Critical Path (13 story points):                         |
-| -------------------------------------------------------- |
-|                                                          |
-| US-001 (5pts) -> US-002 (3pts) -> US-005 (5pts)         |
-| [Login Page]    [JWT Tokens]    [Admin Dashboard]        |
-|                                                          |
-| !! Critical path = 13pts > velocity 21pts                |
-|    Minimum: 1 sprint (if no blockers)                    |
-|                                                          |
-| Near-Critical Paths:                                     |
-| -------------------------------------------------------- |
-| US-001 (5pts) -> US-004 (3pts)  [slack: 2pts]           |
-|                                                          |
-| Parallel Execution Plan:                                 |
-| -------------------------------------------------------- |
-| Phase 1: US-001 + US-006 + US-007  (5+2+1 = 8pts)       |
-| Phase 2: US-002 + US-004           (3+3 = 6pts)          |
-| Phase 3: US-003 + US-005           (2+5 = 7pts)          |
-| Total: 21pts across 3 phases                             |
-|                                                          |
-| Stories with Slack:                                      |
-| -------------------------------------------------------- |
-| US-003: 5pts slack (can delay without impact)            |
-| US-004: 2pts slack (near-critical, monitor)              |
-| US-006: 8pts slack (fully flexible)                      |
-| US-007: 8pts slack (fully flexible)                      |
-+==========================================================+
-```
-
-### Step 5: Recommendations
-
-Based on analysis, provide:
-1. **Optimal execution order** respecting dependencies
-2. **Parallelization opportunities**
-3. **Risk assessment** for critical path stories
-4. **Suggestions** to shorten the critical path (split stories, etc.)
-
-## Example Session
-
-```
-User: /project:critical-path --sprint=Sprint-3 --velocity=21
-
-Claude: Analyzing critical path for Sprint-3...
-
-Critical Path: US-001 -> US-002 -> US-005 (13 story points)
-
-This means the minimum time to complete all dependent work is 13 story
-points of sequential effort, regardless of team size.
-
-Recommended execution plan:
-Phase 1 (8pts): US-001 [critical] + US-006, US-007 [independent]
-Phase 2 (6pts): US-002 [critical] + US-004 [near-critical]
-Phase 3 (7pts): US-005 [critical] + US-003 [has slack]
-
-Total: 21pts, fits within 1 sprint at velocity 21.
-
-!! Risk: If US-001 is delayed by 2+ days, the entire sprint is at risk.
-Recommendation: Assign strongest developer to US-001.
-```
-
-## Related Commands
-
-- `/project:dependencies` — View full dependency graph
-- `/project:trace` — View traceability matrix
-- `/sprint:next-story` — Get next story (considers dependencies)
-- `/sprint:status` — View sprint progress
+Run `/project:report deps --critical $ARGUMENTS`: read `.claude/commands/project/report.md` and follow it with these arguments.