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

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

@@ -1,203 +1,9 @@
 ---
-description: Validate Tech Spec against quality gate (≥90%)
-argument-hint: [techspec-file]
+description: "Deprecated (removed in 9.0): use /gate:check spec"
+deprecated: true
+replaced-by: /gate:check
 ---
 
-# Validate Tech Spec Gate
+> ⚠️ `/gate:validate-techspec` is deprecated and will be removed in 9.0. Use `/gate:check spec`.
 
-Validate a Technical Specification against the Tech Spec quality gate.
-The Tech Spec must score at least 90% to pass.
-
-## Arguments
-
-$ARGUMENTS (format: [techspec-file])
-- **techspec-file** (optional): Path to Tech Spec file. Default: `docs/tech-spec.md`
-
-## Gate Criteria
-
-| Criterion | Weight | Required | Description |
-|-----------|--------|----------|-------------|
-| Architecture Overview | 12% | Yes | System design description |
-| Architecture Diagram | 10% | Yes | Visual representation |
-| Components | 12% | Yes | Module/service definitions |
-| Data Model | 10% | Yes | Database/entity design |
-| API Contracts | 10% | Yes | Endpoint specifications |
-| Security | 12% | Yes | Auth and security measures |
-| Performance | 8% | No | Performance requirements |
-| Error Handling | 8% | No | Error strategy |
-| Testing Strategy | 10% | Yes | Test approach |
-| Deployment | 8% | No | CI/CD and release |
-
-**Threshold: 90%**
-
-## Process
-
-### Step 1: Locate Tech Spec file
-
-1. Use provided path or default `docs/tech-spec.md`
-2. Verify file exists
-3. Load content for analysis
-
-### Step 2: Validate each criterion
-
-For each criterion:
-- Check for relevant sections and keywords
-- Verify diagrams exist (mermaid, images)
-- Validate technical depth
-
-### Step 3: Calculate score
-
-Score = sum of passed criterion weights
-
-### Step 4: Generate report
-
-Show detailed results with suggestions.
-
-## Output Format
-
-### Passing Tech Spec
-
-```
-═══════════════════════════════════════════════════════
-          Tech Spec Quality Gate Validation
-═══════════════════════════════════════════════════════
-
-File: docs/tech-spec.md
-Threshold: 90%
-
-Validation Results:
-──────────────────────────────────────────────────────
-✅ Architecture Overview (12%)
-   Found: Clean Architecture with 4 layers described
-
-✅ Architecture Diagram (10%)
-   Found: Mermaid diagram in "System Design" section
-
-✅ Components (12%)
-   Found: 6 components with responsibilities defined
-
-✅ Data Model (10%)
-   Found: Entity definitions with relationships
-
-✅ API Contracts (10%)
-   Found: REST endpoints with request/response schemas
-
-✅ Security (12%)
-   Found: JWT auth, RBAC, encryption at rest
-
-✅ Performance (8%)
-   Found: Latency targets, caching strategy
-
-✅ Error Handling (8%)
-   Found: Error codes, retry policies
-
-✅ Testing Strategy (10%)
-   Found: Unit, integration, e2e test plans
-
-✅ Deployment (8%)
-   Found: CI/CD pipeline, blue-green deployment
-
-Score: 100/100 (100%)
-──────────────────────────────────────────────────────
-
-✅ TECH SPEC GATE PASSED
-
-Ready to proceed to Backlog creation.
-Next: /arch:handoff po
-═══════════════════════════════════════════════════════
-```
-
-### Failing Tech Spec
-
-```
-═══════════════════════════════════════════════════════
-          Tech Spec Quality Gate Validation
-═══════════════════════════════════════════════════════
-
-File: docs/tech-spec.md
-Threshold: 90%
-
-Validation Results:
-──────────────────────────────────────────────────────
-✅ Architecture Overview (12%)
-❌ Architecture Diagram (10%)
-   Missing: No diagram found (mermaid, PNG, SVG)
-✅ Components (12%)
-✅ Data Model (10%)
-⚠️ API Contracts (10%)
-   Partial: Endpoints listed but no schemas
-❌ Security (12%)
-   Missing: No authentication/authorization defined
-✅ Performance (8%)
-✅ Error Handling (8%)
-✅ Testing Strategy (10%)
-⚠️ Deployment (8%)
-   Partial: CI mentioned but no CD strategy
-
-Score: 68/100 (68%)
-──────────────────────────────────────────────────────
-
-❌ TECH SPEC GATE FAILED (need 90%, got 68%)
-
-Required Actions:
-──────────────────────────────────────────────────────
-1. Add architecture diagram
-   ```mermaid
-   graph TB
-     Client --> API[API Gateway]
-     API --> Service[Business Logic]
-     Service --> DB[(Database)]
-   ```
-
-2. Define security strategy
-   - Authentication method (JWT, OAuth2)
-   - Authorization model (RBAC, ABAC)
-   - Data encryption approach
-
-3. Complete API contracts with schemas
-   - Request/response JSON schemas
-   - Error response formats
-   - Versioning strategy
-
-4. Add deployment strategy
-   - CI/CD pipeline stages
-   - Environment promotion
-   - Rollback procedures
-
-Re-run after fixes: /gate:validate-techspec
-═══════════════════════════════════════════════════════
-```
-
-## Example
-
-```
-/gate:validate-techspec
-/gate:validate-techspec docs/auth-tech-spec.md
-```
-
-## Architecture Review
-
-Consider creating an ADR for significant decisions:
-```
-/arch:adr "JWT vs Session-based authentication"
-```
-
-Gate configuration: `.bmad/gates/techspec-gate.yaml`
-
-## Next Step
-
-```
-╔══════════════════════════════════════════════════════════╗
-║                      NEXT STEP                           ║
-╠══════════════════════════════════════════════════════════╣
-║                                                          ║
-║  If PASS (≥ threshold):                                  ║
-║  → /gate:validate-backlog                                ║
-║    Validate the backlog                                  ║
-║                                                          ║
-║  If FAIL (< threshold):                                  ║
-║  → Correct the tech spec issues                          ║
-║  → /gate:validate-techspec (re-run after corrections)    ║
-║                                                          ║
-╚══════════════════════════════════════════════════════════╝
-```
+Run `/gate:check spec $ARGUMENTS`: read `.claude/commands/gate/check.md` and follow it with these arguments.

package/Project/i18n/en/Sprint/commands/auto-route.md

@@ -1,233 +1,9 @@
 ---
-description: Execute automatic routing rules for story transitions
-argument-hint: [--dry-run]
+description: "Deprecated (removed in 9.0): use /project:backlog move story --auto"
+deprecated: true
+replaced-by: /project:backlog
 ---
 
-# Sprint Auto Route
+> ⚠️ `/sprint:auto-route` is deprecated and will be removed in 9.0. Use `/project:backlog move story --auto`.
 
-Execute automatic routing rules to transition stories based on their current state and completion metrics.
-
-## Arguments
-
-$ARGUMENTS (format: [--dry-run])
-- **--dry-run** (optional): Preview transitions without applying them
-
-## Process
-
-### Step 1: Load sprint status
-
-1. Read `.bmad/sprint-status.yaml`
-2. Load routing rules from `routing.auto_transitions.rules`
-3. Get all stories
-
-### Step 2: Evaluate rules
-
-For each story, evaluate all routing rules:
-
-**Rule: all_tasks_complete**
-```yaml
-when: "tasks.completed == tasks.total && tasks.total > 0"
-from: "in-progress"
-to: "review"
-```
-
-**Rule: review_approved**
-```yaml
-when: "review.approved == true"
-from: "review"
-to: "done"
-```
-
-**Rule: blocked_detection**
-```yaml
-when: "blocked_reason != null"
-from: "*"
-to: "blocked"
-```
-
-**Rule: unblocked**
-```yaml
-when: "blocked_reason == null && previous_status != null"
-from: "blocked"
-to: "previous_status"
-```
-
-### Step 3: Check prerequisites
-
-Before auto-transitioning, verify:
-- Gate requirements for target status
-- No conflicting rules
-- Story is not manually locked
-
-### Step 4: Execute transitions (unless --dry-run)
-
-For each triggered rule:
-1. Log the transition
-2. Update status
-3. Record in history with `by: "auto-route"`
-4. Apply side effects (TDD phase, etc.)
-
-### Step 5: Report results
-
-Show:
-- Number of rules evaluated
-- Transitions made
-- Stories unchanged
-- Any errors or warnings
-
-## Output Format
-
-### Dry Run
-
-```
-═══════════════════════════════════════════════════════
-           Auto-Route Preview (DRY RUN)
-═══════════════════════════════════════════════════════
-
-Evaluating 4 routing rules against 8 stories...
-
-Would transition:
-──────────────────────────────────────────────────────
-📖 US-005: User authentication
-   Rule: all_tasks_complete
-   in-progress → review
-   Reason: 5/5 tasks completed
-
-📖 US-008: Email verification
-   Rule: all_tasks_complete
-   in-progress → review
-   Reason: 3/3 tasks completed
-
-📖 US-003: OAuth integration
-   Rule: unblocked
-   blocked → in-progress
-   Reason: blocked_reason cleared
-
-Summary:
-──────────────────────────────────────────────────────
-Rules evaluated: 4
-Stories checked: 8
-Would transition: 3
-No change needed: 5
-
-Run without --dry-run to apply transitions.
-═══════════════════════════════════════════════════════
-```
-
-### Applied Transitions
-
-```
-═══════════════════════════════════════════════════════
-              Auto-Route Results
-═══════════════════════════════════════════════════════
-
-Evaluating 4 routing rules against 8 stories...
-
-Transitions applied:
-──────────────────────────────────────────────────────
-✅ US-005: in-progress → review
-   Rule: all_tasks_complete
-   Tasks: 5/5 completed
-
-✅ US-008: in-progress → review
-   Rule: all_tasks_complete
-   Tasks: 3/3 completed
-
-✅ US-003: blocked → in-progress
-   Rule: unblocked
-   Previous status restored
-
-Summary:
-──────────────────────────────────────────────────────
-Rules evaluated: 4
-Stories checked: 8
-Transitioned: 3
-No change needed: 5
-
-Sprint status updated. Run /sprint:status --bmad to view.
-═══════════════════════════════════════════════════════
-```
-
-### No Transitions Needed
-
-```
-═══════════════════════════════════════════════════════
-              Auto-Route Results
-═══════════════════════════════════════════════════════
-
-Evaluating 4 routing rules against 8 stories...
-
-No automatic transitions needed.
-──────────────────────────────────────────────────────
-All stories are in appropriate states based on their
-current completion metrics.
-
-Stories by status:
-  📋 Backlog: 2
-  🎯 Ready: 3
-  🔄 In Progress: 2 (tasks pending)
-  ✅ Done: 1
-═══════════════════════════════════════════════════════
-```
-
-## Example
-
-```
-/sprint:auto-route --dry-run
-/sprint:auto-route
-```
-
-## Custom Rules
-
-Add custom rules to `.bmad/sprint-status.yaml`:
-
-```yaml
-routing:
-  auto_transitions:
-    enabled: true
-    rules:
-      # Custom rule: story too long in review
-      - name: "review_timeout"
-        description: "Flag stories in review > 2 days"
-        when: "status == 'review' && days_in_status > 2"
-        action: "flag"  # flag | transition | notify
-
-      # Custom rule: high priority first
-      - name: "priority_bump"
-        description: "Auto-assign high priority stories"
-        when: "priority == 'high' && status == 'ready-for-dev'"
-        action: "notify"
-```
-
-## Integration
-
-Auto-route can be triggered:
-1. Manually via this command
-2. Automatically in Stop hook
-3. After task completion
-4. On session start (configurable)
-
-Configure in `.bmad/sprint-status.yaml`:
-```yaml
-routing:
-  auto_transitions:
-    enabled: true
-    run_on_session_start: false
-    run_on_task_complete: true
-```
-
-## Next Step
-
-```
-╔══════════════════════════════════════════════════════════╗
-║                      NEXT STEP                           ║
-╠══════════════════════════════════════════════════════════╣
-║                                                          ║
-║  → /sprint:next-story                                    ║
-║    Pick the next routed story                            ║
-║                                                          ║
-║  → /sprint:dev                                           ║
-║    Start development                                     ║
-║                                                          ║
-╚══════════════════════════════════════════════════════════╝
-```
+Run `/project:backlog move story --auto $ARGUMENTS`: read `.claude/commands/project/backlog.md` and follow it with these arguments.