[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C2N5HH2DWNKPYZJRVT1B1A":3,"skill-same:01M6C2N5HH2DWNKPYZJRVT1B1A":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6C2N5HH2DWNKPYZJRVT1B1A","architecture-evolution",null,"Manage architecture changes with impact analysis, ADR generation, migration planning, and breaking change tracking","jmagly\u002Faiwg","jmagly","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1159087?v=4","01M6C10AK8N2WCSQN11FYGTJWN","Joseph Magly","01M6C10AQ8A2RMED1Y1BSVY7NF",229,"MIT","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fcodex-sdlc\u002Fskills\u002Farchitecture-evolution\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40],"architecture","architecture evolution","evolution","analysis","breaking change","adr","planning","tracking","change","migration","impact analysis","manage","generation","impact","with","changes","change tracking","2026-11-10 10:12:30",false,"---\nnamespace: aiwg\nname: architecture-evolution\nplatforms: [all]\ndescription: Manage architecture changes with impact analysis, ADR generation, migration planning, and breaking change tracking\n\n---\n\n# architecture-evolution\n\nManage architecture changes with impact analysis, ADR generation, and migration planning.\n\n## Triggers\n\n\nAlternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):\n\n- \"ADR\" → Architecture Decision Record creation\n- \"C4 model\" → architecture diagram update\n- \"architecture drift\" → deviation from baseline\n\n## Purpose\n\nThis skill manages controlled architecture evolution by:\n- Analyzing impact of proposed changes\n- Generating Architecture Decision Records (ADRs)\n- Planning migration paths\n- Tracking breaking changes\n- Coordinating cross-team dependencies\n- Maintaining architecture health\n\n## Behavior\n\nWhen triggered, this skill:\n\n1. **Identifies change scope**:\n   - Parse proposed change\n   - Map affected components\n   - Identify stakeholders\n   - Classify change type\n\n2. **Performs impact analysis**:\n   - Direct dependencies\n   - Transitive dependencies\n   - Data migration needs\n   - API compatibility\n   - Performance implications\n\n3. **Generates documentation**:\n   - Create or update ADR\n   - Update component diagrams\n   - Document migration path\n   - Update API contracts\n\n4. **Plans migration**:\n   - Phase-by-phase approach\n   - Rollback strategy\n   - Feature flags if needed\n   - Communication plan\n\n5. **Coordinates execution**:\n   - Notify affected teams\n   - Track migration progress\n   - Validate each phase\n   - Confirm completion\n\n## Change Categories\n\n### Component Addition\n\n```yaml\ncomponent_addition:\n  description: Adding new service, module, or component\n\n  impact_areas:\n    - infrastructure: New deployment resources\n    - networking: New routes, load balancing\n    - security: Access controls, secrets\n    - monitoring: New dashboards, alerts\n    - dependencies: Integration points\n\n  artifacts:\n    - adr: ADR for new component\n    - diagram: Updated architecture diagram\n    - contract: API specification\n    - runbook: Operational documentation\n```\n\n### Component Deprecation\n\n```yaml\ncomponent_deprecation:\n  description: Phasing out existing component\n\n  impact_areas:\n    - dependents: Who uses this component?\n    - migration: Where do they migrate to?\n    - timeline: How long to deprecate?\n    - data: What happens to stored data?\n    - cleanup: Resource removal plan\n\n  artifacts:\n    - adr: Deprecation decision record\n    - migration_guide: How to migrate\n    - timeline: Phase-out schedule\n    - communication: Stakeholder notifications\n```\n\n### Breaking Change\n\n```yaml\nbreaking_change:\n  description: Incompatible change to existing interface\n\n  impact_areas:\n    - api_consumers: Who calls this API?\n    - contract: What changes in the contract?\n    - versioning: How to version the change?\n    - backward_compat: Can we support both?\n    - rollout: How to phase the rollout?\n\n  artifacts:\n    - adr: Breaking change decision\n    - migration_guide: Upgrade instructions\n    - changelog: Version history update\n    - deprecation_notice: Timeline for old version\n```\n\n### Technology Migration\n\n```yaml\ntechnology_migration:\n  description: Replacing underlying technology\n\n  impact_areas:\n    - learning_curve: Team training needs\n    - code_changes: Rewrite scope\n    - data_migration: Data format changes\n    - testing: New test requirements\n    - operations: New ops procedures\n\n  artifacts:\n    - adr: Technology choice rationale\n    - migration_plan: Step-by-step migration\n    - runbooks: Updated operational docs\n    - training: Team education materials\n```\n\n## Impact Analysis Template\n\n```markdown\n# Architecture Impact Analysis\n\n**Change**: [Description of proposed change]\n**Date**: 2025-12-08\n**Author**: [Name]\n**Status**: Under Review\n\n## Change Summary\n\n### What is Changing\n[Detailed description of the change]\n\n### Why This Change\n[Business or technical driver]\n\n### Scope\n- **Type**: Component Addition \u002F Deprecation \u002F Breaking Change \u002F Migration\n- **Risk Level**: Low \u002F Medium \u002F High \u002F Critical\n- **Estimated Effort**: [Time estimate]\n\n## Impact Assessment\n\n### Direct Dependencies\n\n| Component | Impact | Migration Required | Effort |\n|-----------|--------|-------------------|--------|\n| Service A | High | Yes | 2 weeks |\n| Service B | Medium | Yes | 1 week |\n| Library X | Low | No | N\u002FA |\n\n### Transitive Dependencies\n\n```\nProposed Change\n    ├── Service A (direct)\n    │   ├── Service C (transitive)\n    │   └── Service D (transitive)\n    └── Service B (direct)\n        └── Service E (transitive)\n```\n\nTotal affected: 5 components\n\n### Data Impact\n\n| Data Store | Action | Data Volume | Downtime |\n|------------|--------|-------------|----------|\n| PostgreSQL | Schema migration | 10M rows | ~5 min |\n| Redis | Key format change | 100K keys | None |\n| S3 | Path restructure | 500GB | None |\n\n### API Impact\n\n| API | Change Type | Breaking | Version Strategy |\n|-----|-------------|----------|------------------|\n| \u002Fusers | Response field added | No | Additive |\n| \u002Forders | Endpoint deprecated | Yes | v1 → v2 |\n| \u002Fauth | Token format | Yes | Dual support 30d |\n\n### Performance Impact\n\n| Metric | Current | Expected | Risk |\n|--------|---------|----------|------|\n| Latency p99 | 150ms | 180ms | Medium |\n| Throughput | 1000 rps | 1200 rps | Positive |\n| Memory | 2GB | 2.5GB | Low |\n\n### Security Impact\n\n| Area | Change | Risk | Mitigation |\n|------|--------|------|------------|\n| Auth | New token type | Medium | Security review |\n| Data | New PII field | High | Privacy assessment |\n| Network | New endpoint | Low | Firewall rules |\n\n## Risk Assessment\n\n| Risk | Probability | Impact | Mitigation |\n|------|-------------|--------|------------|\n| Migration failure | Medium | High | Rollback plan |\n| Performance regression | Low | Medium | Load testing |\n| Data loss | Low | Critical | Backup + validation |\n| Extended downtime | Low | High | Blue-green deploy |\n\n## Migration Plan\n\n### Phase 1: Preparation (Week 1)\n- [ ] Create new infrastructure\n- [ ] Deploy in shadow mode\n- [ ] Set up monitoring\n- [ ] Train ops team\n\n### Phase 2: Gradual Rollout (Week 2-3)\n- [ ] 10% traffic migration\n- [ ] Monitor for issues\n- [ ] 50% traffic migration\n- [ ] Validate performance\n\n### Phase 3: Full Migration (Week 4)\n- [ ] 100% traffic migration\n- [ ] Deprecate old system\n- [ ] Cleanup resources\n\n### Rollback Plan\n\n| Phase | Rollback Time | Data Impact | Procedure |\n|-------|---------------|-------------|-----------|\n| Phase 1 | 5 minutes | None | Disable shadow |\n| Phase 2 | 15 minutes | Sync required | Route traffic back |\n| Phase 3 | 30 minutes | Manual merge | Full rollback |\n\n## Stakeholders\n\n| Role | Name | Notification | Approval |\n|------|------|--------------|----------|\n| Architecture | Sarah Chen | Required | Required |\n| Security | Elena Rodriguez | Required | Required |\n| Ops\u002FSRE | David Kim | Required | Informed |\n| Product | James Wilson | Informed | Informed |\n| Affected Teams | [List] | Required | Informed |\n\n## Decision\n\n**Recommendation**: Proceed with Phase 1\n**Conditions**:\n- Security review complete\n- Load test passes\n- Stakeholder sign-off\n\n## Related Documents\n\n- ADR: .aiwg\u002Farchitecture\u002Fadr-XXX.md\n- Migration Guide: .aiwg\u002Farchitecture\u002Fmigrations\u002FXXX.md\n- Rollback Procedure: .aiwg\u002Fdeployment\u002Frollback-XXX.md\n```\n\n## ADR Generation\n\nWhen evolution is approved, generate ADR:\n\n```markdown\n# ADR-XXX: [Title]\n\n## Status\n\nProposed → Accepted → Superseded by ADR-YYY (if applicable)\n\n## Context\n\n[What is the issue that we're seeing that is motivating this decision or change?]\n\n## Decision\n\n[What is the change that we're proposing and\u002For doing?]\n\n## Consequences\n\n### Positive\n- [Benefit 1]\n- [Benefit 2]\n\n### Negative\n- [Trade-off 1]\n- [Trade-off 2]\n\n### Risks\n- [Risk 1 with mitigation]\n- [Risk 2 with mitigation]\n\n## Alternatives Considered\n\n### Option A: [Name]\n[Description and why rejected]\n\n### Option B: [Name]\n[Description and why rejected]\n\n## Implementation\n\n### Migration Path\n[High-level migration steps]\n\n### Timeline\n- Phase 1: [Date] - [Description]\n- Phase 2: [Date] - [Description]\n- Phase 3: [Date] - [Description]\n\n### Rollback Strategy\n[How to undo if needed]\n\n## References\n\n- Impact Analysis: [link]\n- Design Document: [link]\n- Related ADRs: [links]\n```\n\n## Usage Examples\n\n### Plan Component Addition\n\n```\nUser: \"Evolve architecture to add caching layer\"\n\nSkill executes:\n1. Identify change: Add Redis caching\n2. Map affected components\n3. Analyze impact\n4. Generate migration plan\n\nOutput:\n\"Architecture Evolution: Add Caching Layer\n\nImpact Analysis:\n- Direct dependencies: 3 services\n- Data stores: 1 new (Redis)\n- API changes: None\n- Performance: +40% expected improvement\n\nMigration Plan:\nPhase 1: Deploy Redis cluster (Week 1)\nPhase 2: Add cache-aside to read paths (Week 2)\nPhase 3: Enable cache warming (Week 3)\nPhase 4: Monitor and tune (Week 4)\n\nRisk: Medium\n- Rollback: Disable cache reads, direct DB\n\nGenerated:\n- ADR: .aiwg\u002Farchitecture\u002Fadr-023-caching-layer.md\n- Impact Analysis: .aiwg\u002Farchitecture\u002Fimpact\u002Fcaching-layer.md\n- Migration Guide: .aiwg\u002Farchitecture\u002Fmigrations\u002Fadd-caching.md\"\n```\n\n### Handle Breaking Change\n\n```\nUser: \"Breaking change: new auth token format\"\n\nSkill analyzes:\n1. Identify all token consumers\n2. Plan dual-support period\n3. Document migration path\n\nOutput:\n\"Breaking Change Analysis: Auth Token Format\n\nImpact:\n- 5 services consume auth tokens\n- 2 external API consumers identified\n- Mobile apps: iOS 3.2+, Android 4.1+\n\nMigration Strategy:\n1. Deploy services with dual-token support\n2. Issue new tokens, accept both formats\n3. Monitor old token usage decline\n4. Set deprecation date (30 days)\n5. Remove old token support\n\nCommunication Plan:\n- Internal teams: Slack + email (immediate)\n- External consumers: Email + docs (this week)\n- Deprecation notice: 30 days minimum\n\nADR: .aiwg\u002Farchitecture\u002Fadr-024-token-format.md\"\n```\n\n### Deprecation Planning\n\n```\nUser: \"Deprecate legacy order service\"\n\nSkill executes:\n1. Map all dependents\n2. Identify migration target\n3. Plan phase-out timeline\n\nOutput:\n\"Deprecation Plan: Legacy Order Service\n\nCurrent Consumers: 8 services\nMigration Target: Order Service v2\n\nDependency Migration:\n| Consumer | Migration Effort | Target Date |\n|----------|-----------------|-------------|\n| Cart | 2 weeks | Jan 15 |\n| Checkout | 3 weeks | Jan 22 |\n| Reports | 1 week | Jan 10 |\n| ... | ... | ... |\n\nTimeline:\n- Jan 1: Deprecation notice sent\n- Jan 31: All consumers migrated\n- Feb 15: Service decommissioned\n\nData Migration:\n- 5M orders to migrate\n- Strategy: Batch migration + sync\n- Duration: 2 hours (off-peak)\n\nADR: .aiwg\u002Farchitecture\u002Fadr-025-deprecate-order-v1.md\nMigration Guide: .aiwg\u002Farchitecture\u002Fmigrations\u002Forder-v1-to-v2.md\"\n```\n\n## Integration\n\nThis skill uses:\n- `decision-support`: For architectural decisions\n- `project-awareness`: For component topology\n- `artifact-metadata`: For tracking ADRs\n\n## Agent Orchestration\n\n```yaml\nagents:\n  analysis:\n    agent: architecture-designer\n    focus: Impact analysis and design\n\n  security:\n    agent: security-architect\n    focus: Security implications\n    condition: security_relevant == true\n\n  reliability:\n    agent: reliability-engineer\n    focus: Performance and availability impact\n\n  migration:\n    agent: deployment-manager\n    focus: Migration planning and execution\n```\n\n## Configuration\n\n### Change Classification\n\n```yaml\nchange_classification:\n  risk_factors:\n    - data_migration: +2\n    - breaking_api: +3\n    - cross_team: +1\n    - production_impact: +2\n    - security_change: +2\n\n  risk_levels:\n    low: 0-2\n    medium: 3-5\n    high: 6-8\n    critical: 9+\n\n  approval_requirements:\n    low: team_lead\n    medium: architecture_review\n    high: architecture_board\n    critical: executive_approval\n```\n\n### Migration Strategies\n\n```yaml\nmigration_strategies:\n  big_bang:\n    use_when: Low risk, small scope\n    downtime: Possible\n    rollback: Full\n\n  phased:\n    use_when: Medium risk, manageable scope\n    downtime: Minimal\n    rollback: Per-phase\n\n  blue_green:\n    use_when: High availability required\n    downtime: Near-zero\n    rollback: Traffic switch\n\n  strangler:\n    use_when: Large legacy migration\n    downtime: None\n    rollback: Route traffic\n```\n\n## Output Locations\n\n- Impact analyses: `.aiwg\u002Farchitecture\u002Fimpact\u002F`\n- ADRs: `.aiwg\u002Farchitecture\u002Fadr-*.md`\n- Migration plans: `.aiwg\u002Farchitecture\u002Fmigrations\u002F`\n- Deprecation notices: `.aiwg\u002Farchitecture\u002Fdeprecations\u002F`\n\n## References\n\n- ADR template: templates\u002Fanalysis-design\u002Fadr-template.md\n- Impact analysis template: templates\u002Fanalysis-design\u002Fimpact-analysis.md\n- Migration guide template: templates\u002Fdeployment\u002Fmigration-guide.md\n- Architecture diagram: .aiwg\u002Farchitecture\u002Fdiagrams\u002F\n","# architecture-evolution\n\nManage architecture changes with impact analysis, ADR generation, and migration planning.\n\n## Triggers\n\n\nAlternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):\n\n- \"ADR\" → Architecture Decision Record creation\n- \"C4 model\" → architecture diagram update\n- \"architecture drift\" → deviation from baseline\n\n## Purpose\n\nThis skill manages controlled architecture evolution by:\n- Analyzing impact of proposed changes\n- Generating Architecture Decision Records (ADRs)\n- Planning migration paths\n- Tracking breaking changes\n- Coordinating cross-team dependencies\n- Maintaining architecture health\n\n## Behavior\n\nWhen triggered, this skill:\n\n1. **Identifies change scope**:\n   - Parse proposed change\n   - Map affected components\n   - Identify stakeholders\n   - Classify change type\n\n2. **Performs impact analysis**:\n   - Direct dependencies\n   - Transitive dependencies\n   - Data migration needs\n   - API compatibility\n   - Performance implications\n\n3. **Generates documentation**:\n   - Create or update ADR\n   - Update component diagrams\n   - Document migration path\n   - Update API contracts\n\n4. **Plans migration**:\n   - Phase-by-phase approach\n   - Rollback strategy\n   - Feature flags if needed\n   - Communication plan\n\n5. **Coordinates execution**:\n   - Notify affected teams\n   - Track migration progress\n   - Validate each phase\n   - Confirm completion\n\n## Change Categories\n\n### Component Addition\n\n```yaml\ncomponent_addition:\n  description: Adding new service, module, or component\n\n  impact_areas:\n    - infrastructure: New deployment resources\n    - networking: New routes, load balancing\n    - security: Access controls, secrets\n    - monitoring: New dashboards, alerts\n    - dependencies: Integration points\n\n  artifacts:\n    - adr: ADR for new component\n    - diagram: Updated architecture diagram\n    - contract: API specification\n    - runbook: Operational documentation\n```\n\n### Component Deprecation\n\n```yaml\ncomponent_deprecation:\n  description: Phasing out existing component\n\n  impact_areas:\n    - dependents: Who uses this component?\n    - migration: Where do they migrate to?\n    - timeline: How long to deprecate?\n    - data: What happens to stored data?\n    - cleanup: Resource removal plan\n\n  artifacts:\n    - adr: Deprecation decision record\n    - migration_guide: How to migrate\n    - timeline: Phase-out schedule\n    - communication: Stakeholder notifications\n```\n\n### Breaking Change\n\n```yaml\nbreaking_change:\n  description: Incompatible change to existing interface\n\n  impact_areas:\n    - api_consumers: Who calls this API?\n    - contract: What changes in the contract?\n    - versioning: How to version the change?\n    - backward_compat: Can we support both?\n    - rollout: How to phase the rollout?\n\n  artifacts:\n    - adr: Breaking change decision\n    - migration_guide: Upgrade instructions\n    - changelog: Version history update\n    - deprecation_notice: Timeline for old version\n```\n\n### Technology Migration\n\n```yaml\ntechnology_migration:\n  description: Replacing underlying technology\n\n  impact_areas:\n    - learning_curve: Team training needs\n    - code_changes: Rewrite scope\n    - data_migration: Data format changes\n    - testing: New test requirements\n    - operations: New ops procedures\n\n  artifacts:\n    - adr: Technology choice rationale\n    - migration_plan: Step-by-step migration\n    - runbooks: Updated operational docs\n    - training: Team education materials\n```\n\n## Impact Analysis Template\n\n```markdown\n# Architecture Impact Analysis\n\n**Change**: [Description of proposed change]\n**Date**: 2025-12-08\n**Author**: [Name]\n**Status**: Under Review\n\n## Change Summary\n\n### What is Changing\n[Detailed description of the change]\n\n### Why This Change\n[Business or technical driver]\n\n### Scope\n- **Type**: Component Addition \u002F Deprecation \u002F Breaking Change \u002F Migration\n- **Risk Level**: Low \u002F Medium \u002F High \u002F Critical\n- **Estimated Effort**: [Time estimate]\n\n## Impact Assessment\n\n### Direct Dependencies\n\n| Component | Impact | Migration Required | Effort |\n|-----------|--------|-------------------|--------|\n| Service A | High | Yes | 2 weeks |\n| Service B | Medium | Yes | 1 week |\n| Library X | Low | No | N\u002FA |\n\n### Transitive Dependencies\n\n```\nProposed Change\n    ├── Service A (direct)\n    │   ├── Service C (transitive)\n    │   └── Service D (transitive)\n    └── Service B (direct)\n        └── Service E (transitive)\n```\n\nTotal affected: 5 components\n\n### Data Impact\n\n| Data Store | Action | Data Volume | Downtime |\n|------------|--------|-------------|----------|\n| PostgreSQL | Schema migration | 10M rows | ~5 min |\n| Redis | Key format change | 100K keys | None |\n| S3 | Path restructure | 500GB | None |\n\n### API Impact\n\n| API | Change Type | Breaking | Version Strategy |\n|-----|-------------|----------|------------------|\n| \u002Fusers | Response field added | No | Additive |\n| \u002Forders | Endpoint deprecated | Yes | v1 → v2 |\n| \u002Fauth | Token format | Yes | Dual support 30d |\n\n### Performance Impact\n\n| Metric | Current | Expected | Risk |\n|--------|---------|----------|------|\n| Latency p99 | 150ms | 180ms | Medium |\n| Throughput | 1000 rps | 1200 rps | Positive |\n| Memory | 2GB | 2.5GB | Low |\n\n### Security Impact\n\n| Area | Change | Risk | Mitigation |\n|------|--------|------|------------|\n| Auth | New token type | Medium | Security review |\n| Data | New PII field | High | Privacy assessment |\n| Network | New endpoint | Low | Firewall rules |\n\n## Risk Assessment\n\n| Risk | Probability | Impact | Mitigation |\n|------|-------------|--------|------------|\n| Migration failure | Medium | High | Rollback plan |\n| Performance regression | Low | Medium | Load testing |\n| Data loss | Low | Critical | Backup + validation |\n| Extended downtime | Low | High | Blue-green deploy |\n\n## Migration Plan\n\n### Phase 1: Preparation (Week 1)\n- [ ] Create new infrastructure\n- [ ] Deploy in shadow mode\n- [ ] Set up monitoring\n- [ ] Train ops team\n\n### Phase 2: Gradual Rollout (Week 2-3)\n- [ ] 10% traffic migration\n- [ ] Monitor for issues\n- [ ] 50% traffic migration\n- [ ] Validate performance\n\n### Phase 3: Full Migration (Week 4)\n- [ ] 100% traffic migration\n- [ ] Deprecate old system\n- [ ] Cleanup resources\n\n### Rollback Plan\n\n| Phase | Rollback Time | Data Impact | Procedure |\n|-------|---------------|-------------|-----------|\n| Phase 1 | 5 minutes | None | Disable shadow |\n| Phase 2 | 15 minutes | Sync required | Route traffic back |\n| Phase 3 | 30 minutes | Manual merge | Full rollback |\n\n## Stakeholders\n\n| Role | Name | Notification | Approval |\n|------|------|--------------|----------|\n| Architecture | Sarah Chen | Required | Required |\n| Security | Elena Rodriguez | Required | Required |\n| Ops\u002FSRE | David Kim | Required | Informed |\n| Product | James Wilson | Informed | Informed |\n| Affected Teams | [List] | Required | Informed |\n\n## Decision\n\n**Recommendation**: Proceed with Phase 1\n**Conditions**:\n- Security review complete\n- Load test passes\n- Stakeholder sign-off\n\n## Related Documents\n\n- ADR: .aiwg\u002Farchitecture\u002Fadr-XXX.md\n- Migration Guide: .aiwg\u002Farchitecture\u002Fmigrations\u002FXXX.md\n- Rollback Procedure: .aiwg\u002Fdeployment\u002Frollback-XXX.md\n```\n\n## ADR Generation\n\nWhen evolution is approved, generate ADR:\n\n```markdown\n# ADR-XXX: [Title]\n\n## Status\n\nProposed → Accepted → Superseded by ADR-YYY (if applicable)\n\n## Context\n\n[What is the issue that we're seeing that is motivating this decision or change?]\n\n## Decision\n\n[What is the change that we're proposing and\u002For doing?]\n\n## Consequences\n\n### Positive\n- [Benefit 1]\n- [Benefit 2]\n\n### Negative\n- [Trade-off 1]\n- [Trade-off 2]\n\n### Risks\n- [Risk 1 with mitigation]\n- [Risk 2 with mitigation]\n\n## Alternatives Considered\n\n### Option A: [Name]\n[Description and why rejected]\n\n### Option B: [Name]\n[Description and why rejected]\n\n## Implementation\n\n### Migration Path\n[High-level migration steps]\n\n### Timeline\n- Phase 1: [Date] - [Description]\n- Phase 2: [Date] - [Description]\n- Phase 3: [Date] - [Description]\n\n### Rollback Strategy\n[How to undo if needed]\n\n## References\n\n- Impact Analysis: [link]\n- Design Document: [link]\n- Related ADRs: [links]\n```\n\n## Usage Examples\n\n### Plan Component Addition\n\n```\nUser: \"Evolve architecture to add caching layer\"\n\nSkill executes:\n1. Identify change: Add Redis caching\n2. Map affected components\n3. Analyze impact\n4. Generate migration plan\n\nOutput:\n\"Architecture Evolution: Add Caching Layer\n\nImpact Analysis:\n- Direct dependencies: 3 services\n- Data stores: 1 new (Redis)\n- API changes: None\n- Performance: +40% expected improvement\n\nMigration Plan:\nPhase 1: Deploy Redis cluster (Week 1)\nPhase 2: Add cache-aside to read paths (Week 2)\nPhase 3: Enable cache warming (Week 3)\nPhase 4: Monitor and tune (Week 4)\n\nRisk: Medium\n- Rollback: Disable cache reads, direct DB\n\nGenerated:\n- ADR: .aiwg\u002Farchitecture\u002Fadr-023-caching-layer.md\n- Impact Analysis: .aiwg\u002Farchitecture\u002Fimpact\u002Fcaching-layer.md\n- Migration Guide: .aiwg\u002Farchitecture\u002Fmigrations\u002Fadd-caching.md\"\n```\n\n### Handle Breaking Change\n\n```\nUser: \"Breaking change: new auth token format\"\n\nSkill analyzes:\n1. Identify all token consumers\n2. Plan dual-support period\n3. Document migration path\n\nOutput:\n\"Breaking Change Analysis: Auth Token Format\n\nImpact:\n- 5 services consume auth tokens\n- 2 external API consumers identified\n- Mobile apps: iOS 3.2+, Android 4.1+\n\nMigration Strategy:\n1. Deploy services with dual-token support\n2. Issue new tokens, accept both formats\n3. Monitor old token usage decline\n4. Set deprecation date (30 days)\n5. Remove old token support\n\nCommunication Plan:\n- Internal teams: Slack + email (immediate)\n- External consumers: Email + docs (this week)\n- Deprecation notice: 30 days minimum\n\nADR: .aiwg\u002Farchitecture\u002Fadr-024-token-format.md\"\n```\n\n### Deprecation Planning\n\n```\nUser: \"Deprecate legacy order service\"\n\nSkill executes:\n1. Map all dependents\n2. Identify migration target\n3. Plan phase-out timeline\n\nOutput:\n\"Deprecation Plan: Legacy Order Service\n\nCurrent Consumers: 8 services\nMigration Target: Order Service v2\n\nDependency Migration:\n| Consumer | Migration Effort | Target Date |\n|----------|-----------------|-------------|\n| Cart | 2 weeks | Jan 15 |\n| Checkout | 3 weeks | Jan 22 |\n| Reports | 1 week | Jan 10 |\n| ... | ... | ... |\n\nTimeline:\n- Jan 1: Deprecation notice sent\n- Jan 31: All consumers migrated\n- Feb 15: Service decommissioned\n\nData Migration:\n- 5M orders to migrate\n- Strategy: Batch migration + sync\n- Duration: 2 hours (off-peak)\n\nADR: .aiwg\u002Farchitecture\u002Fadr-025-deprecate-order-v1.md\nMigration Guide: .aiwg\u002Farchitecture\u002Fmigrations\u002Forder-v1-to-v2.md\"\n```\n\n## Integration\n\nThis skill uses:\n- `decision-support`: For architectural decisions\n- `project-awareness`: For component topology\n- `artifact-metadata`: For tracking ADRs\n\n## Agent Orchestration\n\n```yaml\nagents:\n  analysis:\n    agent: architecture-designer\n    focus: Impact analysis and design\n\n  security:\n    agent: security-architect\n    focus: Security implications\n    condition: security_relevant == true\n\n  reliability:\n    agent: reliability-engineer\n    focus: Performance and availability impact\n\n  migration:\n    agent: deployment-manager\n    focus: Migration planning and execution\n```\n\n## Configuration\n\n### Change Classification\n\n```yaml\nchange_classification:\n  risk_factors:\n    - data_migration: +2\n    - breaking_api: +3\n    - cross_team: +1\n    - production_impact: +2\n    - security_change: +2\n\n  risk_levels:\n    low: 0-2\n    medium: 3-5\n    high: 6-8\n    critical: 9+\n\n  approval_requirements:\n    low: team_lead\n    medium: architecture_review\n    high: architecture_board\n    critical: executive_approval\n```\n\n### Migration Strategies\n\n```yaml\nmigration_strategies:\n  big_bang:\n    use_when: Low risk, small scope\n    downtime: Possible\n    rollback: Full\n\n  phased:\n    use_when: Medium risk, manageable scope\n    downtime: Minimal\n    rollback: Per-phase\n\n  blue_green:\n    use_when: High availability required\n    downtime: Near-zero\n    rollback: Traffic switch\n\n  strangler:\n    use_when: Large legacy migration\n    downtime: None\n    rollback: Route traffic\n```\n\n## Output Locations\n\n- Impact analyses: `.aiwg\u002Farchitecture\u002Fimpact\u002F`\n- ADRs: `.aiwg\u002Farchitecture\u002Fadr-*.md`\n- Migration plans: `.aiwg\u002Farchitecture\u002Fmigrations\u002F`\n- Deprecation notices: `.aiwg\u002Farchitecture\u002Fdeprecations\u002F`\n\n## References\n\n- ADR template: templates\u002Fanalysis-design\u002Fadr-template.md\n- Impact analysis template: templates\u002Fanalysis-design\u002Fimpact-analysis.md\n- Migration guide template: templates\u002Fdeployment\u002Fmigration-guide.md\n- Architecture diagram: .aiwg\u002Farchitecture\u002Fdiagrams\u002F\n",{"name":5,"namespace":46,"platforms":47,"description":7},"aiwg",[48],"all","main","6754967c344ccb087a8de06972f55a41067b291b","agentic\u002Fcode\u002Fplugins\u002Fcodex-sdlc\u002Fskills\u002Farchitecture-evolution",36,"https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg","https:\u002F\u002Faiwg.io","https:\u002F\u002Fgithub.com\u002Fjmagly","https:\u002F\u002Fintegrolabs.io","ml\u002Fai, industrial automation, safety\u002Fsecurity, ssi\r\n\r\nmagly.net\r\nintegrolabs.io\r\naiwg.io\r\nfortemi.com\r\npagenary.com\r\nbytecask.com","2026-11-12 21:57:33",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add jmagly\u002Faiwg --skill architecture-evolution",{"tool":65,"command":66},"bunx","bunx skills add jmagly\u002Faiwg --skill architecture-evolution",{"tool":68,"command":69},"pnpm","pnpm dlx skills add jmagly\u002Faiwg --skill architecture-evolution","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fcodex-sdlc\u002Fskills\u002Farchitecture-evolution\u002FSKILL.md",true,[],[74,102,125,131,138,152],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":81,"publishedAt":41},"01M70QA0BSYJ49EES9V4RE8QH1","host-hardening","Read-only system hardening baseline and plan-first host hardening recommendations for SSH, Docker bind addresses, firewall persistence, datastores, exporters and audit retention.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[80],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101],"host","host hardening","hardening","read","re","recommendations","remediation","plan","port","verification","Bash","access","only","retention","audit","never","firewall","bind","secrets","request",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":112,"publishedAt":41},"01M70PNT2Z4HMZPRBTAF6073NN","exposure-analysis","Read-only firewall analysis and effective host exposure reconstruction for Docker published ports, UFW bypass, stale rules, CDN scope, IPv6 asymmetry and external probe allowlists.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fforensics\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[108,111],{"categoryNo":109,"categoryName":110,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[113,27,114,85,115,90,116,117,92,118,82,119,94,120,121,97,98,122,123,124],"exposure analysis","unknown","credentials","collection","ufw","ports","internet","local","scope","reconstruction","operator","write",{"skillNo":126,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":130,"publishedAt":41},"01M70P8QATMPKA78E4FT5D2TNA","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[129],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[84,82,83,93,85,101,88,87,96,89,90,91,92,100,94,95,86,97,98,99],{"skillNo":132,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":137,"publishedAt":41},"01M70NMPVJ5H0JH131P60FW4R8","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[135,136],{"categoryNo":109,"categoryName":110,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[27,113,97,115,90,116,92,114,82,119,94,120,121,85,98,118,117,122,123,124],{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":145,"publishedAt":41},"01M6CB4DDR0B4NNCFK7ZK7449H","fixture-skill","Exercise rule delivery.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Frule-delivery\u002Fskills\u002Ffixture-skill\u002FSKILL.md",[144],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[146,147,148,149,150,151],"fixture skill","fixture","rule","delivery","true","exercise",{"skillNo":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":159,"publishedAt":41},"01M6CB4AVK1W76MFMPP0JP32CJ","pi-local","Pi-local duplicate-precedence fixture.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fproviders\u002Fpi\u002Fproject\u002F.pi\u002Fskills\u002Fpi-local\u002FSKILL.md",[158],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[160,161,120,162,147],"pi","pi local","duplicate"]