musubi-sdd 5.0.0 → 5.6.1

package/src/templates/agents/claude-code/skills/constitution-enforcer/constitutional-articles.md

@@ -11,12 +11,14 @@ The 9 Constitutional Articles define immutable governance rules for MUSUBI SDD.
 > **Every feature MUST begin as a standalone library.**
 
 ### Rationale
+
 - Libraries are reusable across projects
 - Encourages modular design
 - Enables testing in isolation
 - Prevents tight coupling to frameworks
 
 ### Compliance Criteria
+
 ```
 ✅ COMPLIANT:
 - Feature implemented in lib/[feature]/
@@ -30,6 +32,7 @@ The 9 Constitutional Articles define immutable governance rules for MUSUBI SDD.
 ```
 
 ### Enforcement
+
 ```bash
 # Check implementation location
 if [[ "$feature_path" =~ ^(src/app/|web/) ]]; then
@@ -46,12 +49,14 @@ fi
 > **All libraries MUST expose CLI interfaces.**
 
 ### Rationale
+
 - CLI enables testing without UI
 - Supports automation and scripting
 - Provides consistent interface across platforms
 - Enables quick validation and debugging
 
 ### Compliance Criteria
+
 ```
 ✅ COMPLIANT:
 - lib/auth/cli.ts or lib/auth/__main__.py exists
@@ -65,6 +70,7 @@ fi
 ```
 
 ### Enforcement
+
 ```bash
 # Check for CLI entry point
 cli_files=("cli.ts" "cli.js" "__main__.py" "main.go")
@@ -89,12 +95,14 @@ done
 > **NON-NEGOTIABLE: No code before tests.**
 
 ### Rationale
+
 - Tests define expected behavior
 - Prevents untested code from entering codebase
 - Enforces Red-Green-Refactor discipline
 - Creates living documentation
 
 ### Compliance Criteria
+
 ```
 ✅ COMPLIANT:
 - Test file committed before source file
@@ -108,11 +116,12 @@ done
 ```
 
 ### Enforcement
+
 ```bash
 # Check git history for test-first
 for commit in $(git log --oneline feature-branch..HEAD); do
     files=$(git show --name-only $commit)
-    
+
     # Check if source files added before tests
     if echo "$files" | grep -q "src/" && ! echo "$files" | grep -q "test"; then
         # Check previous commits for tests
@@ -131,21 +140,24 @@ done
 > **All requirements MUST use EARS patterns.**
 
 ### Rationale
+
 - Unambiguous requirement language
 - Testable specifications
 - Industry-standard format
 - Reduces misinterpretation
 
 ### EARS Patterns
-| Pattern | Template | Use Case |
-|---------|----------|----------|
-| Ubiquitous | The system SHALL [action] | Always applicable |
-| Event-driven | WHEN [event] the system SHALL [action] | Triggered by event |
-| State-driven | WHILE [state] the system SHALL [action] | During condition |
-| Optional | WHERE [feature] the system SHALL [action] | Optional features |
-| Unwanted | IF [condition] THEN the system SHALL [action] | Error handling |
+
+| Pattern      | Template                                      | Use Case           |
+| ------------ | --------------------------------------------- | ------------------ |
+| Ubiquitous   | The system SHALL [action]                     | Always applicable  |
+| Event-driven | WHEN [event] the system SHALL [action]        | Triggered by event |
+| State-driven | WHILE [state] the system SHALL [action]       | During condition   |
+| Optional     | WHERE [feature] the system SHALL [action]     | Optional features  |
+| Unwanted     | IF [condition] THEN the system SHALL [action] | Error handling     |
 
 ### Compliance Criteria
+
 ```
 ✅ COMPLIANT:
 "WHEN user clicks login, the system SHALL validate credentials"
@@ -158,6 +170,7 @@ done
 ```
 
 ### Enforcement
+
 ```python
 invalid_keywords = ["should", "may", "could", "might", "would"]
 required_keywords = ["SHALL", "MUST"]
@@ -165,7 +178,7 @@ required_keywords = ["SHALL", "MUST"]
 for line in requirements:
     if any(kw in line.lower() for kw in invalid_keywords):
         VIOLATION(f"Article IV: Ambiguous keyword in '{line}'")
-    
+
     if "REQ-" in line and not any(kw in line for kw in required_keywords):
         WARNING(f"Article IV: Missing SHALL/MUST in '{line}'")
 ```
@@ -177,12 +190,14 @@ for line in requirements:
 > **100% traceability required: Requirement ↔ Design ↔ Task ↔ Code ↔ Test.**
 
 ### Rationale
+
 - Ensures every requirement is implemented
 - Prevents orphaned code
 - Enables impact analysis
 - Supports audit and compliance
 
 ### Traceability Chain
+
 ```
 REQ-001 (Requirement)
     ↓ (referenced in)
@@ -196,6 +211,7 @@ T-001 (Test)
 ```
 
 ### Compliance Criteria
+
 ```
 ✅ COMPLIANT:
 - 100% requirements have design mappings
@@ -211,19 +227,20 @@ T-001 (Test)
 ```
 
 ### Enforcement
+
 ```python
 def check_traceability():
     requirements = parse_requirements()
     design = parse_design()
     tasks = parse_tasks()
     tests = parse_tests()
-    
+
     for req in requirements:
         if req.id not in design.references:
             VIOLATION(f"Article V: {req.id} not in design")
         if req.id not in tests.references:
             VIOLATION(f"Article V: {req.id} not tested")
-    
+
     coverage = len(traced_requirements) / len(requirements) * 100
     if coverage < 100:
         VIOLATION(f"Article V: Traceability {coverage}% < 100%")
@@ -236,12 +253,14 @@ def check_traceability():
 > **All skills MUST check steering before work.**
 
 ### Rationale
+
 - Consistent architectural decisions
 - Technology stack awareness
 - Business context understanding
 - Prevents conflicting approaches
 
 ### Required Steering Files
+
 ```
 steering/
 ├── structure.md   # Architecture patterns
@@ -252,6 +271,7 @@ steering/
 ```
 
 ### Compliance Criteria
+
 ```
 ✅ COMPLIANT:
 - Steering files read at skill start
@@ -265,6 +285,7 @@ steering/
 ```
 
 ### Enforcement
+
 ```python
 def check_steering_compliance():
     if not exists("steering/structure.md"):
@@ -282,18 +303,21 @@ def check_steering_compliance():
 > **Prefer the simplest solution that satisfies requirements.**
 
 ### Rationale
+
 - Reduces maintenance burden
 - Improves readability
 - Faster development
 - Easier testing
 
 ### Simplicity Principles
+
 1. **YAGNI**: You Aren't Gonna Need It
 2. **KISS**: Keep It Simple, Stupid
 3. **Minimal Dependencies**: Only what's necessary
 4. **Concrete Over Abstract**: Start simple, refactor when needed
 
 ### Compliance Criteria
+
 ```
 ✅ COMPLIANT:
 - Minimal external dependencies
@@ -309,12 +333,13 @@ def check_steering_compliance():
 ```
 
 ### Enforcement
+
 ```python
 def simplicity_check(proposal):
     # Check dependency count
     if len(proposal.dependencies) > THRESHOLD:
         WARNING("Article VII: High dependency count")
-    
+
     # Check for design pattern overuse
     patterns = detect_patterns(proposal)
     if "factory" in patterns and "simple instantiation" in alternatives:
@@ -328,12 +353,14 @@ def simplicity_check(proposal):
 > **No abstraction before the third occurrence.**
 
 ### Rationale
+
 - Prevents premature generalization
 - Abstractions emerge from patterns
 - Concrete code is easier to change
 - Wrong abstractions are costly
 
 ### Rule of Three
+
 ```
 1st occurrence: Implement concrete solution
 2nd occurrence: Copy and adapt (acceptable duplication)
@@ -341,6 +368,7 @@ def simplicity_check(proposal):
 ```
 
 ### Compliance Criteria
+
 ```
 ✅ COMPLIANT:
 - Concrete implementation first
@@ -355,6 +383,7 @@ def simplicity_check(proposal):
 ```
 
 ### Enforcement
+
 ```python
 def anti_abstraction_check():
     for interface in find_interfaces():
@@ -370,12 +399,14 @@ def anti_abstraction_check():
 > **Integration tests before unit tests for new features.**
 
 ### Rationale
+
 - Validates end-to-end behavior first
 - Catches integration issues early
 - Unit tests fill gaps afterward
 - User-centric testing approach
 
 ### Testing Order
+
 ```
 1. Integration tests (happy path)
 2. Integration tests (error paths)
@@ -384,6 +415,7 @@ def anti_abstraction_check():
 ```
 
 ### Compliance Criteria
+
 ```
 ✅ COMPLIANT:
 - Integration tests written first
@@ -397,18 +429,19 @@ def anti_abstraction_check():
 ```
 
 ### Enforcement
+
 ```python
 def integration_first_check(feature):
     integration_tests = find_tests(feature, type="integration")
     unit_tests = find_tests(feature, type="unit")
-    
+
     if not integration_tests:
         VIOLATION("Article IX: No integration tests found")
-    
+
     # Check commit order
     integration_date = get_first_commit(integration_tests)
     unit_date = get_first_commit(unit_tests)
-    
+
     if unit_date < integration_date:
         WARNING("Article IX: Unit tests committed before integration")
 ```
@@ -419,31 +452,34 @@ def integration_first_check(feature):
 
 ### Quick Reference
 
-| Article | Title | Key Rule |
-|---------|-------|----------|
-| I | Library-First | Features start as libraries |
-| II | CLI Mandate | Libraries expose CLI |
-| III | Test-First | Tests before code |
-| IV | EARS Format | Unambiguous requirements |
-| V | Traceability | 100% coverage |
-| VI | Project Memory | Check steering first |
-| VII | Simplicity | Simplest solution |
-| VIII | Anti-Abstraction | Rule of three |
-| IX | Integration-First | Integration before unit |
+| Article | Title             | Key Rule                    |
+| ------- | ----------------- | --------------------------- |
+| I       | Library-First     | Features start as libraries |
+| II      | CLI Mandate       | Libraries expose CLI        |
+| III     | Test-First        | Tests before code           |
+| IV      | EARS Format       | Unambiguous requirements    |
+| V       | Traceability      | 100% coverage               |
+| VI      | Project Memory    | Check steering first        |
+| VII     | Simplicity        | Simplest solution           |
+| VIII    | Anti-Abstraction  | Rule of three               |
+| IX      | Integration-First | Integration before unit     |
 
 ### Enforcement Priority
 
 **Blocking (Must Pass)**:
+
 - Article III: Test-First (no exceptions)
 - Article IV: EARS Format (no exceptions)
 - Article V: Traceability (no exceptions)
 
 **Required (Strong Enforcement)**:
+
 - Article I: Library-First
 - Article II: CLI Mandate
 - Article VI: Project Memory
 
 **Advisory (With Justification)**:
+
 - Article VII: Simplicity Gate
 - Article VIII: Anti-Abstraction Gate
 - Article IX: Integration-First

package/src/templates/agents/claude-code/skills/constitution-enforcer/phase-minus-one-gates.md

@@ -39,6 +39,7 @@ Implementation Begins
 **Purpose**: Ensure project memory is consulted before work begins.
 
 **Validation**:
+
 ```bash
 # Check if steering files exist
 required_files=(
@@ -58,6 +59,7 @@ PASS "Steering files exist and will be consulted"
 ```
 
 **Pass Criteria**:
+
 - [ ] `steering/structure.md` exists
 - [ ] `steering/tech.md` exists
 - [ ] `steering/product.md` exists
@@ -73,6 +75,7 @@ PASS "Steering files exist and will be consulted"
 **Purpose**: Ensure requirements use EARS format.
 
 **Validation**:
+
 ```python
 def validate_ears_format(requirements_file):
     """
@@ -85,20 +88,21 @@ def validate_ears_format(requirements_file):
         r"IF .+ THEN .+ (SHALL|MUST)",     # Conditional
         r"The system (SHALL|MUST)",        # Ubiquitous
     ]
-    
+
     invalid_keywords = ["should", "may", "could", "might"]
-    
+
     for line in requirements_file:
         if any(kw in line.lower() for kw in invalid_keywords):
             FAIL(f"Ambiguous keyword found: {line}")
-        
+
         if "REQ-" in line and not any(re.match(p, line) for p in valid_patterns):
             WARN(f"Requirement may not follow EARS: {line}")
-    
+
     PASS("All requirements follow EARS format")
 ```
 
 **Pass Criteria**:
+
 - [ ] All requirements use SHALL/MUST (not should/may)
 - [ ] Requirements follow EARS patterns
 - [ ] Each requirement has unique ID (REQ-XXX)
@@ -113,6 +117,7 @@ def validate_ears_format(requirements_file):
 **Purpose**: Ensure features are implemented as standalone libraries first.
 
 **Validation**:
+
 ```bash
 # For new features, check target directory
 feature_path="$1"
@@ -120,7 +125,7 @@ feature_path="$1"
 if [[ "$feature_path" == *"/app/"* ]] || [[ "$feature_path" == *"/web/"* ]]; then
     # Check if corresponding lib exists
     lib_path=$(echo "$feature_path" | sed 's/app\//lib\//; s/web\//lib\//')
-    
+
     if [ ! -d "$lib_path" ]; then
         FAIL "Feature must be in lib/ first before app/ or web/"
     fi
@@ -130,6 +135,7 @@ PASS "Library-First principle satisfied"
 ```
 
 **Pass Criteria**:
+
 - [ ] New feature targets `lib/` directory first
 - [ ] OR: Existing `lib/` module exists for the feature
 - [ ] Library has no framework dependencies
@@ -144,6 +150,7 @@ PASS "Library-First principle satisfied"
 **Purpose**: Confirm tests will be written before implementation.
 
 **Validation**:
+
 ```bash
 # This is a confirmation gate - agent must commit to test-first
 echo "TEST-FIRST CONFIRMATION REQUIRED"
@@ -163,6 +170,7 @@ PASS "Test-First commitment confirmed"
 ```
 
 **Pass Criteria**:
+
 - [ ] Agent confirms test-first commitment
 - [ ] Test file paths identified
 - [ ] Test framework confirmed in steering/tech.md
@@ -177,6 +185,7 @@ PASS "Test-First commitment confirmed"
 **Purpose**: Ensure traceability chain is established.
 
 **Validation**:
+
 ```python
 def validate_traceability_setup(feature_name):
     """
@@ -187,18 +196,19 @@ def validate_traceability_setup(feature_name):
         "design": f"storage/features/{feature_name}/design.md",
         "tasks": f"storage/features/{feature_name}/tasks.md",
     }
-    
+
     for artifact, path in required_artifacts.items():
         if artifact == "requirements":
             # Requirements MUST exist before design
             if not os.path.exists(path):
                 FAIL(f"Requirements must exist before implementation: {path}")
-    
+
     # Confirm traceability matrix will be maintained
     PASS("Traceability setup confirmed")
 ```
 
 **Pass Criteria**:
+
 - [ ] Requirements file exists or will be created first
 - [ ] Design will reference requirements
 - [ ] Tasks will reference design
@@ -215,6 +225,7 @@ def validate_traceability_setup(feature_name):
 **Purpose**: Enforce simplest viable solution.
 
 **Validation**:
+
 ```markdown
 ## Simplicity Checklist
 
@@ -242,6 +253,7 @@ For the proposed solution, verify:
 ```
 
 **Pass Criteria**:
+
 - [ ] Solution is the simplest that satisfies requirements
 - [ ] No unnecessary complexity identified
 - [ ] Dependencies are minimal and justified
@@ -256,6 +268,7 @@ For the proposed solution, verify:
 **Purpose**: Prevent unnecessary abstraction layers.
 
 **Validation**:
+
 ```markdown
 ## Anti-Abstraction Checklist
 
@@ -279,6 +292,7 @@ For the proposed solution, verify:
 ```
 
 **Pass Criteria**:
+
 - [ ] No premature abstraction patterns
 - [ ] Concrete implementations prioritized
 - [ ] Any abstraction is justified by requirements
@@ -331,21 +345,22 @@ ALL GATES PASSED → Proceed to implementation
 
 ## Gate Results
 
-| Gate | Status | Notes |
-|------|--------|-------|
-| 1. Steering Check | ✅ PASS | All files exist |
-| 2. EARS Validation | ✅ PASS | 5/5 requirements valid |
-| 3. Library-First | ✅ PASS | Target: lib/auth/ |
-| 4. Test-First | ✅ PASS | Commitment confirmed |
-| 5. Traceability | ✅ PASS | Requirements exist |
-| 6. Simplicity | ✅ PASS | Minimal approach |
-| 7. Anti-Abstraction | ✅ PASS | No premature patterns |
+| Gate                | Status  | Notes                  |
+| ------------------- | ------- | ---------------------- |
+| 1. Steering Check   | ✅ PASS | All files exist        |
+| 2. EARS Validation  | ✅ PASS | 5/5 requirements valid |
+| 3. Library-First    | ✅ PASS | Target: lib/auth/      |
+| 4. Test-First       | ✅ PASS | Commitment confirmed   |
+| 5. Traceability     | ✅ PASS | Requirements exist     |
+| 6. Simplicity       | ✅ PASS | Minimal approach       |
+| 7. Anti-Abstraction | ✅ PASS | No premature patterns  |
 
 ## Overall Result: ✅ PASS
 
 Implementation may proceed.
 
 ## Next Steps
+
 1. Write tests (test-engineer)
 2. Implement code (software-developer)
 3. Review (code-reviewer)
@@ -356,20 +371,24 @@ Implementation may proceed.
 ## Gate Failure Escalation
 
 ### Automatic Remediation
+
 - Gate 1: Auto-run steering skill
 - Gate 2: Auto-run requirements-analyst
 - Gate 5: Auto-create requirements template
 
 ### Manual Intervention Required
+
 - Gate 3: Requires architectural decision
 - Gate 4: Requires developer commitment
 - Gate 6: Requires design simplification
 - Gate 7: Requires refactoring proposal
 
 ### Blocking Gates
+
 - Gate 4 (Test-First): MUST pass - no exceptions
 - Gate 2 (EARS): MUST pass - no exceptions
 
 ### Waivable Gates (with justification)
+
 - Gate 6 (Simplicity): Waivable with documented reason
 - Gate 7 (Anti-Abstraction): Waivable with documented reason

package/src/templates/agents/claude-code/skills/database-administrator/backup-recovery.md

@@ -9,6 +9,7 @@ Best practices for database backup and recovery strategies.
 ## Backup Types
 
 ### Full Backup
+
 Complete copy of entire database.
 
 ```bash
@@ -20,6 +21,7 @@ mysqldump --all-databases > backup_full_$(date +%Y%m%d).sql
 ```
 
 ### Incremental Backup
+
 Only changes since last backup.
 
 ```bash
@@ -31,6 +33,7 @@ mysqlbinlog --start-datetime="2024-01-01 00:00:00" binlog.000001 > incremental.s
 ```
 
 ### Differential Backup
+
 All changes since last full backup.
 
 ---
@@ -45,11 +48,11 @@ All changes since last full backup.
 
 ### Retention Policy
 
-| Backup Type | Frequency | Retention |
-|-------------|-----------|-----------|
-| Full | Weekly | 4 weeks |
-| Differential | Daily | 1 week |
-| WAL/Binlog | Continuous | 2 weeks |
+| Backup Type  | Frequency  | Retention |
+| ------------ | ---------- | --------- |
+| Full         | Weekly     | 4 weeks   |
+| Differential | Daily      | 1 week    |
+| WAL/Binlog   | Continuous | 2 weeks   |
 
 ---
 
@@ -210,21 +213,25 @@ chown -R mysql:mysql /var/lib/mysql
 # Recovery Test Checklist
 
 ## Preparation
+
 - [ ] Identify test environment
 - [ ] Get latest backup
 - [ ] Document start time
 
 ## Restore
+
 - [ ] Restore database
 - [ ] Apply incremental backups
 - [ ] Verify data integrity
 
 ## Validation
+
 - [ ] Count records in key tables
 - [ ] Run application tests
 - [ ] Verify recent transactions
 
 ## Documentation
+
 - [ ] Record recovery time
 - [ ] Note any issues
 - [ ] Update runbook
@@ -232,10 +239,10 @@ chown -R mysql:mysql /var/lib/mysql
 
 ### RTO/RPO Calculation
 
-| Metric | Definition | Target |
-|--------|------------|--------|
-| RTO | Recovery Time Objective | < 1 hour |
-| RPO | Recovery Point Objective | < 15 min |
+| Metric | Definition               | Target   |
+| ------ | ------------------------ | -------- |
+| RTO    | Recovery Time Objective  | < 1 hour |
+| RPO    | Recovery Point Objective | < 15 min |
 
 ---
 
@@ -281,15 +288,15 @@ chown -R mysql:mysql /var/lib/mysql
 metrics:
   - name: backup_last_success_timestamp
     type: gauge
-    help: "Timestamp of last successful backup"
-    
+    help: 'Timestamp of last successful backup'
+
   - name: backup_duration_seconds
     type: histogram
-    help: "Backup duration in seconds"
-    
+    help: 'Backup duration in seconds'
+
   - name: backup_size_bytes
     type: gauge
-    help: "Size of latest backup"
+    help: 'Size of latest backup'
 ```
 
 ### Alerts
@@ -301,14 +308,14 @@ alerts:
     for: 1h
     severity: critical
     annotations:
-      summary: "No successful backup in 24 hours"
-      
+      summary: 'No successful backup in 24 hours'
+
   - alert: BackupTooSmall
     expr: backup_size_bytes < backup_size_bytes offset 1d * 0.5
     for: 5m
     severity: warning
     annotations:
-      summary: "Backup size decreased significantly"
+      summary: 'Backup size decreased significantly'
 ```
 
 ---
@@ -316,16 +323,19 @@ alerts:
 ## Checklist
 
 ### Daily
+
 - [ ] Verify backup completed
 - [ ] Check backup size
 - [ ] Review backup logs
 
 ### Weekly
+
 - [ ] Test restore to dev
 - [ ] Verify offsite replication
 - [ ] Check retention policy
 
 ### Monthly
+
 - [ ] Full recovery drill
 - [ ] Update RTO/RPO metrics
 - [ ] Review backup strategy