musubi-sdd 5.0.0 → 5.6.1

package/src/templates/agents/claude-code/skills/performance-optimizer/benchmark-template.md

@@ -8,68 +8,76 @@ Template for conducting performance benchmarks.
 
 ## Benchmark Document
 
-```markdown
+````markdown
 # Performance Benchmark Report
 
 ## Metadata
 
-| Field | Value |
-|-------|-------|
-| Component | [Component Name] |
-| Date | YYYY-MM-DD |
-| Environment | [dev/staging/prod] |
-| Version | [Version/Commit] |
-| Author | performance-optimizer |
+| Field       | Value                 |
+| ----------- | --------------------- |
+| Component   | [Component Name]      |
+| Date        | YYYY-MM-DD            |
+| Environment | [dev/staging/prod]    |
+| Version     | [Version/Commit]      |
+| Author      | performance-optimizer |
 
 ---
 
 ## 1. Objectives
 
 ### What We're Testing
+
 [Clear description of what is being benchmarked]
 
 ### Success Criteria
-| Metric | Threshold | Priority |
-|--------|-----------|----------|
-| Response Time p95 | < 200ms | Critical |
-| Throughput | > 1000 req/s | High |
-| Error Rate | < 0.1% | Critical |
-| Memory Usage | < 512MB | Medium |
+
+| Metric            | Threshold    | Priority |
+| ----------------- | ------------ | -------- |
+| Response Time p95 | < 200ms      | Critical |
+| Throughput        | > 1000 req/s | High     |
+| Error Rate        | < 0.1%       | Critical |
+| Memory Usage      | < 512MB      | Medium   |
 
 ---
 
 ## 2. Test Environment
 
 ### Hardware
+
 - **CPU**: [e.g., 4 vCPU]
 - **Memory**: [e.g., 8 GB]
 - **Storage**: [e.g., SSD]
 - **Network**: [e.g., 1 Gbps]
 
 ### Software
+
 - **OS**: [e.g., Ubuntu 22.04]
 - **Runtime**: [e.g., Node.js 20.x]
 - **Database**: [e.g., PostgreSQL 15]
 
 ### Configuration
+
 ```yaml
 # Key settings
 db_pool_size: 20
 cache_ttl: 3600
 workers: 4
 ```
+````
 
 ---
 
 ## 3. Scenarios
 
 ### Scenario 1: [Name]
+
 - **Description**: [What this tests]
 - **Users**: [Concurrent users]
 - **Duration**: [Test duration]
 - **Data**: [Test data used]
 
 ### Scenario 2: [Name]
+
 ...
 
 ---
@@ -78,13 +86,13 @@ workers: 4
 
 ### Summary
 
-| Metric | Scenario 1 | Scenario 2 | Target | Status |
-|--------|------------|------------|--------|--------|
-| p50 Latency | 45ms | 52ms | <100ms | ✅ |
-| p95 Latency | 120ms | 180ms | <200ms | ✅ |
-| p99 Latency | 250ms | 380ms | <500ms | ✅ |
-| Throughput | 1,250 req/s | 980 req/s | >1000 | ⚠️ |
-| Error Rate | 0.01% | 0.08% | <0.1% | ✅ |
+| Metric      | Scenario 1  | Scenario 2 | Target | Status |
+| ----------- | ----------- | ---------- | ------ | ------ |
+| p50 Latency | 45ms        | 52ms       | <100ms | ✅     |
+| p95 Latency | 120ms       | 180ms      | <200ms | ✅     |
+| p99 Latency | 250ms       | 380ms      | <500ms | ✅     |
+| Throughput  | 1,250 req/s | 980 req/s  | >1000  | ⚠️     |
+| Error Rate  | 0.01%       | 0.08%      | <0.1%  | ✅     |
 
 ### Latency Distribution
 
@@ -100,40 +108,43 @@ Percentile | Scenario 1 | Scenario 2
 
 ### Resource Usage
 
-| Resource | Peak | Average | Limit |
-|----------|------|---------|-------|
-| CPU | 85% | 65% | 100% |
-| Memory | 420MB | 350MB | 512MB |
-| DB Connections | 18 | 12 | 20 |
+| Resource       | Peak  | Average | Limit |
+| -------------- | ----- | ------- | ----- |
+| CPU            | 85%   | 65%     | 100%  |
+| Memory         | 420MB | 350MB   | 512MB |
+| DB Connections | 18    | 12      | 20    |
 
 ---
 
 ## 5. Bottlenecks Identified
 
 ### Bottleneck 1: [Name]
+
 - **Symptom**: [What was observed]
 - **Cause**: [Root cause]
 - **Impact**: [Performance impact]
 - **Recommendation**: [How to fix]
 
 ### Bottleneck 2: [Name]
+
 ...
 
 ---
 
 ## 6. Recommendations
 
-| Priority | Action | Expected Impact |
-|----------|--------|-----------------|
-| High | Add database index on X | -30% latency |
-| Medium | Enable response caching | +50% throughput |
-| Low | Optimize JSON serialization | -5% CPU |
+| Priority | Action                      | Expected Impact |
+| -------- | --------------------------- | --------------- |
+| High     | Add database index on X     | -30% latency    |
+| Medium   | Enable response caching     | +50% throughput |
+| Low      | Optimize JSON serialization | -5% CPU         |
 
 ---
 
 ## 7. Graphs
 
 [Include relevant graphs:]
+
 - Latency over time
 - Throughput over time
 - Error rate over time
@@ -144,16 +155,20 @@ Percentile | Scenario 1 | Scenario 2
 ## 8. Conclusion
 
 ### Pass/Fail
+
 [Did the benchmark meet success criteria?]
 
 ### Key Findings
+
 1. [Finding 1]
 2. [Finding 2]
 
 ### Next Steps
+
 1. [ ] [Action item 1]
 2. [ ] [Action item 2]
-```
+
+````
 
 ---
 
@@ -190,14 +205,14 @@ const scenarios = [
 async function runBenchmarks() {
   for (const scenario of scenarios) {
     console.log(`Running: ${scenario.name}`);
-    
+
     const result = await autocannon({
       ...config,
       method: scenario.method,
       path: scenario.path,
       body: scenario.body
     });
-    
+
     console.log(`
 Results for ${scenario.name}:
 - Avg Latency: ${result.latency.average}ms
@@ -209,7 +224,7 @@ Results for ${scenario.name}:
 }
 
 runBenchmarks();
-```
+````
 
 ---
 
@@ -225,11 +240,11 @@ const errorRate = new Rate('errors');
 
 export const options = {
   stages: [
-    { duration: '30s', target: 20 },   // Ramp up
-    { duration: '1m', target: 20 },    // Stay at 20 users
-    { duration: '30s', target: 50 },   // Ramp up more
-    { duration: '1m', target: 50 },    // Stay at 50 users
-    { duration: '30s', target: 0 },    // Ramp down
+    { duration: '30s', target: 20 }, // Ramp up
+    { duration: '1m', target: 20 }, // Stay at 20 users
+    { duration: '30s', target: 50 }, // Ramp up more
+    { duration: '1m', target: 50 }, // Stay at 50 users
+    { duration: '30s', target: 0 }, // Ramp down
   ],
   thresholds: {
     http_req_duration: ['p(95)<200'],
@@ -239,14 +254,14 @@ export const options = {
 
 export default function () {
   const res = http.get('http://localhost:3000/api/users');
-  
+
   const checkResult = check(res, {
-    'status is 200': (r) => r.status === 200,
-    'response time < 200ms': (r) => r.timings.duration < 200,
+    'status is 200': r => r.status === 200,
+    'response time < 200ms': r => r.timings.duration < 200,
   });
-  
+
   errorRate.add(!checkResult);
-  
+
   sleep(1);
 }
 ```
@@ -256,17 +271,20 @@ export default function () {
 ## Quick Checklist
 
 ### Before Benchmark
+
 - [ ] Isolated test environment
 - [ ] Warm up completed
 - [ ] Monitoring enabled
 - [ ] Baseline established
 
 ### During Benchmark
+
 - [ ] Monitor resources
 - [ ] Check for errors
 - [ ] Log unusual behavior
 
 ### After Benchmark
+
 - [ ] Compare to baseline
 - [ ] Document findings
 - [ ] Create action items

package/src/templates/agents/claude-code/skills/performance-optimizer/optimization-patterns.md

@@ -14,13 +14,13 @@ Common patterns for optimizing application performance.
 async function getUser(id: string): Promise<User> {
   // Try cache first
   let user = await cache.get(`user:${id}`);
-  
+
   if (!user) {
     // Cache miss - load from DB
     user = await db.users.findById(id);
     await cache.set(`user:${id}`, user, { ttl: 3600 });
   }
-  
+
   return user;
 }
 ```
@@ -33,10 +33,10 @@ async function getUser(id: string): Promise<User> {
 async function updateUser(id: string, data: Partial<User>): Promise<User> {
   // Update DB
   const user = await db.users.update(id, data);
-  
+
   // Update cache
   await cache.set(`user:${id}`, user, { ttl: 3600 });
-  
+
   return user;
 }
 ```
@@ -61,8 +61,8 @@ async function deleteUser(id: string): Promise<void> {
 
 ```typescript
 const pool = new Pool({
-  max: 20,        // Max connections
-  min: 5,         // Min connections
+  max: 20, // Max connections
+  min: 5, // Min connections
   idleTimeoutMillis: 30000,
   connectionTimeoutMillis: 2000,
 });
@@ -92,7 +92,7 @@ for (const user of users) {
 
 // GOOD: Eager loading
 const users = await User.findAll({
-  include: [{ model: Order }]  // 1 query with JOIN
+  include: [{ model: Order }], // 1 query with JOIN
 });
 ```
 
@@ -100,16 +100,16 @@ const users = await User.findAll({
 
 ```typescript
 // Offset pagination (simple but slow for large offsets)
-const page = await db.query(
-  'SELECT * FROM items LIMIT $1 OFFSET $2',
-  [pageSize, (page - 1) * pageSize]
-);
+const page = await db.query('SELECT * FROM items LIMIT $1 OFFSET $2', [
+  pageSize,
+  (page - 1) * pageSize,
+]);
 
 // Cursor pagination (efficient)
-const page = await db.query(
-  'SELECT * FROM items WHERE id > $1 ORDER BY id LIMIT $2',
-  [lastSeenId, pageSize]
-);
+const page = await db.query('SELECT * FROM items WHERE id > $1 ORDER BY id LIMIT $2', [
+  lastSeenId,
+  pageSize,
+]);
 ```
 
 ---
@@ -129,9 +129,7 @@ app.use(compression());
 // GET /users?fields=id,name,email
 app.get('/users', (req, res) => {
   const fields = req.query.fields?.split(',') || ['*'];
-  const users = await db.query(
-    `SELECT ${fields.join(',')} FROM users`
-  );
+  const users = await db.query(`SELECT ${fields.join(',')} FROM users`);
   res.json(users);
 });
 ```
@@ -158,11 +156,11 @@ await api.getUsers([1, 2, 3]);
 // Don't block request for slow operations
 app.post('/orders', async (req, res) => {
   const order = await createOrder(req.body);
-  
+
   // Queue async tasks
   await queue.add('send-confirmation-email', { orderId: order.id });
   await queue.add('update-inventory', { orderId: order.id });
-  
+
   res.json(order); // Respond immediately
 });
 ```
@@ -176,11 +174,7 @@ const products = await getProducts();
 const orders = await getOrders();
 
 // GOOD: Parallel
-const [users, products, orders] = await Promise.all([
-  getUsers(),
-  getProducts(),
-  getOrders()
-]);
+const [users, products, orders] = await Promise.all([getUsers(), getProducts(), getOrders()]);
 ```
 
 ---
@@ -199,7 +193,7 @@ const Settings = React.lazy(() => import('./Settings'));
 
 ```html
 <!-- Responsive images -->
-<img 
+<img
   srcset="image-300.jpg 300w, image-600.jpg 600w"
   sizes="(max-width: 600px) 300px, 600px"
   loading="lazy"
@@ -211,11 +205,11 @@ const Settings = React.lazy(() => import('./Settings'));
 
 ```typescript
 // Debounce search input
-const debouncedSearch = debounce((query) => {
+const debouncedSearch = debounce(query => {
   api.search(query);
 }, 300);
 
-input.addEventListener('input', (e) => {
+input.addEventListener('input', e => {
   debouncedSearch(e.target.value);
 });
 ```
@@ -226,13 +220,13 @@ input.addEventListener('input', (e) => {
 
 ### Key Metrics
 
-| Metric | Target | Tool |
-|--------|--------|------|
-| TTFB | < 200ms | Lighthouse |
-| FCP | < 1.8s | Lighthouse |
-| LCP | < 2.5s | Lighthouse |
-| API p95 | < 200ms | APM |
-| DB p95 | < 50ms | DB monitoring |
+| Metric  | Target  | Tool          |
+| ------- | ------- | ------------- |
+| TTFB    | < 200ms | Lighthouse    |
+| FCP     | < 1.8s  | Lighthouse    |
+| LCP     | < 2.5s  | Lighthouse    |
+| API p95 | < 200ms | APM           |
+| DB p95  | < 50ms  | DB monitoring |
 
 ### Monitoring Queries
 
@@ -249,24 +243,28 @@ LIMIT 10;
 ## Optimization Checklist
 
 ### Database
+
 - [ ] Indexes on frequently queried columns
 - [ ] Connection pooling configured
 - [ ] N+1 queries eliminated
 - [ ] Query plans analyzed (EXPLAIN)
 
 ### API
+
 - [ ] Response compression enabled
 - [ ] Pagination implemented
 - [ ] Caching strategy in place
 - [ ] Slow operations moved to background
 
 ### Frontend
+
 - [ ] Code splitting implemented
 - [ ] Images optimized and lazy loaded
 - [ ] CDN for static assets
 - [ ] Bundle size analyzed
 
 ### Infrastructure
+
 - [ ] Auto-scaling configured
 - [ ] Load balancing in place
 - [ ] CDN configured

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

@@ -53,6 +53,7 @@ musubi-orchestrate status
 ```
 
 **オーケストレーションパターン**:
+
 - **auto**: タスク内容から最適なスキルを自動選択
 - **sequential**: スキルを順番に実行（依存関係を考慮）
 - **group-chat**: 複数スキルが協議して結論を出す
@@ -114,13 +115,13 @@ musubi-workflow status
 
 ### プロジェクトマネージャーの役割
 
-| ワークフローステージ | PMの主な責務 |
-|---------------------|-------------|
-| Stage 0: Spike | 調査範囲の定義、期間設定 |
-| Stage 1-3: Requirements→Design→Tasks | 進捗追跡、リソース配分 |
+| ワークフローステージ                     | PMの主な責務               |
+| ---------------------------------------- | -------------------------- |
+| Stage 0: Spike                           | 調査範囲の定義、期間設定   |
+| Stage 1-3: Requirements→Design→Tasks     | 進捗追跡、リソース配分     |
 | Stage 4-6: Implementation→Review→Testing | リスク管理、ブロッカー解消 |
-| Stage 7-8: Deployment→Monitoring | リリース計画、本番監視 |
-| Stage 9: Retrospective | 振り返りファシリテーション |
+| Stage 7-8: Deployment→Monitoring         | リリース計画、本番監視     |
+| Stage 9: Retrospective                   | 振り返りファシリテーション |
 
 ### 推奨コマンド
 

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

@@ -8,19 +8,20 @@ Guide for running effective Agile ceremonies.
 
 ## Ceremony Overview
 
-| Ceremony | Frequency | Duration | Participants |
-|----------|-----------|----------|--------------|
-| Sprint Planning | Sprint start | 2-4 hours | Team, PO |
-| Daily Standup | Daily | 15 min | Team |
-| Sprint Review | Sprint end | 1-2 hours | Team, PO, Stakeholders |
-| Retrospective | Sprint end | 1-2 hours | Team |
-| Backlog Refinement | Weekly | 1 hour | Team, PO |
+| Ceremony           | Frequency    | Duration  | Participants           |
+| ------------------ | ------------ | --------- | ---------------------- |
+| Sprint Planning    | Sprint start | 2-4 hours | Team, PO               |
+| Daily Standup      | Daily        | 15 min    | Team                   |
+| Sprint Review      | Sprint end   | 1-2 hours | Team, PO, Stakeholders |
+| Retrospective      | Sprint end   | 1-2 hours | Team                   |
+| Backlog Refinement | Weekly       | 1 hour    | Team, PO               |
 
 ---
 
 ## Sprint Planning
 
 ### Objectives
+
 1. Define sprint goal
 2. Select user stories
 3. Create task breakdown
@@ -53,6 +54,7 @@ Guide for running effective Agile ceremonies.
 ```
 
 ### Best Practices
+
 - Come prepared with refined backlog
 - Focus on "what" not "how"
 - Don't overcommit
@@ -65,21 +67,23 @@ Guide for running effective Agile ceremonies.
 ### Format
 
 Each team member answers:
+
 1. What did I complete yesterday?
 2. What will I work on today?
 3. Do I have any blockers?
 
 ### Anti-patterns to Avoid
 
-| Anti-pattern | Better Approach |
-|--------------|-----------------|
-| Status report to manager | Team sync |
-| Solving problems in standup | Take offline |
-| Going over 15 minutes | Keep it short |
-| Only talking to Scrum Master | Talk to team |
-| Sitting down | Stand up (energy) |
+| Anti-pattern                 | Better Approach   |
+| ---------------------------- | ----------------- |
+| Status report to manager     | Team sync         |
+| Solving problems in standup  | Take offline      |
+| Going over 15 minutes        | Keep it short     |
+| Only talking to Scrum Master | Talk to team      |
+| Sitting down                 | Stand up (energy) |
 
 ### Virtual Standup Tips
+
 - Camera on
 - Mute when not speaking
 - Use visual board
@@ -91,6 +95,7 @@ Each team member answers:
 ## Sprint Review (Demo)
 
 ### Objectives
+
 1. Demonstrate completed work
 2. Get stakeholder feedback
 3. Discuss backlog priorities
@@ -121,6 +126,7 @@ Each team member answers:
 ```
 
 ### Tips for Good Demos
+
 - Use real scenarios
 - Show working software
 - Keep it interactive
@@ -132,6 +138,7 @@ Each team member answers:
 ## Retrospective
 
 ### Objectives
+
 1. Reflect on the sprint
 2. Identify improvements
 3. Create action items
@@ -139,6 +146,7 @@ Each team member answers:
 ### Formats
 
 #### Start/Stop/Continue
+
 ```
 🟢 START doing: [What new things should we try?]
 🔴 STOP doing: [What's not working?]
@@ -146,6 +154,7 @@ Each team member answers:
 ```
 
 #### 4Ls
+
 ```
 😍 LIKED: [What did you like?]
 📚 LEARNED: [What did you learn?]
@@ -154,6 +163,7 @@ Each team member answers:
 ```
 
 #### Sailboat
+
 ```
 ⛵ WIND (helps us): [What's pushing us forward?]
 ⚓ ANCHOR (slows us): [What's holding us back?]
@@ -162,6 +172,7 @@ Each team member answers:
 ```
 
 ### Facilitation Tips
+
 - Safe space - no blame
 - Everyone participates
 - Time-box discussions
@@ -174,6 +185,7 @@ Each team member answers:
 ## Backlog Refinement
 
 ### Objectives
+
 1. Clarify upcoming stories
 2. Estimate stories
 3. Break down large items
@@ -204,6 +216,7 @@ Each team member answers:
 ### Definition of Ready
 
 Story is ready when:
+
 - [ ] Clearly written with user perspective
 - [ ] Acceptance criteria defined
 - [ ] Estimated by team
@@ -217,36 +230,38 @@ Story is ready when:
 
 ### Planning Poker
 
-| Points | Meaning |
-|--------|---------|
-| 1 | Trivial |
-| 2 | Simple |
-| 3 | Moderate |
-| 5 | Complex |
-| 8 | Very Complex |
-| 13 | Epic-sized (split it) |
+| Points | Meaning               |
+| ------ | --------------------- |
+| 1      | Trivial               |
+| 2      | Simple                |
+| 3      | Moderate              |
+| 5      | Complex               |
+| 8      | Very Complex          |
+| 13     | Epic-sized (split it) |
 
 ### T-Shirt Sizing
 
 | Size | Relative Effort |
-|------|-----------------|
-| XS | Hours |
-| S | 1-2 days |
-| M | 3-5 days |
-| L | 1-2 weeks |
-| XL | Needs breakdown |
+| ---- | --------------- |
+| XS   | Hours           |
+| S    | 1-2 days        |
+| M    | 3-5 days        |
+| L    | 1-2 weeks       |
+| XL   | Needs breakdown |
 
 ---
 
 ## Remote Ceremony Tips
 
 ### Tools
+
 - Video: Zoom, Teams
 - Board: Miro, Mural
 - Voting: Mentimeter
 - Timer: Online stopwatch
 
 ### Best Practices
+
 - Camera on for engagement
 - Use virtual whiteboard
 - More breaks for longer sessions
@@ -259,24 +274,28 @@ Story is ready when:
 ## Ceremony Health Check
 
 ### Sprint Planning
+
 - [ ] Sprint goal is clear
 - [ ] Team has capacity
 - [ ] Stories are refined
 - [ ] Commitment is realistic
 
 ### Daily Standup
+
 - [ ] Starts on time
 - [ ] Finishes in 15 min
 - [ ] Blockers are raised
 - [ ] Team is engaged
 
 ### Sprint Review
+
 - [ ] Working software shown
 - [ ] Stakeholders present
 - [ ] Feedback captured
 - [ ] Team celebrated
 
 ### Retrospective
+
 - [ ] Safe environment
 - [ ] Everyone participated
 - [ ] Actions are specific