[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CAC9WXQJDTTFKFX13TPC1T":3,"skill-same:01M6CAC9WXQJDTTFKFX13TPC1T":81},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":80},"01M6CAC9WXQJDTTFKFX13TPC1T","flow-change-control",null,"Orchestrate change control workflow with baseline management, impact assessment, CCB review, and communication","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\u002Fsdlc\u002Fskills\u002Fflow-change-control\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,41,42,43],"flow","flow change control","change","control","change control","true","sonnet","impact","project","coding","write","read","directory","communication","text","review","workflow","orchestration","assessment","orchestrate","2026-11-10 10:12:30",false,"---\nnamespace: aiwg\nname: flow-change-control\nplatforms: [all]\ndescription: Orchestrate change control workflow with baseline management, impact assessment, CCB review, and communication\ncommandHint:\n  argumentHint: '[change-type] [change-id] [project-directory] [--guidance \"text\"] [--interactive]'\n  allowedTools: 'Task, Read, Write, Glob, TodoWrite'\n  model: sonnet\n  category: sdlc-orchestration\n  orchestration: true\n  modelRole: coding\n  modelTier: standard\n---\n\n> **Declarative Flow (#1539):** This flow's orchestration is now also expressed as a\n> declarative YAML Flow at `flows\u002Fflow-change-control.playbook.yaml` (source of truth for the step\n> sequence + gates). This SKILL.md remains the discoverable trigger surface and prose\n> reference. See epic #1534.\n\n# Change Control Orchestration Flow\n\n**You are the Change Control Orchestrator** for managing formal change requests through assessment, approval, and implementation.\n\n## Your Role\n\n**You orchestrate multi-agent workflows. You do NOT execute bash scripts.**\n\nWhen the user requests change control (via natural language or explicit command):\n\n1. **Interpret the request** and confirm understanding\n2. **Read this template** as your orchestration guide\n3. **Extract agent assignments** and workflow steps\n4. **Delegate agents with the current provider-native orchestration mechanism** in the correct sequence\n5. **Synthesize results** and finalize artifacts\n6. **Report completion** with change status\n\n## Change Control Overview\n\n**Purpose**: Manage changes to project baselines through formal control process\n\n**Key Activities**:\n- Baseline identification and management\n- Change impact assessment across all dimensions\n- Change Control Board (CCB) review and approval\n- Baseline updates and version control\n- Stakeholder communication\n\n**Success Criteria**:\n- All changes formally documented\n- Impact assessed across scope, schedule, cost, quality, risk\n- CCB decision recorded with rationale\n- Baselines updated and versioned\n- Stakeholders notified appropriately\n\n## Natural Language Triggers\n\nUsers may say:\n- \"Submit change request for {change}\"\n- \"Process change request {id}\"\n- \"Change control for {feature\u002Frequirement\u002Farchitecture}\"\n- \"Review change request\"\n- \"CCB review needed\"\n- \"Assess impact of {change}\"\n- \"Update baseline for {change}\"\n\nYou recognize these as requests for this orchestration flow.\n\n## Parameter Handling\n\n### Change Types\n\nRecognize and categorize:\n- **scope**: Feature additions, requirement changes, functionality modifications\n- **schedule**: Deadline shifts, milestone adjustments, timeline changes\n- **resource**: Team changes, budget adjustments, tool changes\n- **technical**: Architecture changes, technology stack updates, design changes\n- **process**: Methodology changes, workflow updates, tool adoption\n- **risk**: Risk-driven changes, mitigation implementations, contingency activation\n\n### --guidance Parameter\n\n**Purpose**: User provides context to prioritize change assessment\n\n**Examples**:\n```\n--guidance \"Critical customer requirement, fast-track approval needed\"\n--guidance \"Budget impact analysis critical, cost overrun risk\"\n--guidance \"Security implications, need thorough security review\"\n--guidance \"Breaking change, requires migration strategy\"\n```\n\n**How to Apply**:\n- Parse for urgency indicators (critical, emergency, fast-track)\n- Identify focus areas (security, performance, cost, compliance)\n- Adjust CCB composition (add specialist reviewers)\n- Modify assessment depth (comprehensive vs. streamlined)\n\n### --interactive Parameter\n\n**Purpose**: You ask strategic questions about the change\n\n**Questions to Ask** (if --interactive):\n```\nI'll ask 6 strategic questions to understand this change request:\n\nQ1: What triggered this change request?\n    (e.g., customer request, defect discovery, risk mitigation, opportunity)\n\nQ2: What's the urgency level?\n    (Helps determine priority: P0-Critical, P1-High, P2-Medium, P3-Low)\n\nQ3: What's your estimated impact scope?\n    (Small: 1-2 components, Medium: 3-5 components, Large: system-wide)\n\nQ4: Are there any compliance or regulatory implications?\n    (Affects review requirements and approval chain)\n\nQ5: What's your rollback confidence if this change fails?\n    (High: easy rollback, Medium: some risk, Low: difficult to reverse)\n\nQ6: What's your change control maturity?\n    (Ad-hoc, Defined process, Mature CCB, Automated workflows)\n\nBased on your answers, I'll adjust:\n- Change priority and urgency\n- CCB reviewer composition\n- Impact assessment depth\n- Communication strategy\n```\n\n## Artifacts to Generate\n\n**Primary Deliverables**:\n- **Change Request**: Formal request documentation → `.aiwg\u002Fdecisions\u002Fchange-requests\u002FCR-{id}.md`\n- **Impact Assessment**: Multi-dimensional analysis → `.aiwg\u002Fdecisions\u002Fimpact-assessments\u002FIA-{id}.md`\n- **CCB Decision Record**: Meeting notes and decision → `.aiwg\u002Fdecisions\u002Fccb-meetings\u002FCCB-{date}.md`\n- **Baseline Update Log**: Version control records → `.aiwg\u002Fdecisions\u002Fbaseline-updates\u002FBU-{id}.md`\n- **Stakeholder Notification**: Communication records → `.aiwg\u002Fdecisions\u002Fcommunications\u002FCOMM-{id}.md`\n- **Change Implementation Tracking**: Work items and status → `.aiwg\u002Fdecisions\u002Fimplementation\u002FIMPL-{id}.md`\n\n## Multi-Agent Orchestration Workflow\n\n### Step 1: Document Change Request\n\n**Purpose**: Formally capture change request with business justification\n\n**Your Actions**:\n\n1. **Initialize Change Request**:\n   ```\n   # Generate change ID if not provided\n   If no change-id provided:\n     change-id = \"CR-$(date +%Y%m%d)-{sequential}\"\n\n   Create directories:\n   - .aiwg\u002Fdecisions\u002Fchange-requests\u002F\n   - .aiwg\u002Fdecisions\u002Fimpact-assessments\u002F\n   - .aiwg\u002Fdecisions\u002Fccb-meetings\u002F\n   ```\n\n2. **Launch Change Documentation Agent**:\n   ```\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Document formal change request\",\n       prompt=\"\"\"\n       Create change request for: {change-description}\n       Change Type: {scope|schedule|resource|technical|process|risk}\n\n       Document using template from agentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Ftemplates\u002Fconfiguration\u002Fchange-request-card.md:\n\n       1. Change Request Summary\n          - Change ID: {change-id}\n          - Requestor: {name\u002Frole}\n          - Date Submitted: {current-date}\n          - Change Type: {type}\n          - Priority: {P0|P1|P2|P3} (based on urgency)\n\n       2. Business Justification\n          - Why is this change needed?\n          - What problem does it solve or opportunity does it capture?\n          - What happens if we don't make this change?\n\n       3. Current State\n          - Describe the system\u002Fprocess as it exists today\n          - Identify specific artifacts affected\n          - Document current baseline version\n\n       4. Desired State\n          - Describe the system\u002Fprocess after the change\n          - Define success criteria\n          - Specify acceptance criteria\n\n       5. Proposed Approach\n          - High-level implementation strategy\n          - Alternative approaches considered\n          - Recommended approach with rationale\n\n       Save to: .aiwg\u002Fdecisions\u002Fchange-requests\u002FCR-{id}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n✓ Change request initialized: CR-{id}\n⏳ Documenting change request...\n✓ Change request documented: .aiwg\u002Fdecisions\u002Fchange-requests\u002FCR-{id}.md\n```\n\n### Step 2: Conduct Impact Assessment\n\n**Purpose**: Analyze change impact across all project dimensions\n\n**Your Actions**:\n\n1. **Read Project Context**:\n   ```\n   Read key artifacts:\n   - .aiwg\u002Farchitecture\u002Fsoftware-architecture-doc.md (if exists)\n   - .aiwg\u002Fplanning\u002Fproject-plan.md (if exists)\n   - .aiwg\u002Frisks\u002Frisk-list.md\n   - .aiwg\u002Frequirements\u002F*.md (affected requirements)\n   ```\n\n2. **Launch Parallel Impact Assessment Agents**:\n   ```\n   # Agent 1: Scope and Requirements Impact\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Assess scope and requirements impact\",\n       prompt=\"\"\"\n       Analyze change request: .aiwg\u002Fdecisions\u002Fchange-requests\u002FCR-{id}.md\n\n       Assess Scope Impact:\n       - Which requirements are affected? (list requirement IDs)\n       - Which features are impacted? (list features)\n       - Does this change project vision or objectives?\n       - What's the ripple effect on dependent features?\n\n       Categorize impact:\n       - Low: Minor change to existing feature (\u003C5% scope)\n       - Medium: New feature or significant change (5-15% scope)\n       - High: Changes to core functionality (>15% scope)\n\n       Document findings in impact assessment format.\n       Save to: .aiwg\u002Fworking\u002Fchange-control\u002Fscope-impact-{id}.md\n       \"\"\"\n   )\n\n   # Agent 2: Schedule and Cost Impact\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Assess schedule and cost impact\",\n       prompt=\"\"\"\n       Analyze change request: .aiwg\u002Fdecisions\u002Fchange-requests\u002FCR-{id}.md\n\n       Assess Schedule Impact:\n       - How many additional days\u002Fweeks required?\n       - Does this affect critical path?\n       - Which milestones are at risk?\n       - Can this be absorbed in current iteration?\n\n       Assess Cost Impact:\n       - Labor cost (additional hours × rate)\n       - Infrastructure\u002Ftool costs\n       - License costs (if any)\n       - Is this within contingency budget?\n\n       Categorize combined impact:\n       - Low: \u003C5% schedule\u002Fbudget impact, no milestone changes\n       - Medium: 5-15% impact, minor milestone adjustment\n       - High: >15% impact, major milestone shifts\n\n       Save to: .aiwg\u002Fworking\u002Fchange-control\u002Fschedule-cost-impact-{id}.md\n       \"\"\"\n   )\n\n   # Agent 3: Technical and Quality Impact\n   Task(\n       subagent_type=\"architecture-designer\",\n       description=\"Assess technical and quality impact\",\n       prompt=\"\"\"\n       Analyze change request: .aiwg\u002Fdecisions\u002Fchange-requests\u002FCR-{id}.md\n\n       Assess Technical Impact:\n       - Which components need modification?\n       - Does this affect architecture decisions?\n       - What's the integration complexity?\n       - Does this introduce technical debt?\n\n       Assess Quality Impact:\n       - Test coverage impact (new tests needed?)\n       - Performance implications\n       - Security implications\n       - Maintainability concerns\n\n       Categorize impact:\n       - Low: No architecture changes, minimal quality impact\n       - Medium: Component changes, temporary quality impact\n       - High: Architecture changes, significant quality concerns\n\n       Save to: .aiwg\u002Fworking\u002Fchange-control\u002Ftechnical-quality-impact-{id}.md\n       \"\"\"\n   )\n\n   # Agent 4: Risk Impact\n   Task(\n       subagent_type=\"risk-manager\",\n       description=\"Assess risk impact\",\n       prompt=\"\"\"\n       Analyze change request: .aiwg\u002Fdecisions\u002Fchange-requests\u002FCR-{id}.md\n       Read current risks: .aiwg\u002Frisks\u002Frisk-list.md\n\n       Assess Risk Impact:\n       - What new risks does this change introduce?\n       - Does this mitigate any existing risks?\n       - How does this affect risk severity\u002Flikelihood?\n       - What's the rollback risk if change fails?\n\n       Document:\n       - New risks introduced (with severity)\n       - Existing risks mitigated\n       - Risk severity changes\n       - Overall risk posture change\n\n       Categorize impact:\n       - Low: No new High\u002FCritical risks\n       - Medium: New Medium risks or increased severity\n       - High: New Show Stopper risks or multiple High risks\n\n       Save to: .aiwg\u002Fworking\u002Fchange-control\u002Frisk-impact-{id}.md\n       \"\"\"\n   )\n   ```\n\n3. **Synthesize Impact Assessment**:\n   ```\n   Task(\n       subagent_type=\"change-analyst\",\n       description=\"Synthesize comprehensive impact assessment\",\n       prompt=\"\"\"\n       Read all impact analyses:\n       - .aiwg\u002Fworking\u002Fchange-control\u002Fscope-impact-{id}.md\n       - .aiwg\u002Fworking\u002Fchange-control\u002Fschedule-cost-impact-{id}.md\n       - .aiwg\u002Fworking\u002Fchange-control\u002Ftechnical-quality-impact-{id}.md\n       - .aiwg\u002Fworking\u002Fchange-control\u002Frisk-impact-{id}.md\n\n       Create comprehensive Impact Assessment using template:\n       agentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Ftemplates\u002Fconfiguration\u002Fchange-request-card.md\n\n       Structure:\n       1. Executive Summary\n          - Overall impact rating: Low | Medium | High\n          - Recommendation: APPROVE | REJECT | DEFER\n\n       2. Detailed Impact Analysis\n          - Scope Impact: {summary with rating}\n          - Schedule Impact: {summary with rating}\n          - Cost Impact: {summary with rating}\n          - Quality Impact: {summary with rating}\n          - Risk Impact: {summary with rating}\n\n       3. Affected Artifacts\n          - List all documents\u002Fcode\u002Ftests affected\n          - Current baseline versions\n          - Proposed new versions\n\n       4. Stakeholder Impact\n          - Who is affected by this change\n          - Communication requirements\n\n       5. Implementation Considerations\n          - Prerequisites\n          - Dependencies\n          - Rollback strategy\n\n       6. Recommendation\n          - Clear APPROVE\u002FREJECT\u002FDEFER recommendation\n          - Rationale for recommendation\n          - Conditions (if conditional approval)\n\n       Save to: .aiwg\u002Fdecisions\u002Fimpact-assessments\u002FIA-{id}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Conducting impact assessment (4 parallel agents)...\n  ✓ Scope impact: MEDIUM (3 requirements affected)\n  ✓ Schedule impact: LOW (\u003C5% impact, no milestone changes)\n  ✓ Cost impact: LOW (within contingency)\n  ✓ Quality impact: MEDIUM (new tests required)\n  ✓ Risk impact: LOW (no new high risks)\n✓ Impact assessment complete: .aiwg\u002Fdecisions\u002Fimpact-assessments\u002FIA-{id}.md\nOverall Impact: MEDIUM | Recommendation: APPROVE\n```\n\n### Step 3: CCB Review and Decision\n\n**Purpose**: Present to Change Control Board for formal decision\n\n**Your Actions**:\n\n1. **Determine CCB Composition**:\n   ```\n   Based on change type and impact, determine reviewers:\n\n   Core CCB (always):\n   - Executive Sponsor (budget authority)\n   - Product Owner (scope authority)\n   - Software Architect (technical authority)\n   - Project Manager (schedule authority)\n\n   Extended CCB (conditionally):\n   - Security Architect (if security impact)\n   - Legal\u002FCompliance (if regulatory impact)\n   - Customer Representative (if customer-facing)\n   - DevOps Lead (if deployment impact)\n   ```\n\n2. **Launch CCB Review Agents** (parallel):\n   ```\n   # For each CCB member, launch review:\n\n   Task(\n       subagent_type=\"executive-sponsor\",\n       description=\"CCB review: Business and budget perspective\",\n       prompt=\"\"\"\n       Review change request and impact assessment:\n       - .aiwg\u002Fdecisions\u002Fchange-requests\u002FCR-{id}.md\n       - .aiwg\u002Fdecisions\u002Fimpact-assessments\u002FIA-{id}.md\n\n       Evaluate from executive perspective:\n       - Business value vs. cost\n       - Strategic alignment\n       - Budget availability\n       - Risk tolerance\n\n       Provide vote: APPROVE | REJECT | DEFER | ABSTAIN\n       Provide rationale for decision\n\n       Save review to: .aiwg\u002Fworking\u002Fccb-reviews\u002Fexecutive-sponsor-{id}.md\n       \"\"\"\n   )\n\n   Task(\n       subagent_type=\"product-owner\",\n       description=\"CCB review: Product and scope perspective\",\n       prompt=\"\"\"\n       Review change request and impact assessment\n\n       Evaluate from product perspective:\n       - Value to users\u002Fcustomers\n       - Scope creep concerns\n       - Feature priority\n       - Market timing\n\n       Provide vote: APPROVE | REJECT | DEFER | ABSTAIN\n       Provide rationale\n\n       Save to: .aiwg\u002Fworking\u002Fccb-reviews\u002Fproduct-owner-{id}.md\n       \"\"\"\n   )\n\n   Task(\n       subagent_type=\"architecture-designer\",\n       description=\"CCB review: Technical feasibility perspective\",\n       prompt=\"\"\"\n       Review change request and impact assessment\n\n       Evaluate from architecture perspective:\n       - Technical feasibility\n       - Architecture integrity\n       - Technical debt implications\n       - Integration complexity\n\n       Provide vote: APPROVE | REJECT | DEFER | ABSTAIN\n       Provide rationale\n\n       Save to: .aiwg\u002Fworking\u002Fccb-reviews\u002Farchitect-{id}.md\n       \"\"\"\n   )\n\n   # Add conditional reviewers based on guidance\u002Fimpact\n   ```\n\n3. **Synthesize CCB Decision**:\n   ```\n   Task(\n       subagent_type=\"ccb-coordinator\",\n       description=\"Document CCB decision\",\n       prompt=\"\"\"\n       Read all CCB reviews from .aiwg\u002Fworking\u002Fccb-reviews\u002F*-{id}.md\n\n       Tally votes:\n       - APPROVE: {count}\n       - REJECT: {count}\n       - DEFER: {count}\n       - ABSTAIN: {count}\n\n       Determine decision based on voting rules:\n       - Majority APPROVE → APPROVED\n       - Any REJECT with veto power → REJECTED\n       - Split decision → DEFERRED for more information\n\n       Document CCB Meeting using template:\n       CCB meeting fields in this skill\n\n       Include:\n       1. Meeting Details\n          - Date\u002FTime: {current-timestamp}\n          - Attendees: {CCB members}\n          - Quorum: YES (if majority present)\n\n       2. Change Request Review\n          - CR ID: {id}\n          - Presenter: Change Analyst\n          - Discussion summary\n\n       3. Voting Record\n          - Individual votes with rationale\n          - Final tally\n\n       4. Decision\n          - APPROVED | REJECTED | DEFERRED\n          - Decision rationale\n          - Conditions (if conditional approval)\n\n       5. Action Items\n          - If approved: Implementation timeline\n          - If rejected: Notification plan\n          - If deferred: Information needed\n\n       Save to: .aiwg\u002Fdecisions\u002Fccb-meetings\u002FCCB-{date}-CR-{id}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ CCB review in progress...\n  ✓ Executive Sponsor: APPROVE (strategic value outweighs cost)\n  ✓ Product Owner: APPROVE (customer requested feature)\n  ✓ Software Architect: CONDITIONAL (requires ADR for API change)\n  ✓ Project Manager: APPROVE (can fit in current iteration)\n✓ CCB Decision: APPROVED (3 approve, 1 conditional)\nConditions: Create ADR for API versioning strategy\n```\n\n### Step 4: Update Baseline and Documentation\n\n**Purpose**: Update project baselines with approved changes\n\n**Your Actions**:\n\n1. **Identify Affected Baselines**:\n   ```\n   Task(\n       subagent_type=\"configuration-manager\",\n       description=\"Identify baselines to update\",\n       prompt=\"\"\"\n       Based on approved change CR-{id}, identify:\n\n       1. Affected Baselines:\n          - Functional Baseline (requirements, design)\n          - Product Baseline (code, tests)\n          - Project Baseline (schedule, budget)\n\n       2. Current Versions:\n          - Document current version tags\n          - Identify last baseline date\n\n       3. Update Scope:\n          - List specific artifacts to update\n          - Determine new version numbers\n\n       Create baseline update plan.\n       Save to: .aiwg\u002Fworking\u002Fbaseline-plan-{id}.md\n       \"\"\"\n   )\n   ```\n\n2. **Update Artifacts** (parallel where possible):\n   ```\n   # Based on change type, update relevant artifacts\n\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Update requirements baseline\",\n       prompt=\"\"\"\n       For approved change CR-{id}:\n\n       Update affected requirements:\n       - Modify existing requirements as needed\n       - Add new requirements if applicable\n       - Update requirement IDs and traceability\n       - Update version numbers\n\n       Document changes in each file with:\n       \u003C!-- Change CR-{id}: Description of change -->\n\n       Save updated requirements to original locations.\n       Create change summary: .aiwg\u002Fworking\u002Frequirements-changes-{id}.md\n       \"\"\"\n   )\n\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Update project plan\",\n       prompt=\"\"\"\n       For approved change CR-{id}:\n\n       Update project artifacts:\n       - Adjust schedule if needed\n       - Update budget allocations\n       - Modify resource assignments\n       - Update risk register\n\n       Document baseline version change.\n       Save updates to original locations.\n       \"\"\"\n   )\n   ```\n\n3. **Create Baseline Update Log**:\n   ```\n   Task(\n       subagent_type=\"configuration-manager\",\n       description=\"Document baseline update\",\n       prompt=\"\"\"\n       Create baseline update log using template:\n       baseline update fields in this skill\n\n       Document:\n       1. Change Authorization\n          - CR ID: {id}\n          - CCB Approval Date: {date}\n          - Implementer: {agent\u002Fperson}\n\n       2. Baseline Updates\n          - Previous Version: {old-version}\n          - New Version: {new-version}\n          - Artifacts Updated: {list}\n\n       3. Version Control\n          - Git Tag: baseline-{new-version}\n          - Commit Hash: {if applicable}\n          - Branch: {if applicable}\n\n       4. Validation\n          - Updates verified: YES\n          - Traceability maintained: YES\n          - Tests updated: YES\u002FNO\u002FNA\n\n       Save to: .aiwg\u002Fdecisions\u002Fbaseline-updates\u002FBU-{id}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Updating baselines...\n  ✓ Requirements baseline updated (v1.1 → v1.2)\n  ✓ Project plan updated (schedule adjusted)\n  ✓ Risk register updated (new risk added)\n✓ Baseline update complete: v1.2\n✓ Update log: .aiwg\u002Fdecisions\u002Fbaseline-updates\u002FBU-{id}.md\n```\n\n### Step 5: Communicate Change Decision\n\n**Purpose**: Notify all stakeholders of change decision and impacts\n\n**Your Actions**:\n\n1. **Identify Stakeholders**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Identify stakeholders to notify\",\n       prompt=\"\"\"\n       Based on change CR-{id} and impact assessment:\n\n       Identify stakeholder groups:\n       1. Direct Impact (must notify immediately):\n          - Change requestor\n          - Teams working on affected components\n          - Downstream dependencies\n\n       2. Indirect Impact (should notify):\n          - Adjacent teams\n          - QA\u002FTest teams\n          - Operations\u002FDevOps\n\n       3. Informational (nice to notify):\n          - Broader development team\n          - Management chain\n          - Customers (if applicable)\n\n       Determine notification priority and channel for each group.\n       Save to: .aiwg\u002Fworking\u002Fstakeholder-list-{id}.md\n       \"\"\"\n   )\n   ```\n\n2. **Create Stakeholder Communications**:\n   ```\n   Task(\n       subagent_type=\"technical-writer\",\n       description=\"Draft stakeholder notifications\",\n       prompt=\"\"\"\n       Create notifications for change CR-{id} decision: {APPROVED|REJECTED|DEFERRED}\n\n       For each stakeholder group, create appropriate message:\n\n       1. Change Requestor Notification:\n          - Decision and rationale\n          - Next steps\n          - Timeline (if approved)\n          - Contact for questions\n\n       2. Development Team Notification:\n          - What's changing\n          - When it's changing\n          - Impact on their work\n          - Updated artifacts\u002Fbaselines\n\n       3. Management Summary:\n          - Decision summary\n          - Business impact\n          - Schedule\u002Fcost impact\n          - Risk considerations\n\n       Use the inline format: stakeholder notification fields in this skill\n\n       Save to: .aiwg\u002Fdecisions\u002Fcommunications\u002FCOMM-{id}-{audience}.md\n       \"\"\"\n   )\n   ```\n\n3. **Track Communication Delivery**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Document communication delivery\",\n       prompt=\"\"\"\n       Track stakeholder notifications for CR-{id}:\n\n       Create communication log:\n       1. Stakeholder: {name\u002Fgroup}\n       2. Notification sent: {timestamp}\n       3. Channel: {email\u002Fslack\u002Fmeeting}\n       4. Acknowledgment: {received\u002Fpending}\n       5. Follow-up needed: {yes\u002Fno}\n\n       Save to: .aiwg\u002Fdecisions\u002Fcommunications\u002FCOMM-{id}-log.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Notifying stakeholders...\n  ✓ Change requestor notified (acknowledged)\n  ✓ Development team notified (3 teams)\n  ✓ QA team notified\n  ✓ Management briefed\n✓ Stakeholder communication complete\n✓ Communication log: .aiwg\u002Fdecisions\u002Fcommunications\u002FCOMM-{id}-log.md\n```\n\n### Step 6: Track Change Implementation\n\n**Purpose**: Create work items and track implementation to completion\n\n**Your Actions**:\n\n1. **Create Implementation Work Items**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Create work items for change implementation\",\n       prompt=\"\"\"\n       For approved change CR-{id}, create work items:\n\n       Based on impact assessment and change scope:\n       1. Break down change into discrete tasks\n       2. Assign to appropriate teams\u002Findividuals\n       3. Set priorities and dependencies\n       4. Define acceptance criteria\n       5. Estimate effort\n\n       For each work item, document:\n       - WI-{id}: {title}\n       - Assigned to: {team\u002Fperson}\n       - Priority: {P0\u002FP1\u002FP2\u002FP3}\n       - Effort: {hours\u002Fdays}\n       - Dependencies: {other WIs}\n       - Acceptance Criteria: {specific, measurable}\n\n       Save to: .aiwg\u002Fdecisions\u002Fimplementation\u002Fwork-items-CR-{id}.md\n       \"\"\"\n   )\n   ```\n\n2. **Create Implementation Tracking**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Set up implementation tracking\",\n       prompt=\"\"\"\n       Create implementation tracking for CR-{id}:\n\n       Structure:\n       1. Implementation Plan\n          - Start Date: {date}\n          - Target Completion: {date}\n          - Implementation Lead: {name}\n\n       2. Work Items Status\n          - Total: {count}\n          - Not Started: {count}\n          - In Progress: {count}\n          - Completed: {count}\n          - Blocked: {count}\n\n       3. Validation Plan\n          - How to verify change is successful\n          - Test cases to run\n          - Metrics to measure\n\n       4. Rollback Plan\n          - Rollback triggers\n          - Rollback procedure\n          - Rollback owner\n\n       Save to: .aiwg\u002Fdecisions\u002Fimplementation\u002FIMPL-{id}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Setting up implementation tracking...\n  ✓ 5 work items created\n  ✓ Implementation plan defined (5-day timeline)\n  ✓ Validation criteria established\n  ✓ Rollback plan documented\n✓ Implementation tracking: .aiwg\u002Fdecisions\u002Fimplementation\u002FIMPL-{id}.md\n```\n\n### Step 7: Generate Change Control Report\n\n**Purpose**: Create comprehensive report of change control process\n\n**Your Actions**:\n\n```\nTask(\n    subagent_type=\"change-analyst\",\n    description=\"Generate comprehensive change control report\",\n    prompt=\"\"\"\n    Synthesize all change control artifacts for CR-{id}:\n\n    Read:\n    - .aiwg\u002Fdecisions\u002Fchange-requests\u002FCR-{id}.md\n    - .aiwg\u002Fdecisions\u002Fimpact-assessments\u002FIA-{id}.md\n    - .aiwg\u002Fdecisions\u002Fccb-meetings\u002FCCB-*-CR-{id}.md\n    - .aiwg\u002Fdecisions\u002Fbaseline-updates\u002FBU-{id}.md\n    - .aiwg\u002Fdecisions\u002Fcommunications\u002FCOMM-{id}-log.md\n    - .aiwg\u002Fdecisions\u002Fimplementation\u002FIMPL-{id}.md\n\n    Generate Change Control Report:\n\n    # Change Control Report - CR-{id}\n\n    ## Executive Summary\n    - Change ID: CR-{id}\n    - Type: {scope|schedule|resource|technical|process|risk}\n    - Priority: {P0|P1|P2|P3}\n    - Status: {APPROVED|REJECTED|DEFERRED|IMPLEMENTED}\n    - Decision Date: {date}\n\n    ## Change Request\n    - Requestor: {name\u002Frole}\n    - Justification: {summary}\n    - Current State: {brief}\n    - Desired State: {brief}\n\n    ## Impact Assessment\n    - Overall Impact: {LOW|MEDIUM|HIGH}\n    - Scope: {rating} - {summary}\n    - Schedule: {rating} - {days\u002Fweeks impact}\n    - Cost: {rating} - ${amount}\n    - Quality: {rating} - {summary}\n    - Risk: {rating} - {new risks, mitigated risks}\n\n    ## CCB Decision\n    - Meeting Date: {date}\n    - Attendees: {list}\n    - Vote: {tally}\n    - Decision: {APPROVED|REJECTED|DEFERRED}\n    - Rationale: {summary}\n    - Conditions: {if any}\n\n    ## Baseline Updates\n    - Previous Version: {version}\n    - New Version: {version}\n    - Artifacts Updated: {count}\n    - Update Date: {date}\n\n    ## Stakeholder Communication\n    - Notifications Sent: {count}\n    - Key Stakeholders: {list}\n    - Communication Status: COMPLETE\n\n    ## Implementation Status\n    - Work Items: {total count}\n    - Progress: {percentage}%\n    - Target Completion: {date}\n    - Current Status: {NOT_STARTED|IN_PROGRESS|COMPLETED|BLOCKED}\n\n    ## Lessons Learned\n    - What went well\n    - What could improve\n    - Recommendations for future changes\n\n    ## Appendices\n    - Links to all related documents\n    - Audit trail\n\n    Save to: .aiwg\u002Freports\u002Fchange-control-report-CR-{id}.md\n    \"\"\"\n)\n```\n\n**Final Communication**:\n```\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nChange Control Process Complete\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nChange ID: CR-{id}\nDecision: APPROVED\nImpact: MEDIUM\nImplementation: IN PROGRESS\n\nArtifacts Generated:\n✓ Change Request: .aiwg\u002Fdecisions\u002Fchange-requests\u002FCR-{id}.md\n✓ Impact Assessment: .aiwg\u002Fdecisions\u002Fimpact-assessments\u002FIA-{id}.md\n✓ CCB Decision: .aiwg\u002Fdecisions\u002Fccb-meetings\u002FCCB-{date}-CR-{id}.md\n✓ Baseline Update: .aiwg\u002Fdecisions\u002Fbaseline-updates\u002FBU-{id}.md\n✓ Communications: .aiwg\u002Fdecisions\u002Fcommunications\u002FCOMM-{id}-*.md\n✓ Implementation Plan: .aiwg\u002Fdecisions\u002Fimplementation\u002FIMPL-{id}.md\n✓ Final Report: .aiwg\u002Freports\u002Fchange-control-report-CR-{id}.md\n\nNext Steps:\n1. Monitor implementation progress\n2. Validate acceptance criteria\n3. Close change request when complete\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n```\n\n## Quality Gates\n\nBefore marking workflow complete, verify:\n- [ ] Change request formally documented\n- [ ] Impact assessment covers all dimensions\n- [ ] CCB quorum achieved and decision recorded\n- [ ] Baseline updated with version control\n- [ ] All stakeholders notified appropriately\n- [ ] Implementation tracking established\n- [ ] Comprehensive report generated\n\n## Success Criteria\n\nThis orchestration succeeds when:\n- [ ] Change request has clear business justification\n- [ ] Impact assessed across scope, schedule, cost, quality, risk\n- [ ] CCB review conducted with quorum\n- [ ] Decision recorded with rationale\n- [ ] If approved: Baselines updated and versioned\n- [ ] If rejected: Requestor notified with reasoning\n- [ ] If deferred: Follow-up scheduled\n- [ ] Stakeholders appropriately informed\n- [ ] Implementation plan created (if approved)\n- [ ] Complete audit trail maintained\n\n## Error Handling\n\n**If No Quorum**:\n```\n⚠️ CCB quorum not met ({present}\u002F{required})\n\nCannot proceed with decision.\n\nActions:\n1. Reschedule CCB meeting\n2. For P0-Critical: Invoke emergency process\n3. Notify change requestor of delay\n\nNext meeting scheduled: {date\u002Ftime}\n```\n\n**If Impact Too High**:\n```\n⚠️ Change impact exceeds thresholds\n\nImpact Summary:\n- Scope: HIGH (>15% change)\n- Cost: HIGH (>15% budget impact)\n- Schedule: HIGH (milestone at risk)\n\nRecommendation: REJECT or significant re-scoping\n\nEscalating to Executive Sponsor...\n```\n\n**If Baseline Conflict**:\n```\n❌ Baseline update conflict detected\n\nConflict: Another change (CR-{other-id}) modified same artifacts\n\nResolution needed:\n1. Analyze conflict scope\n2. Determine precedence\n3. Merge changes if compatible\n4. Defer one change if incompatible\n\nEscalating to CCB...\n```\n\n## References\n\n**Templates** (via $AIWG_ROOT):\n- Change Request: `agentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Ftemplates\u002Fconfiguration\u002Fchange-request-card.md`\n- Impact Assessment: `agentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Ftemplates\u002Fconfiguration\u002Fchange-request-card.md`\n- CCB Meeting Notes: CCB meeting fields in this skill\n- Baseline Log: baseline update fields in this skill\n- Stakeholder Communication: stakeholder notification fields in this skill\n- Work Package Card: `templates\u002Fmanagement\u002Fwork-package-card.md`\n\n**Related Flows**:\n- Gate Checks: `flow-gate-check.md`\n- Risk Management: `flow-risk-management-cycle.md`\n- Architecture Evolution: `flow-architecture-evolution.md`\n- Requirements Management: `flow-requirements-baseline.md`\n\n**External References**:\n- PMBOK Guide Change Control Process\n- Configuration Management Best Practices","> **Declarative Flow (#1539):** This flow's orchestration is now also expressed as a\n> declarative YAML Flow at `flows\u002Fflow-change-control.playbook.yaml` (source of truth for the step\n> sequence + gates). This SKILL.md remains the discoverable trigger surface and prose\n> reference. See epic #1534.\n\n# Change Control Orchestration Flow\n\n**You are the Change Control Orchestrator** for managing formal change requests through assessment, approval, and implementation.\n\n## Your Role\n\n**You orchestrate multi-agent workflows. You do NOT execute bash scripts.**\n\nWhen the user requests change control (via natural language or explicit command):\n\n1. **Interpret the request** and confirm understanding\n2. **Read this template** as your orchestration guide\n3. **Extract agent assignments** and workflow steps\n4. **Delegate agents with the current provider-native orchestration mechanism** in the correct sequence\n5. **Synthesize results** and finalize artifacts\n6. **Report completion** with change status\n\n## Change Control Overview\n\n**Purpose**: Manage changes to project baselines through formal control process\n\n**Key Activities**:\n- Baseline identification and management\n- Change impact assessment across all dimensions\n- Change Control Board (CCB) review and approval\n- Baseline updates and version control\n- Stakeholder communication\n\n**Success Criteria**:\n- All changes formally documented\n- Impact assessed across scope, schedule, cost, quality, risk\n- CCB decision recorded with rationale\n- Baselines updated and versioned\n- Stakeholders notified appropriately\n\n## Natural Language Triggers\n\nUsers may say:\n- \"Submit change request for {change}\"\n- \"Process change request {id}\"\n- \"Change control for {feature\u002Frequirement\u002Farchitecture}\"\n- \"Review change request\"\n- \"CCB review needed\"\n- \"Assess impact of {change}\"\n- \"Update baseline for {change}\"\n\nYou recognize these as requests for this orchestration flow.\n\n## Parameter Handling\n\n### Change Types\n\nRecognize and categorize:\n- **scope**: Feature additions, requirement changes, functionality modifications\n- **schedule**: Deadline shifts, milestone adjustments, timeline changes\n- **resource**: Team changes, budget adjustments, tool changes\n- **technical**: Architecture changes, technology stack updates, design changes\n- **process**: Methodology changes, workflow updates, tool adoption\n- **risk**: Risk-driven changes, mitigation implementations, contingency activation\n\n### --guidance Parameter\n\n**Purpose**: User provides context to prioritize change assessment\n\n**Examples**:\n```\n--guidance \"Critical customer requirement, fast-track approval needed\"\n--guidance \"Budget impact analysis critical, cost overrun risk\"\n--guidance \"Security implications, need thorough security review\"\n--guidance \"Breaking change, requires migration strategy\"\n```\n\n**How to Apply**:\n- Parse for urgency indicators (critical, emergency, fast-track)\n- Identify focus areas (security, performance, cost, compliance)\n- Adjust CCB composition (add specialist reviewers)\n- Modify assessment depth (comprehensive vs. streamlined)\n\n### --interactive Parameter\n\n**Purpose**: You ask strategic questions about the change\n\n**Questions to Ask** (if --interactive):\n```\nI'll ask 6 strategic questions to understand this change request:\n\nQ1: What triggered this change request?\n    (e.g., customer request, defect discovery, risk mitigation, opportunity)\n\nQ2: What's the urgency level?\n    (Helps determine priority: P0-Critical, P1-High, P2-Medium, P3-Low)\n\nQ3: What's your estimated impact scope?\n    (Small: 1-2 components, Medium: 3-5 components, Large: system-wide)\n\nQ4: Are there any compliance or regulatory implications?\n    (Affects review requirements and approval chain)\n\nQ5: What's your rollback confidence if this change fails?\n    (High: easy rollback, Medium: some risk, Low: difficult to reverse)\n\nQ6: What's your change control maturity?\n    (Ad-hoc, Defined process, Mature CCB, Automated workflows)\n\nBased on your answers, I'll adjust:\n- Change priority and urgency\n- CCB reviewer composition\n- Impact assessment depth\n- Communication strategy\n```\n\n## Artifacts to Generate\n\n**Primary Deliverables**:\n- **Change Request**: Formal request documentation → `.aiwg\u002Fdecisions\u002Fchange-requests\u002FCR-{id}.md`\n- **Impact Assessment**: Multi-dimensional analysis → `.aiwg\u002Fdecisions\u002Fimpact-assessments\u002FIA-{id}.md`\n- **CCB Decision Record**: Meeting notes and decision → `.aiwg\u002Fdecisions\u002Fccb-meetings\u002FCCB-{date}.md`\n- **Baseline Update Log**: Version control records → `.aiwg\u002Fdecisions\u002Fbaseline-updates\u002FBU-{id}.md`\n- **Stakeholder Notification**: Communication records → `.aiwg\u002Fdecisions\u002Fcommunications\u002FCOMM-{id}.md`\n- **Change Implementation Tracking**: Work items and status → `.aiwg\u002Fdecisions\u002Fimplementation\u002FIMPL-{id}.md`\n\n## Multi-Agent Orchestration Workflow\n\n### Step 1: Document Change Request\n\n**Purpose**: Formally capture change request with business justification\n\n**Your Actions**:\n\n1. **Initialize Change Request**:\n   ```\n   # Generate change ID if not provided\n   If no change-id provided:\n     change-id = \"CR-$(date +%Y%m%d)-{sequential}\"\n\n   Create directories:\n   - .aiwg\u002Fdecisions\u002Fchange-requests\u002F\n   - .aiwg\u002Fdecisions\u002Fimpact-assessments\u002F\n   - .aiwg\u002Fdecisions\u002Fccb-meetings\u002F\n   ```\n\n2. **Launch Change Documentation Agent**:\n   ```\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Document formal change request\",\n       prompt=\"\"\"\n       Create change request for: {change-description}\n       Change Type: {scope|schedule|resource|technical|process|risk}\n\n       Document using template from agentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Ftemplates\u002Fconfiguration\u002Fchange-request-card.md:\n\n       1. Change Request Summary\n          - Change ID: {change-id}\n          - Requestor: {name\u002Frole}\n          - Date Submitted: {current-date}\n          - Change Type: {type}\n          - Priority: {P0|P1|P2|P3} (based on urgency)\n\n       2. Business Justification\n          - Why is this change needed?\n          - What problem does it solve or opportunity does it capture?\n          - What happens if we don't make this change?\n\n       3. Current State\n          - Describe the system\u002Fprocess as it exists today\n          - Identify specific artifacts affected\n          - Document current baseline version\n\n       4. Desired State\n          - Describe the system\u002Fprocess after the change\n          - Define success criteria\n          - Specify acceptance criteria\n\n       5. Proposed Approach\n          - High-level implementation strategy\n          - Alternative approaches considered\n          - Recommended approach with rationale\n\n       Save to: .aiwg\u002Fdecisions\u002Fchange-requests\u002FCR-{id}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n✓ Change request initialized: CR-{id}\n⏳ Documenting change request...\n✓ Change request documented: .aiwg\u002Fdecisions\u002Fchange-requests\u002FCR-{id}.md\n```\n\n### Step 2: Conduct Impact Assessment\n\n**Purpose**: Analyze change impact across all project dimensions\n\n**Your Actions**:\n\n1. **Read Project Context**:\n   ```\n   Read key artifacts:\n   - .aiwg\u002Farchitecture\u002Fsoftware-architecture-doc.md (if exists)\n   - .aiwg\u002Fplanning\u002Fproject-plan.md (if exists)\n   - .aiwg\u002Frisks\u002Frisk-list.md\n   - .aiwg\u002Frequirements\u002F*.md (affected requirements)\n   ```\n\n2. **Launch Parallel Impact Assessment Agents**:\n   ```\n   # Agent 1: Scope and Requirements Impact\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Assess scope and requirements impact\",\n       prompt=\"\"\"\n       Analyze change request: .aiwg\u002Fdecisions\u002Fchange-requests\u002FCR-{id}.md\n\n       Assess Scope Impact:\n       - Which requirements are affected? (list requirement IDs)\n       - Which features are impacted? (list features)\n       - Does this change project vision or objectives?\n       - What's the ripple effect on dependent features?\n\n       Categorize impact:\n       - Low: Minor change to existing feature (\u003C5% scope)\n       - Medium: New feature or significant change (5-15% scope)\n       - High: Changes to core functionality (>15% scope)\n\n       Document findings in impact assessment format.\n       Save to: .aiwg\u002Fworking\u002Fchange-control\u002Fscope-impact-{id}.md\n       \"\"\"\n   )\n\n   # Agent 2: Schedule and Cost Impact\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Assess schedule and cost impact\",\n       prompt=\"\"\"\n       Analyze change request: .aiwg\u002Fdecisions\u002Fchange-requests\u002FCR-{id}.md\n\n       Assess Schedule Impact:\n       - How many additional days\u002Fweeks required?\n       - Does this affect critical path?\n       - Which milestones are at risk?\n       - Can this be absorbed in current iteration?\n\n       Assess Cost Impact:\n       - Labor cost (additional hours × rate)\n       - Infrastructure\u002Ftool costs\n       - License costs (if any)\n       - Is this within contingency budget?\n\n       Categorize combined impact:\n       - Low: \u003C5% schedule\u002Fbudget impact, no milestone changes\n       - Medium: 5-15% impact, minor milestone adjustment\n       - High: >15% impact, major milestone shifts\n\n       Save to: .aiwg\u002Fworking\u002Fchange-control\u002Fschedule-cost-impact-{id}.md\n       \"\"\"\n   )\n\n   # Agent 3: Technical and Quality Impact\n   Task(\n       subagent_type=\"architecture-designer\",\n       description=\"Assess technical and quality impact\",\n       prompt=\"\"\"\n       Analyze change request: .aiwg\u002Fdecisions\u002Fchange-requests\u002FCR-{id}.md\n\n       Assess Technical Impact:\n       - Which components need modification?\n       - Does this affect architecture decisions?\n       - What's the integration complexity?\n       - Does this introduce technical debt?\n\n       Assess Quality Impact:\n       - Test coverage impact (new tests needed?)\n       - Performance implications\n       - Security implications\n       - Maintainability concerns\n\n       Categorize impact:\n       - Low: No architecture changes, minimal quality impact\n       - Medium: Component changes, temporary quality impact\n       - High: Architecture changes, significant quality concerns\n\n       Save to: .aiwg\u002Fworking\u002Fchange-control\u002Ftechnical-quality-impact-{id}.md\n       \"\"\"\n   )\n\n   # Agent 4: Risk Impact\n   Task(\n       subagent_type=\"risk-manager\",\n       description=\"Assess risk impact\",\n       prompt=\"\"\"\n       Analyze change request: .aiwg\u002Fdecisions\u002Fchange-requests\u002FCR-{id}.md\n       Read current risks: .aiwg\u002Frisks\u002Frisk-list.md\n\n       Assess Risk Impact:\n       - What new risks does this change introduce?\n       - Does this mitigate any existing risks?\n       - How does this affect risk severity\u002Flikelihood?\n       - What's the rollback risk if change fails?\n\n       Document:\n       - New risks introduced (with severity)\n       - Existing risks mitigated\n       - Risk severity changes\n       - Overall risk posture change\n\n       Categorize impact:\n       - Low: No new High\u002FCritical risks\n       - Medium: New Medium risks or increased severity\n       - High: New Show Stopper risks or multiple High risks\n\n       Save to: .aiwg\u002Fworking\u002Fchange-control\u002Frisk-impact-{id}.md\n       \"\"\"\n   )\n   ```\n\n3. **Synthesize Impact Assessment**:\n   ```\n   Task(\n       subagent_type=\"change-analyst\",\n       description=\"Synthesize comprehensive impact assessment\",\n       prompt=\"\"\"\n       Read all impact analyses:\n       - .aiwg\u002Fworking\u002Fchange-control\u002Fscope-impact-{id}.md\n       - .aiwg\u002Fworking\u002Fchange-control\u002Fschedule-cost-impact-{id}.md\n       - .aiwg\u002Fworking\u002Fchange-control\u002Ftechnical-quality-impact-{id}.md\n       - .aiwg\u002Fworking\u002Fchange-control\u002Frisk-impact-{id}.md\n\n       Create comprehensive Impact Assessment using template:\n       agentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Ftemplates\u002Fconfiguration\u002Fchange-request-card.md\n\n       Structure:\n       1. Executive Summary\n          - Overall impact rating: Low | Medium | High\n          - Recommendation: APPROVE | REJECT | DEFER\n\n       2. Detailed Impact Analysis\n          - Scope Impact: {summary with rating}\n          - Schedule Impact: {summary with rating}\n          - Cost Impact: {summary with rating}\n          - Quality Impact: {summary with rating}\n          - Risk Impact: {summary with rating}\n\n       3. Affected Artifacts\n          - List all documents\u002Fcode\u002Ftests affected\n          - Current baseline versions\n          - Proposed new versions\n\n       4. Stakeholder Impact\n          - Who is affected by this change\n          - Communication requirements\n\n       5. Implementation Considerations\n          - Prerequisites\n          - Dependencies\n          - Rollback strategy\n\n       6. Recommendation\n          - Clear APPROVE\u002FREJECT\u002FDEFER recommendation\n          - Rationale for recommendation\n          - Conditions (if conditional approval)\n\n       Save to: .aiwg\u002Fdecisions\u002Fimpact-assessments\u002FIA-{id}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Conducting impact assessment (4 parallel agents)...\n  ✓ Scope impact: MEDIUM (3 requirements affected)\n  ✓ Schedule impact: LOW (\u003C5% impact, no milestone changes)\n  ✓ Cost impact: LOW (within contingency)\n  ✓ Quality impact: MEDIUM (new tests required)\n  ✓ Risk impact: LOW (no new high risks)\n✓ Impact assessment complete: .aiwg\u002Fdecisions\u002Fimpact-assessments\u002FIA-{id}.md\nOverall Impact: MEDIUM | Recommendation: APPROVE\n```\n\n### Step 3: CCB Review and Decision\n\n**Purpose**: Present to Change Control Board for formal decision\n\n**Your Actions**:\n\n1. **Determine CCB Composition**:\n   ```\n   Based on change type and impact, determine reviewers:\n\n   Core CCB (always):\n   - Executive Sponsor (budget authority)\n   - Product Owner (scope authority)\n   - Software Architect (technical authority)\n   - Project Manager (schedule authority)\n\n   Extended CCB (conditionally):\n   - Security Architect (if security impact)\n   - Legal\u002FCompliance (if regulatory impact)\n   - Customer Representative (if customer-facing)\n   - DevOps Lead (if deployment impact)\n   ```\n\n2. **Launch CCB Review Agents** (parallel):\n   ```\n   # For each CCB member, launch review:\n\n   Task(\n       subagent_type=\"executive-sponsor\",\n       description=\"CCB review: Business and budget perspective\",\n       prompt=\"\"\"\n       Review change request and impact assessment:\n       - .aiwg\u002Fdecisions\u002Fchange-requests\u002FCR-{id}.md\n       - .aiwg\u002Fdecisions\u002Fimpact-assessments\u002FIA-{id}.md\n\n       Evaluate from executive perspective:\n       - Business value vs. cost\n       - Strategic alignment\n       - Budget availability\n       - Risk tolerance\n\n       Provide vote: APPROVE | REJECT | DEFER | ABSTAIN\n       Provide rationale for decision\n\n       Save review to: .aiwg\u002Fworking\u002Fccb-reviews\u002Fexecutive-sponsor-{id}.md\n       \"\"\"\n   )\n\n   Task(\n       subagent_type=\"product-owner\",\n       description=\"CCB review: Product and scope perspective\",\n       prompt=\"\"\"\n       Review change request and impact assessment\n\n       Evaluate from product perspective:\n       - Value to users\u002Fcustomers\n       - Scope creep concerns\n       - Feature priority\n       - Market timing\n\n       Provide vote: APPROVE | REJECT | DEFER | ABSTAIN\n       Provide rationale\n\n       Save to: .aiwg\u002Fworking\u002Fccb-reviews\u002Fproduct-owner-{id}.md\n       \"\"\"\n   )\n\n   Task(\n       subagent_type=\"architecture-designer\",\n       description=\"CCB review: Technical feasibility perspective\",\n       prompt=\"\"\"\n       Review change request and impact assessment\n\n       Evaluate from architecture perspective:\n       - Technical feasibility\n       - Architecture integrity\n       - Technical debt implications\n       - Integration complexity\n\n       Provide vote: APPROVE | REJECT | DEFER | ABSTAIN\n       Provide rationale\n\n       Save to: .aiwg\u002Fworking\u002Fccb-reviews\u002Farchitect-{id}.md\n       \"\"\"\n   )\n\n   # Add conditional reviewers based on guidance\u002Fimpact\n   ```\n\n3. **Synthesize CCB Decision**:\n   ```\n   Task(\n       subagent_type=\"ccb-coordinator\",\n       description=\"Document CCB decision\",\n       prompt=\"\"\"\n       Read all CCB reviews from .aiwg\u002Fworking\u002Fccb-reviews\u002F*-{id}.md\n\n       Tally votes:\n       - APPROVE: {count}\n       - REJECT: {count}\n       - DEFER: {count}\n       - ABSTAIN: {count}\n\n       Determine decision based on voting rules:\n       - Majority APPROVE → APPROVED\n       - Any REJECT with veto power → REJECTED\n       - Split decision → DEFERRED for more information\n\n       Document CCB Meeting using template:\n       CCB meeting fields in this skill\n\n       Include:\n       1. Meeting Details\n          - Date\u002FTime: {current-timestamp}\n          - Attendees: {CCB members}\n          - Quorum: YES (if majority present)\n\n       2. Change Request Review\n          - CR ID: {id}\n          - Presenter: Change Analyst\n          - Discussion summary\n\n       3. Voting Record\n          - Individual votes with rationale\n          - Final tally\n\n       4. Decision\n          - APPROVED | REJECTED | DEFERRED\n          - Decision rationale\n          - Conditions (if conditional approval)\n\n       5. Action Items\n          - If approved: Implementation timeline\n          - If rejected: Notification plan\n          - If deferred: Information needed\n\n       Save to: .aiwg\u002Fdecisions\u002Fccb-meetings\u002FCCB-{date}-CR-{id}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ CCB review in progress...\n  ✓ Executive Sponsor: APPROVE (strategic value outweighs cost)\n  ✓ Product Owner: APPROVE (customer requested feature)\n  ✓ Software Architect: CONDITIONAL (requires ADR for API change)\n  ✓ Project Manager: APPROVE (can fit in current iteration)\n✓ CCB Decision: APPROVED (3 approve, 1 conditional)\nConditions: Create ADR for API versioning strategy\n```\n\n### Step 4: Update Baseline and Documentation\n\n**Purpose**: Update project baselines with approved changes\n\n**Your Actions**:\n\n1. **Identify Affected Baselines**:\n   ```\n   Task(\n       subagent_type=\"configuration-manager\",\n       description=\"Identify baselines to update\",\n       prompt=\"\"\"\n       Based on approved change CR-{id}, identify:\n\n       1. Affected Baselines:\n          - Functional Baseline (requirements, design)\n          - Product Baseline (code, tests)\n          - Project Baseline (schedule, budget)\n\n       2. Current Versions:\n          - Document current version tags\n          - Identify last baseline date\n\n       3. Update Scope:\n          - List specific artifacts to update\n          - Determine new version numbers\n\n       Create baseline update plan.\n       Save to: .aiwg\u002Fworking\u002Fbaseline-plan-{id}.md\n       \"\"\"\n   )\n   ```\n\n2. **Update Artifacts** (parallel where possible):\n   ```\n   # Based on change type, update relevant artifacts\n\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Update requirements baseline\",\n       prompt=\"\"\"\n       For approved change CR-{id}:\n\n       Update affected requirements:\n       - Modify existing requirements as needed\n       - Add new requirements if applicable\n       - Update requirement IDs and traceability\n       - Update version numbers\n\n       Document changes in each file with:\n       \u003C!-- Change CR-{id}: Description of change -->\n\n       Save updated requirements to original locations.\n       Create change summary: .aiwg\u002Fworking\u002Frequirements-changes-{id}.md\n       \"\"\"\n   )\n\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Update project plan\",\n       prompt=\"\"\"\n       For approved change CR-{id}:\n\n       Update project artifacts:\n       - Adjust schedule if needed\n       - Update budget allocations\n       - Modify resource assignments\n       - Update risk register\n\n       Document baseline version change.\n       Save updates to original locations.\n       \"\"\"\n   )\n   ```\n\n3. **Create Baseline Update Log**:\n   ```\n   Task(\n       subagent_type=\"configuration-manager\",\n       description=\"Document baseline update\",\n       prompt=\"\"\"\n       Create baseline update log using template:\n       baseline update fields in this skill\n\n       Document:\n       1. Change Authorization\n          - CR ID: {id}\n          - CCB Approval Date: {date}\n          - Implementer: {agent\u002Fperson}\n\n       2. Baseline Updates\n          - Previous Version: {old-version}\n          - New Version: {new-version}\n          - Artifacts Updated: {list}\n\n       3. Version Control\n          - Git Tag: baseline-{new-version}\n          - Commit Hash: {if applicable}\n          - Branch: {if applicable}\n\n       4. Validation\n          - Updates verified: YES\n          - Traceability maintained: YES\n          - Tests updated: YES\u002FNO\u002FNA\n\n       Save to: .aiwg\u002Fdecisions\u002Fbaseline-updates\u002FBU-{id}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Updating baselines...\n  ✓ Requirements baseline updated (v1.1 → v1.2)\n  ✓ Project plan updated (schedule adjusted)\n  ✓ Risk register updated (new risk added)\n✓ Baseline update complete: v1.2\n✓ Update log: .aiwg\u002Fdecisions\u002Fbaseline-updates\u002FBU-{id}.md\n```\n\n### Step 5: Communicate Change Decision\n\n**Purpose**: Notify all stakeholders of change decision and impacts\n\n**Your Actions**:\n\n1. **Identify Stakeholders**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Identify stakeholders to notify\",\n       prompt=\"\"\"\n       Based on change CR-{id} and impact assessment:\n\n       Identify stakeholder groups:\n       1. Direct Impact (must notify immediately):\n          - Change requestor\n          - Teams working on affected components\n          - Downstream dependencies\n\n       2. Indirect Impact (should notify):\n          - Adjacent teams\n          - QA\u002FTest teams\n          - Operations\u002FDevOps\n\n       3. Informational (nice to notify):\n          - Broader development team\n          - Management chain\n          - Customers (if applicable)\n\n       Determine notification priority and channel for each group.\n       Save to: .aiwg\u002Fworking\u002Fstakeholder-list-{id}.md\n       \"\"\"\n   )\n   ```\n\n2. **Create Stakeholder Communications**:\n   ```\n   Task(\n       subagent_type=\"technical-writer\",\n       description=\"Draft stakeholder notifications\",\n       prompt=\"\"\"\n       Create notifications for change CR-{id} decision: {APPROVED|REJECTED|DEFERRED}\n\n       For each stakeholder group, create appropriate message:\n\n       1. Change Requestor Notification:\n          - Decision and rationale\n          - Next steps\n          - Timeline (if approved)\n          - Contact for questions\n\n       2. Development Team Notification:\n          - What's changing\n          - When it's changing\n          - Impact on their work\n          - Updated artifacts\u002Fbaselines\n\n       3. Management Summary:\n          - Decision summary\n          - Business impact\n          - Schedule\u002Fcost impact\n          - Risk considerations\n\n       Use the inline format: stakeholder notification fields in this skill\n\n       Save to: .aiwg\u002Fdecisions\u002Fcommunications\u002FCOMM-{id}-{audience}.md\n       \"\"\"\n   )\n   ```\n\n3. **Track Communication Delivery**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Document communication delivery\",\n       prompt=\"\"\"\n       Track stakeholder notifications for CR-{id}:\n\n       Create communication log:\n       1. Stakeholder: {name\u002Fgroup}\n       2. Notification sent: {timestamp}\n       3. Channel: {email\u002Fslack\u002Fmeeting}\n       4. Acknowledgment: {received\u002Fpending}\n       5. Follow-up needed: {yes\u002Fno}\n\n       Save to: .aiwg\u002Fdecisions\u002Fcommunications\u002FCOMM-{id}-log.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Notifying stakeholders...\n  ✓ Change requestor notified (acknowledged)\n  ✓ Development team notified (3 teams)\n  ✓ QA team notified\n  ✓ Management briefed\n✓ Stakeholder communication complete\n✓ Communication log: .aiwg\u002Fdecisions\u002Fcommunications\u002FCOMM-{id}-log.md\n```\n\n### Step 6: Track Change Implementation\n\n**Purpose**: Create work items and track implementation to completion\n\n**Your Actions**:\n\n1. **Create Implementation Work Items**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Create work items for change implementation\",\n       prompt=\"\"\"\n       For approved change CR-{id}, create work items:\n\n       Based on impact assessment and change scope:\n       1. Break down change into discrete tasks\n       2. Assign to appropriate teams\u002Findividuals\n       3. Set priorities and dependencies\n       4. Define acceptance criteria\n       5. Estimate effort\n\n       For each work item, document:\n       - WI-{id}: {title}\n       - Assigned to: {team\u002Fperson}\n       - Priority: {P0\u002FP1\u002FP2\u002FP3}\n       - Effort: {hours\u002Fdays}\n       - Dependencies: {other WIs}\n       - Acceptance Criteria: {specific, measurable}\n\n       Save to: .aiwg\u002Fdecisions\u002Fimplementation\u002Fwork-items-CR-{id}.md\n       \"\"\"\n   )\n   ```\n\n2. **Create Implementation Tracking**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Set up implementation tracking\",\n       prompt=\"\"\"\n       Create implementation tracking for CR-{id}:\n\n       Structure:\n       1. Implementation Plan\n          - Start Date: {date}\n          - Target Completion: {date}\n          - Implementation Lead: {name}\n\n       2. Work Items Status\n          - Total: {count}\n          - Not Started: {count}\n          - In Progress: {count}\n          - Completed: {count}\n          - Blocked: {count}\n\n       3. Validation Plan\n          - How to verify change is successful\n          - Test cases to run\n          - Metrics to measure\n\n       4. Rollback Plan\n          - Rollback triggers\n          - Rollback procedure\n          - Rollback owner\n\n       Save to: .aiwg\u002Fdecisions\u002Fimplementation\u002FIMPL-{id}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Setting up implementation tracking...\n  ✓ 5 work items created\n  ✓ Implementation plan defined (5-day timeline)\n  ✓ Validation criteria established\n  ✓ Rollback plan documented\n✓ Implementation tracking: .aiwg\u002Fdecisions\u002Fimplementation\u002FIMPL-{id}.md\n```\n\n### Step 7: Generate Change Control Report\n\n**Purpose**: Create comprehensive report of change control process\n\n**Your Actions**:\n\n```\nTask(\n    subagent_type=\"change-analyst\",\n    description=\"Generate comprehensive change control report\",\n    prompt=\"\"\"\n    Synthesize all change control artifacts for CR-{id}:\n\n    Read:\n    - .aiwg\u002Fdecisions\u002Fchange-requests\u002FCR-{id}.md\n    - .aiwg\u002Fdecisions\u002Fimpact-assessments\u002FIA-{id}.md\n    - .aiwg\u002Fdecisions\u002Fccb-meetings\u002FCCB-*-CR-{id}.md\n    - .aiwg\u002Fdecisions\u002Fbaseline-updates\u002FBU-{id}.md\n    - .aiwg\u002Fdecisions\u002Fcommunications\u002FCOMM-{id}-log.md\n    - .aiwg\u002Fdecisions\u002Fimplementation\u002FIMPL-{id}.md\n\n    Generate Change Control Report:\n\n    # Change Control Report - CR-{id}\n\n    ## Executive Summary\n    - Change ID: CR-{id}\n    - Type: {scope|schedule|resource|technical|process|risk}\n    - Priority: {P0|P1|P2|P3}\n    - Status: {APPROVED|REJECTED|DEFERRED|IMPLEMENTED}\n    - Decision Date: {date}\n\n    ## Change Request\n    - Requestor: {name\u002Frole}\n    - Justification: {summary}\n    - Current State: {brief}\n    - Desired State: {brief}\n\n    ## Impact Assessment\n    - Overall Impact: {LOW|MEDIUM|HIGH}\n    - Scope: {rating} - {summary}\n    - Schedule: {rating} - {days\u002Fweeks impact}\n    - Cost: {rating} - ${amount}\n    - Quality: {rating} - {summary}\n    - Risk: {rating} - {new risks, mitigated risks}\n\n    ## CCB Decision\n    - Meeting Date: {date}\n    - Attendees: {list}\n    - Vote: {tally}\n    - Decision: {APPROVED|REJECTED|DEFERRED}\n    - Rationale: {summary}\n    - Conditions: {if any}\n\n    ## Baseline Updates\n    - Previous Version: {version}\n    - New Version: {version}\n    - Artifacts Updated: {count}\n    - Update Date: {date}\n\n    ## Stakeholder Communication\n    - Notifications Sent: {count}\n    - Key Stakeholders: {list}\n    - Communication Status: COMPLETE\n\n    ## Implementation Status\n    - Work Items: {total count}\n    - Progress: {percentage}%\n    - Target Completion: {date}\n    - Current Status: {NOT_STARTED|IN_PROGRESS|COMPLETED|BLOCKED}\n\n    ## Lessons Learned\n    - What went well\n    - What could improve\n    - Recommendations for future changes\n\n    ## Appendices\n    - Links to all related documents\n    - Audit trail\n\n    Save to: .aiwg\u002Freports\u002Fchange-control-report-CR-{id}.md\n    \"\"\"\n)\n```\n\n**Final Communication**:\n```\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nChange Control Process Complete\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n\nChange ID: CR-{id}\nDecision: APPROVED\nImpact: MEDIUM\nImplementation: IN PROGRESS\n\nArtifacts Generated:\n✓ Change Request: .aiwg\u002Fdecisions\u002Fchange-requests\u002FCR-{id}.md\n✓ Impact Assessment: .aiwg\u002Fdecisions\u002Fimpact-assessments\u002FIA-{id}.md\n✓ CCB Decision: .aiwg\u002Fdecisions\u002Fccb-meetings\u002FCCB-{date}-CR-{id}.md\n✓ Baseline Update: .aiwg\u002Fdecisions\u002Fbaseline-updates\u002FBU-{id}.md\n✓ Communications: .aiwg\u002Fdecisions\u002Fcommunications\u002FCOMM-{id}-*.md\n✓ Implementation Plan: .aiwg\u002Fdecisions\u002Fimplementation\u002FIMPL-{id}.md\n✓ Final Report: .aiwg\u002Freports\u002Fchange-control-report-CR-{id}.md\n\nNext Steps:\n1. Monitor implementation progress\n2. Validate acceptance criteria\n3. Close change request when complete\n\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n```\n\n## Quality Gates\n\nBefore marking workflow complete, verify:\n- [ ] Change request formally documented\n- [ ] Impact assessment covers all dimensions\n- [ ] CCB quorum achieved and decision recorded\n- [ ] Baseline updated with version control\n- [ ] All stakeholders notified appropriately\n- [ ] Implementation tracking established\n- [ ] Comprehensive report generated\n\n## Success Criteria\n\nThis orchestration succeeds when:\n- [ ] Change request has clear business justification\n- [ ] Impact assessed across scope, schedule, cost, quality, risk\n- [ ] CCB review conducted with quorum\n- [ ] Decision recorded with rationale\n- [ ] If approved: Baselines updated and versioned\n- [ ] If rejected: Requestor notified with reasoning\n- [ ] If deferred: Follow-up scheduled\n- [ ] Stakeholders appropriately informed\n- [ ] Implementation plan created (if approved)\n- [ ] Complete audit trail maintained\n\n## Error Handling\n\n**If No Quorum**:\n```\n⚠️ CCB quorum not met ({present}\u002F{required})\n\nCannot proceed with decision.\n\nActions:\n1. Reschedule CCB meeting\n2. For P0-Critical: Invoke emergency process\n3. Notify change requestor of delay\n\nNext meeting scheduled: {date\u002Ftime}\n```\n\n**If Impact Too High**:\n```\n⚠️ Change impact exceeds thresholds\n\nImpact Summary:\n- Scope: HIGH (>15% change)\n- Cost: HIGH (>15% budget impact)\n- Schedule: HIGH (milestone at risk)\n\nRecommendation: REJECT or significant re-scoping\n\nEscalating to Executive Sponsor...\n```\n\n**If Baseline Conflict**:\n```\n❌ Baseline update conflict detected\n\nConflict: Another change (CR-{other-id}) modified same artifacts\n\nResolution needed:\n1. Analyze conflict scope\n2. Determine precedence\n3. Merge changes if compatible\n4. Defer one change if incompatible\n\nEscalating to CCB...\n```\n\n## References\n\n**Templates** (via $AIWG_ROOT):\n- Change Request: `agentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Ftemplates\u002Fconfiguration\u002Fchange-request-card.md`\n- Impact Assessment: `agentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Ftemplates\u002Fconfiguration\u002Fchange-request-card.md`\n- CCB Meeting Notes: CCB meeting fields in this skill\n- Baseline Log: baseline update fields in this skill\n- Stakeholder Communication: stakeholder notification fields in this skill\n- Work Package Card: `templates\u002Fmanagement\u002Fwork-package-card.md`\n\n**Related Flows**:\n- Gate Checks: `flow-gate-check.md`\n- Risk Management: `flow-risk-management-cycle.md`\n- Architecture Evolution: `flow-architecture-evolution.md`\n- Requirements Management: `flow-requirements-baseline.md`\n\n**External References**:\n- PMBOK Guide Change Control Process\n- Configuration Management Best Practices",{"name":5,"namespace":49,"platforms":50,"commandHint":52,"description":7},"aiwg",[51],"all",{"model":30,"category":53,"modelRole":33,"modelTier":54,"allowedTools":55,"argumentHint":56,"orchestration":57},"sdlc-orchestration","standard","Task, Read, Write, Glob, TodoWrite","[change-type] [change-id] [project-directory] [--guidance \"text\"] [--interactive]",true,"main","a602706fc62ff1cfcb18001358ac39647b08acf5","agentic\u002Fcode\u002Fplugins\u002Fsdlc\u002Fskills\u002Fflow-change-control",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-14 02:10:01",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":57},[70,73,76],{"tool":71,"command":72},"npx","npx skills add jmagly\u002Faiwg --skill flow-change-control",{"tool":74,"command":75},"bunx","bunx skills add jmagly\u002Faiwg --skill flow-change-control",{"tool":77,"command":78},"pnpm","pnpm dlx skills add jmagly\u002Faiwg --skill flow-change-control","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fsdlc\u002Fskills\u002Fflow-change-control\u002FSKILL.md",[],[82,109,132,138,145,158],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":89,"publishedAt":44},"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",[88],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[90,91,92,35,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108],"host","host hardening","hardening","re","recommendations","remediation","plan","port","verification","Bash","access","only","retention","audit","never","firewall","bind","secrets","request",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":119,"publishedAt":44},"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",[115,118],{"categoryNo":116,"categoryName":117,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[120,121,122,35,123,97,124,125,99,126,90,127,101,128,129,104,105,130,131,34],"exposure analysis","analysis","unknown","credentials","collection","ufw","ports","internet","local","scope","reconstruction","operator",{"skillNo":133,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":137,"publishedAt":44},"01M70P8QATMPKA78E4FT5D2TNA","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[136],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[92,90,91,100,35,108,95,94,103,96,97,98,99,107,101,102,93,104,105,106],{"skillNo":139,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":144,"publishedAt":44},"01M70NMPVJ5H0JH131P60FW4R8","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[142,143],{"categoryNo":116,"categoryName":117,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[121,120,104,123,97,124,99,122,90,127,101,128,129,35,105,126,125,130,131,34],{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":152,"publishedAt":44},"01M6CB4DDR0B4NNCFK7ZK7449H","fixture-skill","Exercise rule delivery.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Frule-delivery\u002Fskills\u002Ffixture-skill\u002FSKILL.md",[151],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[153,154,155,156,29,157],"fixture skill","fixture","rule","delivery","exercise",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":165,"publishedAt":44},"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",[164],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[166,167,128,168,154],"pi","pi local","duplicate"]