majiayu000 MUSUBIX SDD Workflow Skill
This skill guides you through the complete SDD workflow for MUSUBIX projects.
Prerequisites
Before starting any development task:
- Read
steering/directory for project context - Check
steering/rules/constitution.mdfor the 9 constitutional articles - Review existing specs in
storage/specs/
Complete Workflow
Phase 1: Requirements Definition
Step 1: Create Requirements Document (Article IV - EARS Format)
Create requirements using EARS patterns:
# REQ-[CATEGORY]-[NUMBER]
**種別**: [UBIQUITOUS|EVENT-DRIVEN|STATE-DRIVEN|UNWANTED|OPTIONAL]
**優先度**: [P0|P1|P2]
**要件**:
[EARS形式の要件文]
**トレーサビリティ**: DES-XXX, TEST-XXX
EARS Patterns:
- Ubiquitous:
THE [system] SHALL [requirement] - Event-driven:
WHEN [event], THE [system] SHALL [response] - State-driven:
WHILE [state], THE [system] SHALL [response] - Unwanted:
THE [system] SHALL NOT [behavior] - Optional:
IF [condition], THEN THE [system] SHALL [response]
Step 2-3: Requirements Review Loop
Review requirements for:
- EARS format compliance
- Completeness and clarity
- Testability
- Traceability readiness
Repeat until no issues remain.
Phase 2: Design
Step 4: Create Design Document (Article VII - Design Patterns)
Create C4 model design documents:
- Context Level: System boundaries and external actors
- Container Level: Technology choices and container composition
- Component Level: Internal structure of containers
- Code Level: Implementation details
Design document template:
# DES-[CATEGORY]-[NUMBER]
## トレーサビリティ
- 要件: REQ-XXX
## C4モデル
### Level 2: Container
[PlantUML diagram]
## コンポーネント設計
[Component details]
Step 5-6: Design Review Loop
Review design for:
- Requirement coverage
- SOLID principles compliance
- Design pattern appropriateness
- Traceability to requirements
Repeat until no issues remain.
Phase 3: Task Decomposition
Step 7: Generate Tasks
Generate implementation tasks from design:
# TSK-[CATEGORY]-[NUMBER]
## 関連設計: DES-XXX
## 関連要件: REQ-XXX
## タスク内容
[Implementation task description]
## 受入基準
- [ ] Criterion 1
- [ ] Criterion 2
## 見積もり
[4時間以内を推奨]
Step 8-9: Task Review Loop
Review tasks for:
- Appropriate granularity (≤4 hours)
- Clear acceptance criteria
- Complete traceability chain
Repeat until no issues remain.
Phase 4: Implementation
Step 10: Coding & Unit Testing (Article III - Test-First)
For each task, follow Red-Green-Blue cycle:
- Red: Write failing test first
- Green: Write minimal code to pass
- Blue: Refactor while keeping tests green
Add requirement IDs in code comments:
/**
* @see REQ-INT-001 - Neuro-Symbolic Integration
*/
Step 11: Integration Testing
When required by the task:
- Run integration tests
- Verify component interactions
- Ensure end-to-end flows work correctly
Phase 5: Documentation & Completion
Step 12: Update CHANGELOG.md
Document all changes:
- New features
- Bug fixes
- Breaking changes
- Migration notes
Step 13: Update Other Documentation
If necessary, update:
- README.md
- USER-GUIDE.md
- API-REFERENCE.md
- AGENTS.md
Step 14: Git Commit & Push
git add .
git commit -m "feat/fix/chore: description"
git push
Traceability Validation (Article V)
Ensure 100% traceability throughout:
REQ-* → DES-* → TSK-* → Code → Test
CLI Commands
# Requirements
npx musubix requirements analyze <file>
npx musubix requirements validate <file>
# Design
npx musubix design generate <file>
npx musubix design patterns <context>
# Code Generation
npx musubix codegen generate <file>
# Traceability
npx musubix trace matrix
npx musubix trace validate
Constitutional Articles Checklist
- Article I: Library-First - Is this a standalone library?
- Article II: CLI Interface - Does it expose CLI?
- Article III: Test-First - Are tests written first?
- Article IV: EARS Format - Are requirements in EARS?
- Article V: Traceability - Is everything traceable?
- Article VI: Project Memory - Did you check steering/?
- Article VII: Design Patterns - Are patterns documented?
- Article VIII: Decision Records - Is ADR created?
- Article IX: Quality Gates - Are quality checks passed?