musubi-sdd 5.0.0 → 5.6.1

package/src/templates/agents/claude-code/skills/change-impact-analyzer/dependency-graph-patterns.md

@@ -9,16 +9,19 @@ Patterns for building and analyzing dependency graphs in software systems.
 ## Types of Dependencies
 
 ### Direct Dependencies
+
 ```
 A → B: A directly uses B
 ```
 
 ### Transitive Dependencies
+
 ```
 A → B → C: A depends on C through B
 ```
 
 ### Circular Dependencies
+
 ```
 A → B → C → A: Problematic cycle
 ```
@@ -43,7 +46,7 @@ const graph: DependencyGraph = {
   edges: new Map([
     ['auth.ts', new Set(['user.ts', 'db.ts'])],
     ['user.ts', new Set(['db.ts'])],
-  ])
+  ]),
 };
 ```
 
@@ -52,12 +55,12 @@ const graph: DependencyGraph = {
 ```dot
 digraph Dependencies {
   rankdir=TB;
-  
+
   // Nodes
   auth [label="auth.ts"];
   user [label="user.ts"];
   db [label="db.ts"];
-  
+
   // Edges
   auth -> user;
   auth -> db;
@@ -78,14 +81,14 @@ function getAllDependencies(
   visited = new Set<string>()
 ): Set<string> {
   if (visited.has(node)) return visited;
-  
+
   visited.add(node);
-  
+
   const deps = graph.edges.get(node) || new Set();
   for (const dep of deps) {
     getAllDependencies(graph, dep, visited);
   }
-  
+
   return visited;
 }
 ```
@@ -93,18 +96,16 @@ function getAllDependencies(
 ### Find Circular Dependencies
 
 ```typescript
-function findCircularDependencies(
-  graph: DependencyGraph
-): string[][] {
+function findCircularDependencies(graph: DependencyGraph): string[][] {
   const cycles: string[][] = [];
   const visited = new Set<string>();
   const recursionStack = new Set<string>();
-  
+
   function dfs(node: string, path: string[]): void {
     visited.add(node);
     recursionStack.add(node);
     path.push(node);
-    
+
     const deps = graph.edges.get(node) || new Set();
     for (const dep of deps) {
       if (!visited.has(dep)) {
@@ -115,17 +116,17 @@ function findCircularDependencies(
         cycles.push(path.slice(cycleStart));
       }
     }
-    
+
     path.pop();
     recursionStack.delete(node);
   }
-  
+
   for (const node of graph.nodes.keys()) {
     if (!visited.has(node)) {
       dfs(node, []);
     }
   }
-  
+
   return cycles;
 }
 ```
@@ -137,29 +138,29 @@ function topologicalSort(graph: DependencyGraph): string[] {
   const inDegree = new Map<string, number>();
   const result: string[] = [];
   const queue: string[] = [];
-  
+
   // Initialize in-degrees
   for (const node of graph.nodes.keys()) {
     inDegree.set(node, 0);
   }
-  
+
   for (const deps of graph.edges.values()) {
     for (const dep of deps) {
       inDegree.set(dep, (inDegree.get(dep) || 0) + 1);
     }
   }
-  
+
   // Start with nodes that have no dependencies
   for (const [node, degree] of inDegree) {
     if (degree === 0) {
       queue.push(node);
     }
   }
-  
+
   while (queue.length > 0) {
     const node = queue.shift()!;
     result.push(node);
-    
+
     const deps = graph.edges.get(node) || new Set();
     for (const dep of deps) {
       inDegree.set(dep, inDegree.get(dep)! - 1);
@@ -168,7 +169,7 @@ function topologicalSort(graph: DependencyGraph): string[] {
       }
     }
   }
-  
+
   return result;
 }
 ```
@@ -178,13 +179,11 @@ function topologicalSort(graph: DependencyGraph): string[] {
 ## Impact Scoring
 
 ### Afferent Coupling (Ca)
+
 Number of modules that depend on this module.
 
 ```typescript
-function getAfferentCoupling(
-  graph: DependencyGraph,
-  node: string
-): number {
+function getAfferentCoupling(graph: DependencyGraph, node: string): number {
   let count = 0;
   for (const [source, deps] of graph.edges) {
     if (deps.has(node)) {
@@ -196,13 +195,11 @@ function getAfferentCoupling(
 ```
 
 ### Efferent Coupling (Ce)
+
 Number of modules this module depends on.
 
 ```typescript
-function getEfferentCoupling(
-  graph: DependencyGraph,
-  node: string
-): number {
+function getEfferentCoupling(graph: DependencyGraph, node: string): number {
   return graph.edges.get(node)?.size || 0;
 }
 ```
@@ -269,10 +266,10 @@ function extractImports(filePath: string): string[] {
     ts.ScriptTarget.Latest,
     true
   );
-  
+
   const imports: string[] = [];
-  
-  ts.forEachChild(sourceFile, (node) => {
+
+  ts.forEachChild(sourceFile, node => {
     if (ts.isImportDeclaration(node)) {
       const moduleSpecifier = node.moduleSpecifier;
       if (ts.isStringLiteral(moduleSpecifier)) {
@@ -280,7 +277,7 @@ function extractImports(filePath: string): string[] {
       }
     }
   });
-  
+
   return imports;
 }
 ```
@@ -290,10 +287,7 @@ function extractImports(filePath: string): string[] {
 ```typescript
 function getDependencies(packagePath: string): string[] {
   const pkg = JSON.parse(fs.readFileSync(packagePath, 'utf8'));
-  return [
-    ...Object.keys(pkg.dependencies || {}),
-    ...Object.keys(pkg.devDependencies || {})
-  ];
+  return [...Object.keys(pkg.dependencies || {}), ...Object.keys(pkg.devDependencies || {})];
 }
 ```
 
@@ -302,12 +296,9 @@ function getDependencies(packagePath: string): string[] {
 ## Change Impact from Graph
 
 ```typescript
-function getImpactedModules(
-  graph: DependencyGraph,
-  changedModules: string[]
-): Set<string> {
+function getImpactedModules(graph: DependencyGraph, changedModules: string[]): Set<string> {
   const impacted = new Set<string>();
-  
+
   // Find all modules that depend on changed modules
   for (const changed of changedModules) {
     // Reverse DFS to find dependents
@@ -321,7 +312,7 @@ function getImpactedModules(
       }
     }
   }
-  
+
   return impacted;
 }
 ```
@@ -331,18 +322,21 @@ function getImpactedModules(
 ## Dependency Analysis Checklist
 
 ### Build Graph
+
 - [ ] Parse source files
 - [ ] Extract import statements
 - [ ] Resolve module paths
 - [ ] Store in graph structure
 
 ### Analyze
+
 - [ ] Find circular dependencies
 - [ ] Calculate coupling metrics
 - [ ] Identify hotspots
 - [ ] Generate reports
 
 ### Visualize
+
 - [ ] Create diagrams
 - [ ] Highlight problem areas
 - [ ] Show change impact

package/src/templates/agents/claude-code/skills/change-impact-analyzer/impact-analysis-template.md

@@ -23,25 +23,29 @@ Framework for analyzing the impact of proposed changes on a system.
 # Change Impact Analysis: [Change Name]
 
 ## Change Overview
-| Field | Value |
-|-------|-------|
-| Request ID | CHG-[XXX] |
-| Requested By | [Name] |
-| Date | YYYY-MM-DD |
-| Priority | Low / Medium / High / Critical |
-| Status | Draft / Under Review / Approved / Rejected |
+
+| Field        | Value                                      |
+| ------------ | ------------------------------------------ |
+| Request ID   | CHG-[XXX]                                  |
+| Requested By | [Name]                                     |
+| Date         | YYYY-MM-DD                                 |
+| Priority     | Low / Medium / High / Critical             |
+| Status       | Draft / Under Review / Approved / Rejected |
 
 ---
 
 ## 1. Change Description
 
 ### What is being changed?
+
 [Clear description of the proposed change]
 
 ### Why is this change needed?
+
 [Business justification]
 
 ### What is the expected outcome?
+
 [Success criteria]
 
 ---
@@ -50,26 +54,26 @@ Framework for analyzing the impact of proposed changes on a system.
 
 ### Files Affected
 
-| File/Module | Change Type | Effort |
-|-------------|-------------|--------|
-| src/auth/login.ts | Modify | Medium |
-| src/api/users.ts | Modify | Low |
-| tests/auth.test.ts | Add | Medium |
+| File/Module        | Change Type | Effort |
+| ------------------ | ----------- | ------ |
+| src/auth/login.ts  | Modify      | Medium |
+| src/api/users.ts   | Modify      | Low    |
+| tests/auth.test.ts | Add         | Medium |
 
 ### Dependencies
 
-| Dependency | Impact | Action Needed |
-|------------|--------|---------------|
-| User Service | Breaking | Update API |
-| Auth Library | Compatible | None |
-| Database | Schema change | Migration |
+| Dependency   | Impact        | Action Needed |
+| ------------ | ------------- | ------------- |
+| User Service | Breaking      | Update API    |
+| Auth Library | Compatible    | None          |
+| Database     | Schema change | Migration     |
 
 ### APIs Affected
 
-| API | Change | Breaking |
-|-----|--------|----------|
-| POST /login | New field | No |
-| GET /user | New response field | No |
+| API         | Change             | Breaking |
+| ----------- | ------------------ | -------- |
+| POST /login | New field          | No       |
+| GET /user   | New response field | No       |
 
 ---
 
@@ -77,20 +81,20 @@ Framework for analyzing the impact of proposed changes on a system.
 
 ### Technical Impact
 
-| Area | Impact Level | Description |
-|------|--------------|-------------|
-| Performance | Low | No significant change |
-| Security | Medium | New auth flow |
-| Scalability | Low | No change |
-| Maintainability | Medium | Added complexity |
+| Area            | Impact Level | Description           |
+| --------------- | ------------ | --------------------- |
+| Performance     | Low          | No significant change |
+| Security        | Medium       | New auth flow         |
+| Scalability     | Low          | No change             |
+| Maintainability | Medium       | Added complexity      |
 
 ### Business Impact
 
-| Area | Impact Level | Description |
-|------|--------------|-------------|
-| Users | Medium | New login step |
-| Operations | Low | Minor training |
-| Revenue | None | N/A |
+| Area       | Impact Level | Description    |
+| ---------- | ------------ | -------------- |
+| Users      | Medium       | New login step |
+| Operations | Low          | Minor training |
+| Revenue    | None         | N/A            |
 
 ---
 
@@ -98,13 +102,14 @@ Framework for analyzing the impact of proposed changes on a system.
 
 ### Risks
 
-| Risk | Probability | Impact | Mitigation |
-|------|-------------|--------|------------|
-| User confusion | Medium | Medium | Clear UI guidance |
-| Integration failure | Low | High | Thorough testing |
-| Performance regression | Low | Medium | Load testing |
+| Risk                   | Probability | Impact | Mitigation        |
+| ---------------------- | ----------- | ------ | ----------------- |
+| User confusion         | Medium      | Medium | Clear UI guidance |
+| Integration failure    | Low         | High   | Thorough testing  |
+| Performance regression | Low         | Medium | Load testing      |
 
 ### Rollback Plan
+
 1. [Step 1 to revert]
 2. [Step 2 to revert]
 3. [Verification steps]
@@ -115,19 +120,19 @@ Framework for analyzing the impact of proposed changes on a system.
 
 ### Tasks
 
-| Task | Owner | Estimate | Dependencies |
-|------|-------|----------|--------------|
-| Update auth logic | [Name] | 2 days | None |
-| Add tests | [Name] | 1 day | Auth logic |
+| Task                 | Owner  | Estimate | Dependencies   |
+| -------------------- | ------ | -------- | -------------- |
+| Update auth logic    | [Name] | 2 days   | None           |
+| Add tests            | [Name] | 1 day    | Auth logic     |
 | Update documentation | [Name] | 0.5 days | Implementation |
 
 ### Timeline
 
-| Phase | Start | End | Owner |
-|-------|-------|-----|-------|
+| Phase       | Start | End   | Owner    |
+| ----------- | ----- | ----- | -------- |
 | Development | MM/DD | MM/DD | Dev Team |
-| Testing | MM/DD | MM/DD | QA Team |
-| Deployment | MM/DD | MM/DD | DevOps |
+| Testing     | MM/DD | MM/DD | QA Team  |
+| Deployment  | MM/DD | MM/DD | DevOps   |
 
 ---
 
@@ -143,31 +148,33 @@ Framework for analyzing the impact of proposed changes on a system.
 
 ## 7. Communication Plan
 
-| Audience | Channel | When | Owner |
-|----------|---------|------|-------|
-| Dev Team | Slack | Before start | [Name] |
-| Stakeholders | Email | Before deploy | [Name] |
-| Users | In-app | After deploy | [Name] |
+| Audience     | Channel | When          | Owner  |
+| ------------ | ------- | ------------- | ------ |
+| Dev Team     | Slack   | Before start  | [Name] |
+| Stakeholders | Email   | Before deploy | [Name] |
+| Users        | In-app  | After deploy  | [Name] |
 
 ---
 
 ## 8. Approval
 
-| Approver | Role | Decision | Date |
-|----------|------|----------|------|
-| [Name] | Tech Lead | | |
-| [Name] | Product Owner | | |
-| [Name] | Security | | |
+| Approver | Role          | Decision | Date |
+| -------- | ------------- | -------- | ---- |
+| [Name]   | Tech Lead     |          |      |
+| [Name]   | Product Owner |          |      |
+| [Name]   | Security      |          |      |
 
 ---
 
 ## 9. Post-Implementation
 
 ### Verification Steps
+
 - [ ] [Verification 1]
 - [ ] [Verification 2]
 
 ### Monitoring
+
 - [ ] Error rates checked
 - [ ] Performance baseline compared
 - [ ] User feedback collected
@@ -216,17 +223,18 @@ git log --oneline --name-only -- src/changed-file.ts | \
 
 ## Impact Severity Matrix
 
-| Probability ↓ / Impact → | Low | Medium | High |
-|---------------------------|-----|--------|------|
-| **High** | Medium | High | Critical |
-| **Medium** | Low | Medium | High |
-| **Low** | Low | Low | Medium |
+| Probability ↓ / Impact → | Low    | Medium | High     |
+| ------------------------ | ------ | ------ | -------- |
+| **High**                 | Medium | High   | Critical |
+| **Medium**               | Low    | Medium | High     |
+| **Low**                  | Low    | Low    | Medium   |
 
 ---
 
 ## Quick Impact Checklist
 
 ### Before Approving
+
 - [ ] All affected files identified
 - [ ] Breaking changes documented
 - [ ] Dependencies analyzed
@@ -237,6 +245,7 @@ git log --oneline --name-only -- src/changed-file.ts | \
 - [ ] Stakeholders notified
 
 ### Red Flags
+
 - 🚩 Many files affected
 - 🚩 Database schema changes
 - 🚩 Public API breaking changes

package/src/templates/agents/claude-code/skills/cloud-architect/aws-patterns.md

@@ -62,29 +62,20 @@ resources:
 ```yaml
 # task-definition.json
 {
-  "family": "my-api",
-  "networkMode": "awsvpc",
-  "requiresCompatibilities": ["FARGATE"],
-  "cpu": "256",
-  "memory": "512",
-  "containerDefinitions": [
-    {
-      "name": "api",
-      "image": "my-api:latest",
-      "portMappings": [
-        {
-          "containerPort": 3000,
-          "protocol": "tcp"
-        }
-      ],
-      "environment": [
-        {
-          "name": "DATABASE_URL",
-          "value": "postgres://..."
-        }
-      ]
-    }
-  ]
+  'family': 'my-api',
+  'networkMode': 'awsvpc',
+  'requiresCompatibilities': ['FARGATE'],
+  'cpu': '256',
+  'memory': '512',
+  'containerDefinitions':
+    [
+      {
+        'name': 'api',
+        'image': 'my-api:latest',
+        'portMappings': [{ 'containerPort': 3000, 'protocol': 'tcp' }],
+        'environment': [{ 'name': 'DATABASE_URL', 'value': 'postgres://...' }],
+      },
+    ],
 }
 ```
 
@@ -124,7 +115,7 @@ Resources:
     Properties:
       CidrBlock: 10.0.0.0/16
       EnableDnsHostnames: true
-      
+
   PublicSubnet1:
     Type: AWS::EC2::Subnet
     Properties:
@@ -132,7 +123,7 @@ Resources:
       CidrBlock: 10.0.1.0/24
       AvailabilityZone: !Select [0, !GetAZs '']
       MapPublicIpOnLaunch: true
-      
+
   PrivateSubnet1:
     Type: AWS::EC2::Subnet
     Properties:
@@ -149,10 +140,7 @@ Resources:
   "Statement": [
     {
       "Effect": "Allow",
-      "Action": [
-        "dynamodb:GetItem",
-        "dynamodb:PutItem"
-      ],
+      "Action": ["dynamodb:GetItem", "dynamodb:PutItem"],
       "Resource": "arn:aws:dynamodb:*:*:table/users",
       "Condition": {
         "StringEquals": {
@@ -195,45 +183,50 @@ Resources:
 
 ### Compute Savings
 
-| Option | Savings | Use Case |
-|--------|---------|----------|
+| Option             | Savings   | Use Case              |
+| ------------------ | --------- | --------------------- |
 | Reserved Instances | Up to 72% | Predictable workloads |
-| Savings Plans | Up to 72% | Flexible compute |
-| Spot Instances | Up to 90% | Fault-tolerant |
+| Savings Plans      | Up to 72% | Flexible compute      |
+| Spot Instances     | Up to 90% | Fault-tolerant        |
 
 ### Storage Tiers
 
-| Tier | Cost | Access |
-|------|------|--------|
-| S3 Standard | $$$ | Frequent |
-| S3 IA | $$ | Infrequent |
-| S3 Glacier | $ | Archive |
+| Tier        | Cost | Access     |
+| ----------- | ---- | ---------- |
+| S3 Standard | $$$  | Frequent   |
+| S3 IA       | $$   | Infrequent |
+| S3 Glacier  | $    | Archive    |
 
 ---
 
 ## Well-Architected Checklist
 
 ### Operational Excellence
+
 - [ ] Infrastructure as code
 - [ ] Automated deployments
 - [ ] Monitoring and alerting
 
 ### Security
+
 - [ ] Least privilege IAM
 - [ ] Encryption at rest and in transit
 - [ ] VPC isolation
 
 ### Reliability
+
 - [ ] Multi-AZ deployment
 - [ ] Auto-scaling configured
 - [ ] Disaster recovery plan
 
 ### Performance
+
 - [ ] Right-sized resources
 - [ ] Caching implemented
 - [ ] CDN for static content
 
 ### Cost Optimization
+
 - [ ] Reserved/spot usage
 - [ ] Resource tagging
 - [ ] Cost monitoring