musubi-sdd 5.1.0 → 5.6.1

package/src/templates/agents/claude-code/skills/project-manager/project-templates.md

@@ -12,21 +12,24 @@ Templates for project planning, tracking, and reporting.
 # Project Charter: [Project Name]
 
 ## Overview
-| Field | Value |
-|-------|-------|
-| Project Name | [Name] |
-| Project Manager | [Name] |
-| Sponsor | [Name] |
-| Start Date | YYYY-MM-DD |
-| Target End Date | YYYY-MM-DD |
-| Status | Planning / Active / Complete |
+
+| Field           | Value                        |
+| --------------- | ---------------------------- |
+| Project Name    | [Name]                       |
+| Project Manager | [Name]                       |
+| Sponsor         | [Name]                       |
+| Start Date      | YYYY-MM-DD                   |
+| Target End Date | YYYY-MM-DD                   |
+| Status          | Planning / Active / Complete |
 
 ---
 
 ## 1. Project Purpose
+
 [Why are we doing this project?]
 
 ## 2. Objectives
+
 - [Objective 1]
 - [Objective 2]
 - [Objective 3]
@@ -34,46 +37,54 @@ Templates for project planning, tracking, and reporting.
 ## 3. Scope
 
 ### In Scope
+
 - [Item 1]
 - [Item 2]
 
 ### Out of Scope
+
 - [Item 1]
 - [Item 2]
 
 ## 4. Deliverables
-| Deliverable | Description | Due Date |
-|-------------|-------------|----------|
-| [D1] | [Description] | [Date] |
-| [D2] | [Description] | [Date] |
+
+| Deliverable | Description   | Due Date |
+| ----------- | ------------- | -------- |
+| [D1]        | [Description] | [Date]   |
+| [D2]        | [Description] | [Date]   |
 
 ## 5. Success Criteria
+
 - [Criterion 1]
 - [Criterion 2]
 
 ## 6. Stakeholders
-| Name | Role | Involvement |
-|------|------|-------------|
-| [Name] | Sponsor | Approver |
+
+| Name   | Role           | Involvement |
+| ------ | -------------- | ----------- |
+| [Name] | Sponsor        | Approver    |
 | [Name] | Lead Developer | Contributor |
 
 ## 7. Risks
-| Risk | Probability | Impact | Mitigation |
-|------|-------------|--------|------------|
-| [Risk 1] | High | High | [Mitigation] |
+
+| Risk     | Probability | Impact | Mitigation   |
+| -------- | ----------- | ------ | ------------ |
+| [Risk 1] | High        | High   | [Mitigation] |
 
 ## 8. Budget
-| Category | Amount |
-|----------|--------|
-| Development | $X |
-| Infrastructure | $Y |
-| Total | $Z |
+
+| Category       | Amount |
+| -------------- | ------ |
+| Development    | $X     |
+| Infrastructure | $Y     |
+| Total          | $Z     |
 
 ## 9. Approvals
-| Name | Role | Date | Signature |
-|------|------|------|-----------|
-| [Name] | Sponsor | | |
-| [Name] | PM | | |
+
+| Name   | Role    | Date | Signature |
+| ------ | ------- | ---- | --------- |
+| [Name] | Sponsor |      |           |
+| [Name] | PM      |      |           |
 ```
 
 ---
@@ -90,37 +101,37 @@ Templates for project planning, tracking, and reporting.
 
 ## Capacity
 
-| Team Member | Capacity (days) | Notes |
-|-------------|-----------------|-------|
-| [Name] | 8 | PTO Friday |
-| [Name] | 10 | Full capacity |
-| **Total** | **18** | |
+| Team Member | Capacity (days) | Notes         |
+| ----------- | --------------- | ------------- |
+| [Name]      | 8               | PTO Friday    |
+| [Name]      | 10              | Full capacity |
+| **Total**   | **18**          |               |
 
 ---
 
 ## Sprint Backlog
 
-| ID | Story | Points | Assignee | Status |
-|----|-------|--------|----------|--------|
-| US-001 | [User story] | 5 | [Name] | To Do |
-| US-002 | [User story] | 3 | [Name] | To Do |
-| **Total** | | **8** | | |
+| ID        | Story        | Points | Assignee | Status |
+| --------- | ------------ | ------ | -------- | ------ |
+| US-001    | [User story] | 5      | [Name]   | To Do  |
+| US-002    | [User story] | 3      | [Name]   | To Do  |
+| **Total** |              | **8**  |          |        |
 
 ---
 
 ## Technical Tasks
 
-| Task | Story | Estimate | Assignee |
-|------|-------|----------|----------|
-| [Task 1] | US-001 | 4h | [Name] |
-| [Task 2] | US-001 | 2h | [Name] |
+| Task     | Story  | Estimate | Assignee |
+| -------- | ------ | -------- | -------- |
+| [Task 1] | US-001 | 4h       | [Name]   |
+| [Task 2] | US-001 | 2h       | [Name]   |
 
 ---
 
 ## Dependencies
 
-| Dependency | From | Status |
-|------------|------|--------|
+| Dependency   | From          | Status  |
+| ------------ | ------------- | ------- |
 | [Dependency] | [Team/System] | Pending |
 
 ---
@@ -173,24 +184,26 @@ Templates for project planning, tracking, and reporting.
 
 ## Metrics
 
-| Metric | Target | Actual | Status |
-|--------|--------|--------|--------|
-| Sprint velocity | 30 pts | 28 pts | 🟢 |
-| Bug count | < 5 | 3 | 🟢 |
-| Test coverage | > 80% | 75% | 🟡 |
+| Metric          | Target | Actual | Status |
+| --------------- | ------ | ------ | ------ |
+| Sprint velocity | 30 pts | 28 pts | 🟢     |
+| Bug count       | < 5    | 3      | 🟢     |
+| Test coverage   | > 80%  | 75%    | 🟡     |
 
 ---
 
 ## Risks and Issues
 
 ### Risks
-| Risk | Probability | Impact | Mitigation | Owner |
-|------|-------------|--------|------------|-------|
-| [Risk] | Medium | High | [Mitigation] | [Name] |
+
+| Risk   | Probability | Impact | Mitigation   | Owner  |
+| ------ | ----------- | ------ | ------------ | ------ |
+| [Risk] | Medium      | High   | [Mitigation] | [Name] |
 
 ### Issues
-| Issue | Impact | Action | Owner | Due |
-|-------|--------|--------|-------|-----|
+
+| Issue   | Impact   | Action   | Owner  | Due    |
+| ------- | -------- | -------- | ------ | ------ |
 | [Issue] | [Impact] | [Action] | [Name] | [Date] |
 
 ---
@@ -232,11 +245,13 @@ Templates for project planning, tracking, and reporting.
 ## Discussion Notes
 
 ### Topic 1: [Name]
+
 - [Key point]
 - [Key point]
 - **Decision**: [Decision made]
 
 ### Topic 2: [Name]
+
 - [Key point]
 - **Decision**: [Decision made]
 
@@ -244,10 +259,10 @@ Templates for project planning, tracking, and reporting.
 
 ## Action Items
 
-| Action | Owner | Due Date |
-|--------|-------|----------|
-| [Action 1] | [Name] | [Date] |
-| [Action 2] | [Name] | [Date] |
+| Action     | Owner  | Due Date |
+| ---------- | ------ | -------- |
+| [Action 1] | [Name] | [Date]   |
+| [Action 2] | [Name] | [Date]   |
 
 ---
 
@@ -295,30 +310,30 @@ Templates for project planning, tracking, and reporting.
 
 ## Action Items
 
-| Action | Owner | Status |
-|--------|-------|--------|
-| [Action 1] | [Name] | Open |
-| [Action 2] | [Name] | Open |
+| Action     | Owner  | Status |
+| ---------- | ------ | ------ |
+| [Action 1] | [Name] | Open   |
+| [Action 2] | [Name] | Open   |
 
 ---
 
 ## Previous Action Items
 
-| Action | Owner | Status |
-|--------|-------|--------|
-| [Previous action] | [Name] | ✅ Done |
+| Action            | Owner  | Status         |
+| ----------------- | ------ | -------------- |
+| [Previous action] | [Name] | ✅ Done        |
 | [Previous action] | [Name] | 🔄 In Progress |
 
 ---
 
 ## Team Health
 
-| Category | Score (1-5) |
-|----------|-------------|
-| Collaboration | ⭐⭐⭐⭐ |
-| Velocity | ⭐⭐⭐ |
-| Quality | ⭐⭐⭐⭐ |
-| Morale | ⭐⭐⭐⭐ |
+| Category      | Score (1-5) |
+| ------------- | ----------- |
+| Collaboration | ⭐⭐⭐⭐    |
+| Velocity      | ⭐⭐⭐      |
+| Quality       | ⭐⭐⭐⭐    |
+| Morale        | ⭐⭐⭐⭐    |
 ```
 
 ---
@@ -328,16 +343,17 @@ Templates for project planning, tracking, and reporting.
 ```markdown
 # RACI Matrix
 
-| Task | PM | Dev Lead | Developer | QA | Stakeholder |
-|------|:--:|:--------:|:---------:|:--:|:-----------:|
-| Requirements | A | C | I | C | R |
-| Architecture | C | R | C | I | I |
-| Development | I | A | R | C | I |
-| Testing | I | C | C | R | I |
-| Deployment | A | R | C | C | I |
-| Sign-off | A | I | I | I | R |
+| Task         | PM  | Dev Lead | Developer | QA  | Stakeholder |
+| ------------ | :-: | :------: | :-------: | :-: | :---------: |
+| Requirements |  A  |    C     |     I     |  C  |      R      |
+| Architecture |  C  |    R     |     C     |  I  |      I      |
+| Development  |  I  |    A     |     R     |  C  |      I      |
+| Testing      |  I  |    C     |     C     |  R  |      I      |
+| Deployment   |  A  |    R     |     C     |  C  |      I      |
+| Sign-off     |  A  |    I     |     I     |  I  |      R      |
 
 **Legend**:
+
 - **R** = Responsible (does the work)
 - **A** = Accountable (final decision)
 - **C** = Consulted (provides input)

package/src/templates/agents/claude-code/skills/quality-assurance/SKILL.md

@@ -43,17 +43,17 @@ const critic = new CriticSystem();
 // Evaluate requirements quality
 const reqResult = await critic.evaluate('requirements', {
   projectRoot: process.cwd(),
-  content: reqDocument
+  content: reqDocument,
 });
 
-console.log(reqResult.score);      // 0.85
-console.log(reqResult.grade);      // 'B'
-console.log(reqResult.success);    // true (score >= 0.5)
-console.log(reqResult.feedback);   // Improvement suggestions
+console.log(reqResult.score); // 0.85
+console.log(reqResult.grade); // 'B'
+console.log(reqResult.success); // true (score >= 0.5)
+console.log(reqResult.feedback); // Improvement suggestions
 
 // Evaluate all stages
 const allResults = await critic.evaluateAll({
-  projectRoot: process.cwd()
+  projectRoot: process.cwd(),
 });
 
 // Generate markdown report
@@ -62,11 +62,11 @@ const report = critic.generateReport(allResults);
 
 ### Quality Gate Criteria
 
-| Stage | Minimum Score | Key Checks |
-|-------|--------------|------------|
-| Requirements | 0.5 | EARS format, completeness, testability |
-| Design | 0.5 | C4 diagrams, ADR presence |
-| Implementation | 0.5 | Test coverage, code quality, docs |
+| Stage          | Minimum Score | Key Checks                             |
+| -------------- | ------------- | -------------------------------------- |
+| Requirements   | 0.5           | EARS format, completeness, testability |
+| Design         | 0.5           | C4 diagrams, ADR presence              |
+| Implementation | 0.5           | Test coverage, code quality, docs      |
 
 ### MemoryCondenser (`src/managers/memory-condenser.js`)
 
@@ -77,15 +77,18 @@ const { MemoryCondenser, MemoryEvent } = require('musubi/src/managers/memory-con
 
 const condenser = MemoryCondenser.create('recent', {
   maxEvents: 100,
-  keepRecent: 30
+  keepRecent: 30,
 });
 
 // Condense long QA session history
-const events = qaSessionEvents.map(e => new MemoryEvent({
-  type: e.type,
-  content: e.content,
-  important: e.type === 'defect_found'
-}));
+const events = qaSessionEvents.map(
+  e =>
+    new MemoryEvent({
+      type: e.type,
+      content: e.content,
+      important: e.type === 'defect_found',
+    })
+);
 
 const condensed = await condenser.condense(events);
 ```

package/src/templates/agents/claude-code/skills/quality-assurance/qa-plan-template.md

@@ -13,26 +13,29 @@ Template for creating comprehensive Quality Assurance plans.
 
 ## Document Information
 
-| Field | Value |
-|-------|-------|
-| Version | 1.0 |
-| Date | YYYY-MM-DD |
-| Author | quality-assurance |
-| Status | Draft / Approved |
-| Reviewers | [Names] |
+| Field     | Value             |
+| --------- | ----------------- |
+| Version   | 1.0               |
+| Date      | YYYY-MM-DD        |
+| Author    | quality-assurance |
+| Status    | Draft / Approved  |
+| Reviewers | [Names]           |
 
 ---
 
 ## 1. Introduction
 
 ### 1.1 Purpose
+
 [Describe the purpose of this QA plan]
 
 ### 1.2 Scope
+
 - **In Scope**: [What will be tested]
 - **Out of Scope**: [What won't be tested]
 
 ### 1.3 References
+
 - Requirements: [Link to requirements]
 - Design: [Link to design docs]
 - Related ADRs: [Links]
@@ -43,13 +46,13 @@ Template for creating comprehensive Quality Assurance plans.
 
 ### 2.1 Test Levels
 
-| Level | Description | Tools |
-|-------|-------------|-------|
-| Unit | Individual functions/methods | Jest/pytest |
-| Integration | Component interactions | Supertest |
-| E2E | Full user journeys | Playwright |
-| Performance | Load/stress testing | k6 |
-| Security | Vulnerability testing | OWASP ZAP |
+| Level       | Description                  | Tools       |
+| ----------- | ---------------------------- | ----------- |
+| Unit        | Individual functions/methods | Jest/pytest |
+| Integration | Component interactions       | Supertest   |
+| E2E         | Full user journeys           | Playwright  |
+| Performance | Load/stress testing          | k6          |
+| Security    | Vulnerability testing        | OWASP ZAP   |
 
 ### 2.2 Test Types
 
@@ -64,10 +67,12 @@ Template for creating comprehensive Quality Assurance plans.
 ### 2.3 Test Approach
 
 **Test-First (Mandatory - Article III)**:
+
 - All tests written before implementation
 - Red-Green-Refactor cycle followed
 
 **Integration-First (Article IX)**:
+
 - Integration tests before unit tests
 - E2E tests for critical paths
 
@@ -77,11 +82,11 @@ Template for creating comprehensive Quality Assurance plans.
 
 ### 3.1 Environments
 
-| Environment | Purpose | URL |
-|-------------|---------|-----|
-| Development | Developer testing | localhost |
-| Staging | Integration testing | staging.example.com |
-| Production | Live system | example.com |
+| Environment | Purpose             | URL                 |
+| ----------- | ------------------- | ------------------- |
+| Development | Developer testing   | localhost           |
+| Staging     | Integration testing | staging.example.com |
+| Production  | Live system         | example.com         |
 
 ### 3.2 Test Data
 
@@ -95,15 +100,16 @@ Template for creating comprehensive Quality Assurance plans.
 
 ### 4.1 Coverage Targets
 
-| Metric | Target | Current |
-|--------|--------|---------|
-| Line Coverage | 80% | - |
-| Branch Coverage | 75% | - |
-| Requirements Coverage | 100% | - |
+| Metric                | Target | Current |
+| --------------------- | ------ | ------- |
+| Line Coverage         | 80%    | -       |
+| Branch Coverage       | 75%    | -       |
+| Requirements Coverage | 100%   | -       |
 
 ### 4.2 Critical Paths
 
 Must have 100% test coverage:
+
 1. Authentication flow
 2. Payment processing
 3. User data operations
@@ -113,12 +119,14 @@ Must have 100% test coverage:
 ## 5. Entry/Exit Criteria
 
 ### 5.1 Entry Criteria
+
 - [ ] Requirements approved
 - [ ] Design complete
 - [ ] Test environment ready
 - [ ] Test data available
 
 ### 5.2 Exit Criteria
+
 - [ ] All critical tests pass
 - [ ] Coverage targets met
 - [ ] No P1/P2 bugs open
@@ -129,24 +137,24 @@ Must have 100% test coverage:
 
 ## 6. Risk Assessment
 
-| Risk | Probability | Impact | Mitigation |
-|------|-------------|--------|------------|
-| Tight timeline | High | High | Early testing, automation |
-| Environment issues | Medium | High | Backup environments |
-| Data quality | Medium | Medium | Data validation |
+| Risk               | Probability | Impact | Mitigation                |
+| ------------------ | ----------- | ------ | ------------------------- |
+| Tight timeline     | High        | High   | Early testing, automation |
+| Environment issues | Medium      | High   | Backup environments       |
+| Data quality       | Medium      | Medium | Data validation           |
 
 ---
 
 ## 7. Schedule
 
-| Phase | Start | End | Owner |
-|-------|-------|-----|-------|
-| Test Planning | MM/DD | MM/DD | QA Lead |
-| Test Development | MM/DD | MM/DD | QA Team |
-| Test Execution | MM/DD | MM/DD | QA Team |
-| Bug Fixes | MM/DD | MM/DD | Dev Team |
-| Regression | MM/DD | MM/DD | QA Team |
-| Sign-off | MM/DD | MM/DD | QA Lead |
+| Phase            | Start | End   | Owner    |
+| ---------------- | ----- | ----- | -------- |
+| Test Planning    | MM/DD | MM/DD | QA Lead  |
+| Test Development | MM/DD | MM/DD | QA Team  |
+| Test Execution   | MM/DD | MM/DD | QA Team  |
+| Bug Fixes        | MM/DD | MM/DD | Dev Team |
+| Regression       | MM/DD | MM/DD | QA Team  |
+| Sign-off         | MM/DD | MM/DD | QA Lead  |
 
 ---
 
@@ -163,36 +171,39 @@ Must have 100% test coverage:
 
 ## 9. Roles & Responsibilities
 
-| Role | Responsibility | Person |
-|------|----------------|--------|
-| QA Lead | Plan, coordinate | [Name] |
-| QA Engineer | Execute tests | [Name] |
-| Developer | Fix bugs, unit tests | [Name] |
-| PM | Review, approve | [Name] |
+| Role        | Responsibility       | Person |
+| ----------- | -------------------- | ------ |
+| QA Lead     | Plan, coordinate     | [Name] |
+| QA Engineer | Execute tests        | [Name] |
+| Developer   | Fix bugs, unit tests | [Name] |
+| PM          | Review, approve      | [Name] |
 
 ---
 
 ## 10. Tools
 
-| Purpose | Tool |
-|---------|------|
+| Purpose         | Tool        |
+| --------------- | ----------- |
 | Test Management | [Tool name] |
-| Bug Tracking | [Tool name] |
-| Automation | [Tool name] |
-| CI/CD | [Tool name] |
-| Coverage | [Tool name] |
+| Bug Tracking    | [Tool name] |
+| Automation      | [Tool name] |
+| CI/CD           | [Tool name] |
+| Coverage        | [Tool name] |
 
 ---
 
 ## Appendix
 
 ### A. Test Case Template
+
 [Link to template]
 
 ### B. Bug Report Template
+
 [Link to template]
 
 ### C. Glossary
+
 [Terms and definitions]
 ```
 
@@ -201,16 +212,19 @@ Must have 100% test coverage:
 ## Quick QA Checklist
 
 ### Before Development
+
 - [ ] Requirements are testable (EARS format)
 - [ ] Acceptance criteria defined
 - [ ] Test environment ready
 
 ### During Development
+
 - [ ] Tests written first
 - [ ] CI/CD running tests
 - [ ] Code review includes test review
 
 ### Before Release
+
 - [ ] All tests passing
 - [ ] Coverage targets met
 - [ ] No critical bugs open

package/src/templates/agents/claude-code/skills/release-coordinator/SKILL.md

@@ -56,11 +56,11 @@ musubi-workflow next monitoring
 
 ### リリースタイプ別フロー
 
-| リリースタイプ | ワークフローアクション |
-|---------------|----------------------|
-| Hotfix | `musubi-workflow init hotfix-xxx` → 高速パス |
-| Patch | 通常フロー（Stage 6→7→8） |
-| Minor/Major | 完全フロー（Stage 0→9） |
+| リリースタイプ | ワークフローアクション                       |
+| -------------- | -------------------------------------------- |
+| Hotfix         | `musubi-workflow init hotfix-xxx` → 高速パス |
+| Patch          | 通常フロー（Stage 6→7→8）                    |
+| Minor/Major    | 完全フロー（Stage 0→9）                      |
 
 ### デプロイ完了チェックリスト