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

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

@@ -1,265 +1,9 @@
 ---
-description: Show comprehensive quality gates report
-argument-hint: [--detailed]
+description: "Deprecated (removed in 9.0): use /gate:check all"
+deprecated: true
+replaced-by: /gate:check
 ---
 
-# Quality Gates Report
+> ⚠️ `/gate:report` is deprecated and will be removed in 9.0. Use `/gate:check all`.
 
-Generate a comprehensive report of all BMAD quality gates status.
-
-## Arguments
-
-$ARGUMENTS (format: [--detailed])
-- **--detailed** (optional): Include validation details for each gate
-
-## Process
-
-### Step 1: Identify applicable gates
-
-Determine which gates apply based on project state:
-- PRD Gate: If PRD file exists
-- Tech Spec Gate: If tech spec file exists
-- Backlog Gate: If stories exist in sprint-status
-- Sprint Ready Gate: If sprint metadata exists
-- Story Gates: For each in-progress/review story
-
-### Step 2: Run validations
-
-Execute each applicable gate validator:
-1. PRD validation (if docs/prd.md exists)
-2. Tech Spec validation (if docs/tech-spec.md exists)
-3. Backlog INVEST validation
-4. Sprint readiness validation
-5. Individual story DoD validations
-
-### Step 3: Aggregate results
-
-Compile results into summary report.
-
-### Step 4: Generate recommendations
-
-Based on failures, suggest prioritized actions.
-
-## Output Format
-
-### Summary Report
-
-```
-═══════════════════════════════════════════════════════
-            BMAD Quality Gates Report
-═══════════════════════════════════════════════════════
-
-Project: claude-craft
-Sprint: sprint-3 - User Management
-Generated: 2026-01-29 10:00:00
-
-Gate Summary:
-══════════════════════════════════════════════════════
-| Gate | Threshold | Score | Status |
-|------|-----------|-------|--------|
-| PRD | 80% | 90% | ✅ PASS |
-| Tech Spec | 90% | 92% | ✅ PASS |
-| Backlog | 6/6 | 5.8/6 avg | ⚠️ WARN |
-| Sprint Ready | 100% | 100% | ✅ PASS |
-| Story DoD | 100% | varies | 📊 |
-
-Story DoD Status:
-──────────────────────────────────────────────────────
-| Story | Status | DoD Score | Gate |
-|-------|--------|-----------|------|
-| US-010 | in-progress | 45% | ⏳ |
-| US-011 | in-progress | 60% | ⏳ |
-| US-012 | review | 85% | ⚠️ |
-| US-013 | done | 100% | ✅ |
-
-Overall Health: 🟢 Good
-──────────────────────────────────────────────────────
-4/5 gates passing
-8/10 stories on track
-No critical blockers
-
-Recommendations:
-──────────────────────────────────────────────────────
-1. ⚠️ US-002 missing story points (INVEST: E)
-   Run: /project:update-story US-002 --points 3
-
-2. ⚠️ US-012 needs code review to complete
-   Create PR and request review
-
-3. 💡 Consider adding capacity planning
-   Add metadata.capacity_points to sprint config
-
-Commands:
-  /gate:validate-prd       Re-run PRD gate
-  /gate:validate-backlog   Re-run backlog gate
-  /gate:validate-story US-012  Check specific story
-═══════════════════════════════════════════════════════
-```
-
-### Detailed Report
-
-```
-═══════════════════════════════════════════════════════
-            BMAD Quality Gates Report (Detailed)
-═══════════════════════════════════════════════════════
-
-Project: claude-craft
-Sprint: sprint-3 - User Management
-
-═══════════════════════════════════════════════════════
-                    PRD Gate
-═══════════════════════════════════════════════════════
-File: docs/prd.md
-Threshold: 80%
-Score: 90%
-Status: ✅ PASS
-
-Criteria:
-  ✅ Problem Statement (15%)
-  ✅ Target Users (15%)
-  ✅ Goals/Objectives (15%)
-  ✅ Success Metrics (15%)
-  ✅ Scope/Boundaries (10%)
-  ✅ User Stories Overview (10%)
-  ✅ Assumptions (10%)
-  ⚠️ Risks (10%) - Partial
-
-═══════════════════════════════════════════════════════
-                  Tech Spec Gate
-═══════════════════════════════════════════════════════
-File: docs/tech-spec.md
-Threshold: 90%
-Score: 92%
-Status: ✅ PASS
-
-Criteria:
-  ✅ Architecture Overview (12%)
-  ✅ Architecture Diagram (10%)
-  ✅ Components (12%)
-  ✅ Data Model (10%)
-  ✅ API Contracts (10%)
-  ✅ Security (12%)
-  ✅ Performance (8%)
-  ⚠️ Error Handling (8%) - Basic
-  ✅ Testing Strategy (10%)
-  ✅ Deployment (8%)
-
-═══════════════════════════════════════════════════════
-                  Backlog Gate
-═══════════════════════════════════════════════════════
-Stories: 10
-Threshold: 6/6 INVEST
-Average Score: 5.8/6
-Status: ⚠️ WARNING
-
-Stories with issues:
-  ⚠️ US-002: 5/6 (missing: Estimable)
-  ⚠️ US-008: 5/6 (missing: Small - 10 points)
-
-═══════════════════════════════════════════════════════
-                Sprint Ready Gate
-═══════════════════════════════════════════════════════
-Sprint: sprint-3
-Threshold: 100%
-Score: 100%
-Status: ✅ PASS
-
-Criteria:
-  ✅ Sprint Metadata
-  ✅ Sprint Goal
-  ✅ Stories Ready (5)
-  ✅ Stories Estimated
-  ✅ Capacity Check (84%)
-  ✅ Dependencies Resolved
-
-═══════════════════════════════════════════════════════
-                  Story DoD Gates
-═══════════════════════════════════════════════════════
-
-US-010: User registration
-  Status: in-progress
-  DoD Score: 45%
-  ❌ Tasks: 2/5
-  ❌ Tests: red phase
-  ⚠️ AC: 1/3
-  ❌ Review: not started
-
-US-011: User login
-  Status: in-progress
-  DoD Score: 60%
-  ⚠️ Tasks: 3/4
-  ✅ Tests: green phase
-  ⚠️ AC: 2/3
-  ❌ Review: not started
-
-US-012: Profile page
-  Status: review
-  DoD Score: 85%
-  ✅ Tasks: 4/4
-  ✅ Tests: refactor phase
-  ✅ AC: 3/3
-  ⚠️ Review: pending approval
-
-US-013: Password reset
-  Status: done
-  DoD Score: 100%
-  ✅ All criteria met
-
-═══════════════════════════════════════════════════════
-                   Action Items
-═══════════════════════════════════════════════════════
-
-Priority 1 (Blocking):
-  None
-
-Priority 2 (Should fix):
-  1. US-002: Add story points estimate
-  2. US-008: Split into smaller stories
-
-Priority 3 (Nice to have):
-  1. Add risk mitigations to PRD
-  2. Enhance error handling in tech spec
-═══════════════════════════════════════════════════════
-```
-
-## Example
-
-```
-/gate:report
-/gate:report --detailed
-```
-
-## Gate Configuration
-
-Gates are configured in `.bmad/gates/`:
-- `prd-gate.yaml`
-- `techspec-gate.yaml`
-- `backlog-gate.yaml`
-- `story-gate.yaml`
-- `sprint-ready-gate.yaml`
-
-## Integration
-
-The report can be:
-1. Generated on demand via this command
-2. Included in sprint retrospective
-3. Used for project health monitoring
-4. Exported for stakeholder reporting
-
-## Next Step
-
-```
-╔══════════════════════════════════════════════════════════╗
-║                      NEXT STEP                           ║
-╠══════════════════════════════════════════════════════════╣
-║                                                          ║
-║  Run the specific gate that needs attention:             ║
-║                                                          ║
-║  • /gate:validate-prd      — PRD quality gate            ║
-║  • /gate:validate-techspec — Tech spec gate              ║
-║  • /gate:validate-backlog  — Backlog gate                ║
-║  • /gate:validate-sprint   — Sprint readiness gate       ║
-║  • /gate:validate-story    — Story DoD gate              ║
-║                                                          ║
-╚══════════════════════════════════════════════════════════╝
-```
+Run `/gate:check all $ARGUMENTS`: read `.claude/commands/gate/check.md` and follow it with these arguments.

package/Project/i18n/en/Gate/commands/validate-alignment.md

@@ -1,123 +1,9 @@
 ---
-description: Validate spec-code alignment to ensure implementation matches specifications
-argument-hint: [story-id]
+description: "Deprecated (removed in 9.0): use /gate:check alignment"
+deprecated: true
+replaced-by: /gate:check
 ---
 
-# Validate Spec-Code Alignment
+> ⚠️ `/gate:validate-alignment` is deprecated and will be removed in 9.0. Use `/gate:check alignment`.
 
-Validate that the code implementation aligns with the specifications (PRD, user stories, tech spec). This gate ensures no specification drift has occurred during implementation.
-
-## Arguments
-
-$ARGUMENTS (format: [story-id])
-- **story-id** (optional): Story ID to check alignment for. Default: all stories in current sprint
-
-## Gate Criteria
-
-| Criterion | Weight | Required | Description |
-|-----------|--------|----------|-------------|
-| Requirement coverage | 20% | Yes | All FR-xxx from PRD are covered by stories |
-| Story-code mapping | 20% | Yes | All stories have corresponding code references |
-| AC-test mapping | 20% | Yes | All acceptance criteria have corresponding tests |
-| Tech spec adherence | 15% | Yes | Implementation follows tech spec design |
-| Constitution compliance | 15% | Yes | Code respects project constitution |
-| Scope drift detection | 10% | No | No unreferenced code changes |
-
-**Threshold: 85%**
-
-## Process
-
-### Step 1: Load Specifications
-
-1. Load PRD with FR-xxx requirement IDs
-2. Load user stories with `Implements:` references
-3. Load tech spec with requirement mapping
-4. Load project constitution (if exists)
-
-### Step 2: Trace Forward (Spec → Code)
-
-For each requirement FR-xxx in the PRD:
-1. Find stories that implement it (`Implements: FR-xxx`)
-2. For each story, find code files with `// Story: US-xxx`
-3. For each AC, find corresponding test
-4. Record coverage status
-
-### Step 3: Trace Backward (Code → Spec)
-
-For each code file with story references:
-1. Verify the story reference exists in the backlog
-2. Verify the story is assigned to the correct sprint
-3. Check for code changes without story references (scope drift)
-
-### Step 4: Validate Constitution
-
-If `project-management/constitution.md` exists:
-1. Check technical constraints compliance
-2. Verify design principles adherence
-3. Check NFR targets
-
-### Step 5: Score and Report
-
-Calculate weighted score across all criteria. Generate detailed report.
-
-## Output Format
-
-### Passing Gate
-
-```
-╔══════════════════════════════════════════════════════════╗
-║          SPEC-CODE ALIGNMENT GATE ✅                     ║
-╠══════════════════════════════════════════════════════════╣
-║ Story: US-012 | Score: 92%                               ║
-╠══════════════════════════════════════════════════════════╣
-║                                                          ║
-║ ✅ Requirement coverage      3/3 FR-xxx covered (100%)   ║
-║ ✅ Story-code mapping        4 files reference US-012     ║
-║ ✅ AC-test mapping           3/3 ACs have tests           ║
-║ ✅ Tech spec adherence       Design matches spec          ║
-║ ✅ Constitution compliance   All constraints met          ║
-║ ⚠️  Scope drift              1 unreferenced file found    ║
-║                                                          ║
-║ → Alignment verified, ready for merge                    ║
-╚══════════════════════════════════════════════════════════╝
-```
-
-### Failing Gate
-
-```
-╔══════════════════════════════════════════════════════════╗
-║          SPEC-CODE ALIGNMENT GATE ❌                     ║
-╠══════════════════════════════════════════════════════════╣
-║ Story: US-012 | Score: 65%                               ║
-╠══════════════════════════════════════════════════════════╣
-║                                                          ║
-║ ✅ Requirement coverage      3/3 FR-xxx covered           ║
-║ ❌ Story-code mapping        2 files missing references   ║
-║ ❌ AC-test mapping           AC-2 has no test             ║
-║ ✅ Tech spec adherence       Design matches spec          ║
-║ ❌ Constitution compliance   Perf NFR not met             ║
-║ ⚠️  Scope drift              3 unreferenced files         ║
-║                                                          ║
-║ Actions required:                                        ║
-║ 1. Add // Story: US-012 to ProfileService.ts             ║
-║ 2. Add // Story: US-012 to ProfileValidator.ts           ║
-║ 3. Write test for AC-2: User can edit email              ║
-║ 4. Optimize profile API to meet <200ms target            ║
-║                                                          ║
-║ → Fix issues before merging                              ║
-╚══════════════════════════════════════════════════════════╝
-```
-
-## Example
-
-```
-/gate:validate-alignment US-012
-/gate:validate-alignment          # All stories in current sprint
-```
-
-## Related Commands
-
-- `/project:trace` — View traceability matrix
-- `/project:coverage-map` — Check requirement coverage
-- `/project:checkpoint` — Run phase-specific checkpoints
-- `/gate:validate-story` — Validate story completeness
+Run `/gate:check alignment $ARGUMENTS`: read `.claude/commands/gate/check.md` and follow it with these arguments.

package/Project/i18n/en/Gate/commands/validate-backlog.md

@@ -1,240 +1,9 @@
 ---
-description: "Validate backlog stories against INVEST criteria"
-argument-hint: "[story-id] [--no-gate]"
+description: "Deprecated (removed in 9.0): use /gate:check backlog"
+deprecated: true
+replaced-by: /gate:check
 ---
 
-# Validate Backlog Gate
+> ⚠️ `/gate:validate-backlog` is deprecated and will be removed in 9.0. Use `/gate:check backlog`.
 
-Validate User Stories against INVEST criteria.
-All stories must pass all 6 INVEST criteria.
-
-## Arguments
-
-$ARGUMENTS (format: [story-id] [--no-gate])
-- **story-id** (optional): Specific story to validate (e.g., US-001). If omitted, validates all stories.
-- **--no-gate** (optional): Run simple INVEST validation only (skip quality gate enforcement, scoring thresholds, and pass/fail verdict). Useful for quick checks during refinement without blocking on gate criteria.
-
-## INVEST Criteria
-
-| Letter | Criterion | Description | Checks |
-|--------|-----------|-------------|--------|
-| **I** | Independent | Can be developed alone | No blocking dependencies |
-| **N** | Negotiable | Details can be discussed | Has description, not over-specified |
-| **V** | Valuable | Delivers user value | Has acceptance criteria, benefit statement |
-| **E** | Estimable | Can be estimated | Has story points |
-| **S** | Small | Fits in one sprint | ≤ 8 story points |
-| **T** | Testable | Can be tested | Has acceptance criteria |
-
-**Threshold: 6/6 for each story**
-
-## Process
-
-### Step 1: Load stories
-
-1. Read `.bmad/sprint-status.yaml`
-2. Get specified story or all stories
-3. Load story details
-
-### Step 2: Validate INVEST for each story
-
-For each criterion:
-- **Independent**: Check `blocked_by` is empty
-- **Negotiable**: Check description length, task count
-- **Valuable**: Check acceptance criteria exist
-- **Estimable**: Check story points > 0
-- **Small**: Check story points ≤ 8
-- **Testable**: Check acceptance criteria count > 0
-
-### Step 3: Calculate scores
-
-Per-story INVEST score (0-6)
-
-### Step 4: Generate report
-
-Show individual and aggregate results.
-
-## Output Format
-
-### All Stories Pass
-
-```
-═══════════════════════════════════════════════════════
-          Backlog INVEST Gate Validation
-═══════════════════════════════════════════════════════
-
-Validating 8 stories...
-
-Story Results:
-──────────────────────────────────────────────────────
-✅ US-001: User login
-   [I] ✓ Independent - No dependencies
-   [N] ✓ Negotiable - Clear description
-   [V] ✓ Valuable - 3 acceptance criteria
-   [E] ✓ Estimable - 5 story points
-   [S] ✓ Small - 5 ≤ 8 points
-   [T] ✓ Testable - Gherkin AC defined
-   Score: 6/6 ✅
-
-✅ US-002: User registration
-   Score: 6/6 ✅
-
-✅ US-003: Password reset
-   Score: 6/6 ✅
-
-[... more stories ...]
-
-Summary:
-──────────────────────────────────────────────────────
-Stories validated: 8
-Passing (6/6): 8
-Warnings (4-5/6): 0
-Failing (<4/6): 0
-
-✅ BACKLOG GATE PASSED
-
-All stories meet INVEST criteria.
-Ready for sprint planning.
-═══════════════════════════════════════════════════════
-```
-
-### Stories Failing
-
-```
-═══════════════════════════════════════════════════════
-          Backlog INVEST Gate Validation
-═══════════════════════════════════════════════════════
-
-Validating 8 stories...
-
-Story Results:
-──────────────────────────────────────────────────────
-✅ US-001: User login
-   Score: 6/6 ✅
-
-⚠️ US-002: User registration
-   [I] ✓ Independent
-   [N] ✓ Negotiable
-   [V] ✓ Valuable
-   [E] ✗ Estimable - No story points
-   [S] ? Small - Cannot check without points
-   [T] ✓ Testable
-   Score: 4/6 ⚠️
-
-❌ US-003: Complete rewrite of auth system
-   [I] ✗ Independent - Blocked by US-001, US-002
-   [N] ✗ Negotiable - 15 tasks (too specified)
-   [V] ✓ Valuable
-   [E] ✓ Estimable - 13 points
-   [S] ✗ Small - 13 > 8 points
-   [T] ✓ Testable
-   Score: 3/6 ❌
-
-Summary:
-──────────────────────────────────────────────────────
-Stories validated: 8
-Passing (6/6): 6
-Warnings (4-5/6): 1
-Failing (<4/6): 1
-
-❌ BACKLOG GATE FAILED
-
-Required Actions:
-──────────────────────────────────────────────────────
-US-002:
-  → Add story points estimate
-  → Run: /project:update-story US-002 --points 3
-
-US-003:
-  → Split into smaller stories (≤8 points each)
-  → Remove unnecessary task details
-  → Resolve dependencies or reorder
-  → Consider: /project:split-story US-003
-
-Re-run after fixes: /gate:validate-backlog
-═══════════════════════════════════════════════════════
-```
-
-### Single Story Validation
-
-```
-═══════════════════════════════════════════════════════
-          INVEST Validation: US-005
-═══════════════════════════════════════════════════════
-
-📖 US-005: Email verification
-
-INVEST Analysis:
-──────────────────────────────────────────────────────
-[I] ✓ Independent
-    No blocking dependencies
-
-[N] ✓ Negotiable
-    Description: 45 words
-    Tasks: 4 (reasonable)
-
-[V] ✓ Valuable
-    "As a user, I want to verify my email
-     so that I can secure my account"
-    Acceptance Criteria: 3
-
-[E] ✓ Estimable
-    Story Points: 3
-
-[S] ✓ Small
-    3 points ≤ 8 points
-
-[T] ✓ Testable
-    3 Gherkin scenarios defined
-
-Score: 6/6 ✅
-──────────────────────────────────────────────────────
-
-✅ Story meets INVEST criteria
-
-Status: ready-for-dev
-═══════════════════════════════════════════════════════
-```
-
-## Example
-
-```
-/gate:validate-backlog
-/gate:validate-backlog US-005
-```
-
-## Fixing Common Issues
-
-### Story too large (S)
-```
-/project:split-story US-003
-```
-
-### Missing story points (E)
-```
-/project:update-story US-002 --points 3
-```
-
-### Missing acceptance criteria (V, T)
-```
-/project:add-ac US-002 "Given... When... Then..."
-```
-
-Gate configuration: `.bmad/gates/backlog-gate.yaml`
-
-## Next Step
-
-```
-╔══════════════════════════════════════════════════════════╗
-║                      NEXT STEP                           ║
-╠══════════════════════════════════════════════════════════╣
-║                                                          ║
-║  If PASS (≥ threshold):                                  ║
-║  → /gate:validate-sprint                                 ║
-║    Validate sprint readiness                             ║
-║                                                          ║
-║  If FAIL (< threshold):                                  ║
-║  → Correct the identified issues                         ║
-║  → /gate:validate-backlog (re-run after corrections)     ║
-║                                                          ║
-╚══════════════════════════════════════════════════════════╝
-```
+Run `/gate:check backlog $ARGUMENTS`: read `.claude/commands/gate/check.md` and follow it with these arguments.