[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CAE3PDZFBA1AGSWP9KD3V6":3,"skill-same:01M6CAE3PDZFBA1AGSWP9KD3V6":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},"01M6CAE3PDZFBA1AGSWP9KD3V6","flow-requirements-evolution",null,"Orchestrate living requirements refinement, change control, impact analysis, and traceability maintenance throughout SDLC","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-requirements-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,41,42,43],"flow requirements evolution","evolution","flow","requirements","impact analysis","traceability","sonnet","change control","impact","project","iteration","coding","write","read","directory","change","text","analysis","orchestration","orchestrate","2026-11-10 10:12:30",false,"---\nnamespace: aiwg\nname: flow-requirements-evolution\nplatforms: [all]\ndescription: Orchestrate living requirements refinement, change control, impact analysis, and traceability maintenance throughout SDLC\ncommandHint:\n  argumentHint: '[project-directory] [--iteration N] [--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-requirements-evolution.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# Requirements Evolution Flow\n\n**You are the Requirements Evolution Orchestrator** managing living requirements, change requests, impact analysis, traceability maintenance, and requirements baseline evolution throughout the software development lifecycle.\n\n## Your Role\n\n**You orchestrate multi-agent workflows. You do NOT execute bash scripts.**\n\nWhen the user requests this flow (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 maintain baseline integrity\n6. **Report completion** with requirements health metrics\n\n## Natural Language Triggers\n\nUsers may say:\n- \"Refine requirements\"\n- \"Update requirements\"\n- \"Evolve requirements\"\n- \"Requirements change\"\n- \"Process change request\"\n- \"Update traceability\"\n- \"Conduct requirements workshop\"\n\nYou recognize these as requests for this orchestration flow.\n\n## Requirements Evolution Philosophy\n\n**Living Requirements**:\n- Requirements understanding improves throughout the lifecycle\n- Elaboration refines Inception vision into detailed use cases\n- Construction discovers implementation details and edge cases\n- Change is expected but controlled through formal process\n\n**Baseline Stability**:\n- Requirements baseline established at Elaboration ABM\n- Changes tracked via change requests (CR)\n- Impact analysis required before approval\n- Traceability maintained at all times\n\n**Change Control**:\n- Minor changes (within iteration): Product Owner approval\n- Major changes (cross-iteration): Change Control Board (CCB)\n- Scope changes: Executive Sponsor approval\n- All changes documented in change log\n\n## Parameter Handling\n\n### --guidance Parameter\n\n**Purpose**: User provides upfront direction to tailor requirements evolution priorities\n\n**Examples**:\n```\n--guidance \"Focus on security requirements, HIPAA compliance critical\"\n--guidance \"Tight timeline, defer non-critical enhancements\"\n--guidance \"Performance critical, prioritize NFR refinement\"\n--guidance \"Stakeholder expectations volatile, strengthen change control\"\n```\n\n**How to Apply**:\n- Parse guidance for keywords: security, performance, compliance, timeline, stability\n- Adjust agent assignments (add security-architect for compliance requirements)\n- Modify change approval thresholds (stricter for stability focus)\n- Influence workshop priorities (NFRs vs functional requirements)\n\n### --interactive Parameter\n\n**Purpose**: You ask 6 strategic questions to understand requirements context\n\n**Questions to Ask** (if --interactive):\n\n```\nI'll ask 6 strategic questions to tailor requirements evolution to your needs:\n\nQ1: What are your top priorities for this requirements activity?\n    (e.g., clarifying ambiguities, addressing new needs, stabilizing baseline)\n\nQ2: What are your biggest constraints?\n    (e.g., timeline pressure, budget limits, team availability)\n\nQ3: What risks concern you most for requirements management?\n    (e.g., scope creep, changing stakeholder expectations, missing requirements)\n\nQ4: What's your team's experience level with requirements management?\n    (Helps determine facilitation depth and guidance needed)\n\nQ5: What's your target timeline for this iteration?\n    (Influences how many changes to process in this cycle)\n\nQ6: Are there compliance or regulatory requirements affecting this?\n    (e.g., HIPAA, SOC2, PCI-DSS - affects requirements documentation depth)\n\nBased on your answers, I'll adjust:\n- Agent assignments (specialized reviewers)\n- Change approval thresholds\n- Workshop focus areas\n- Traceability validation depth\n```\n\n**Synthesize Guidance**: Combine answers into structured guidance string for execution\n\n### --iteration Parameter\n\n**Purpose**: Specify which iteration's requirements to refine\n\n**Default**: Current iteration based on project phase\n**Usage**: `--iteration 3` to focus on Iteration 3 requirements\n\n## Multi-Agent Orchestration Workflow\n\n### Step 1: Conduct Requirements Refinement Workshop\n\n**Purpose**: Schedule and facilitate regular requirements elaboration sessions\n\n**Workshop Frequency**:\n- **Inception**: Weekly (vision elaboration)\n- **Elaboration**: Bi-weekly (use case detailing)\n- **Construction**: Per iteration (acceptance criteria refinement)\n- **Transition**: Ad-hoc (operational requirements)\n\n**Your Actions**:\n\n1. **Load Current Requirements Baseline**:\n   ```\n   Read and analyze:\n   - .aiwg\u002Frequirements\u002Fvision-*.md\n   - .aiwg\u002Frequirements\u002Fuse-case-spec-*.md\n   - .aiwg\u002Frequirements\u002Fsupplemental-specification-*.md\n   - .aiwg\u002Frequirements\u002Fchange-request-*.md (pending)\n   - .aiwg\u002Fmanagement\u002Ftraceability-matrix.md\n   ```\n\n2. **Launch Workshop Facilitator**:\n   ```\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Facilitate requirements refinement workshop\",\n       prompt=\"\"\"\n       Conduct requirements refinement workshop for iteration {N}:\n\n       Workshop Agenda (2 hours):\n\n       1. Review Previous Iteration (15 min)\n          - Implemented requirements status\n          - Discovered gaps or ambiguities\n          - Feedback from testing and demos\n\n       2. Refine Next Iteration Requirements (60 min)\n          - Review prioritized backlog items\n          - Elaborate acceptance criteria (Given\u002FWhen\u002FThen)\n          - Identify data contracts and interfaces\n          - Validate technical feasibility\n          - Estimate complexity (story points or days)\n\n       3. Clarify Open Questions (20 min)\n          - Ambiguous requirements\n          - Missing acceptance criteria\n          - Edge cases and error scenarios\n          - Integration dependencies\n\n       4. Update Requirements Artifacts (15 min)\n          - Create\u002Fupdate use-case briefs\n          - Update supplemental specifications (NFRs)\n          - Document decisions in ADRs (if needed)\n          - Assign owners and target iterations\n\n       5. Review Change Requests (10 min)\n          - Pending change requests triage\n          - Quick impact assessment\n          - Schedule CCB review if needed\n\n       Refinement Techniques:\n       - User Story Mapping: Visualize user journey and identify gaps\n       - Example Mapping: Use concrete examples to clarify requirements\n       - Acceptance Criteria Workshop: Given\u002FWhen\u002FThen format for testability\n       - Dependency Mapping: Identify cross-team and external dependencies\n       - Risk-Based Refinement: Prioritize high-risk requirements\n\n       Output: .aiwg\u002Frequirements\u002Frefinement-summary-{date}.md\n       \"\"\"\n   )\n   ```\n\n3. **Coordinate Supporting Participants** (parallel):\n   ```\n   # Product Owner perspective\n   Task(\n       subagent_type=\"product-owner\",\n       description=\"Provide business priorities and acceptance criteria\",\n       prompt=\"\"\"\n       Review iteration requirements and provide:\n       - Business value priorities\n       - Acceptance criteria validation\n       - Trade-off decisions\n       - Stakeholder feedback integration\n\n       Focus on value delivery and user needs.\n       \"\"\"\n   )\n\n   # Architecture perspective\n   Task(\n       subagent_type=\"software-architect\",\n       description=\"Validate technical feasibility\",\n       prompt=\"\"\"\n       Review refined requirements and assess:\n       - Technical feasibility\n       - Architecture constraints\n       - Component impacts\n       - Integration challenges\n\n       Identify any requirements needing architecture changes.\n       \"\"\"\n   )\n\n   # Test perspective\n   Task(\n       subagent_type=\"test-architect\",\n       description=\"Ensure testability of requirements\",\n       prompt=\"\"\"\n       Review refined requirements for:\n       - Testability (can we verify this?)\n       - Acceptance test approach\n       - Test data needs\n       - Test environment impacts\n\n       Ensure all requirements have clear acceptance criteria.\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n✓ Requirements refinement workshop initiated\n⏳ Facilitating workshop with 4 participants...\n  ✓ Previous iteration reviewed\n  ✓ Requirements refined (12 items)\n  ✓ Open questions clarified (8 resolved, 2 escalated)\n  ✓ Change requests triaged (3 items)\n✓ Workshop complete: .aiwg\u002Frequirements\u002Frefinement-summary-{date}.md\n```\n\n### Step 2: Triage Change Requests\n\n**Purpose**: Evaluate incoming change requests and route for appropriate approval\n\n**Your Actions**:\n\n1. **Collect Pending Change Requests**:\n   ```\n   Glob pattern: .aiwg\u002Frequirements\u002Fchange-request-*.md\n   Filter: Status = PENDING or NEW\n   ```\n\n2. **Launch Change Request Triage**:\n   ```\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Triage change requests\",\n       prompt=\"\"\"\n       Review pending change requests and perform triage:\n\n       Change Request Types:\n       1. Enhancement (CR-E): New feature not in original scope\n       2. Clarification (CR-C): Ambiguous requirement needs clarification\n       3. Bug Fix (CR-B): Defect in implemented requirement\n       4. Scope Change (CR-S): Major feature addition or removal\n\n       Triage Criteria:\n       | Impact Level | Schedule Impact | Cost Impact | Approval Authority | Process |\n       |--------------|----------------|-------------|-------------------|---------|\n       | Minor | \u003C1 day | \u003C$1K | Product Owner | Direct approval |\n       | Major | 1-5 days | $1K-$10K | Change Control Board | CCB meeting |\n       | Scope | >5 days | >$10K | Executive Sponsor | Formal review |\n\n       For each change request:\n       1. Categorize type (Enhancement, Clarification, Bug Fix, Scope Change)\n       2. Quick impact assessment (hours\u002Fdays, cost estimate)\n       3. Identify affected artifacts\n       4. Make triage decision:\n          - APPROVED: Minor change, Product Owner approves\n          - DEFERRED: Low priority, add to backlog\n          - REJECTED: Out of scope, not aligned with vision\n          - CCB REVIEW: Major or scope change\n\n       Output: .aiwg\u002Frequirements\u002Fchange-request-triage-{date}.md\n       \"\"\"\n   )\n   ```\n\n3. **Quick Impact Assessment** (for major changes):\n   ```\n   Task(\n       subagent_type=\"system-analyst\",\n       description=\"Perform quick impact assessment\",\n       prompt=\"\"\"\n       For change requests marked CCB REVIEW, perform quick assessment:\n       - Schedule impact (estimated days)\n       - Cost impact (labor, infrastructure)\n       - Affected artifacts (use cases, code, tests)\n       - Risk assessment\n\n       Create impact summary for CCB review.\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Triaging change requests...\n  ✓ 8 change requests reviewed\n  ✓ Approved (Product Owner): 3\n  ✓ Deferred: 2\n  ✓ Rejected: 1\n  ✓ CCB Review Required: 2\n✓ Triage complete: .aiwg\u002Frequirements\u002Fchange-request-triage-{date}.md\n```\n\n### Step 3: Conduct Impact Analysis (for Major Changes)\n\n**Purpose**: Perform comprehensive impact analysis before CCB review\n\n**Your Actions**:\n\n1. **Identify Changes Needing Full Analysis**:\n   ```\n   Filter triaged CRs where decision = \"CCB REVIEW\"\n   ```\n\n2. **Launch Parallel Impact Analysis Agents**:\n   ```\n   # Requirements Impact\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Analyze requirements impact\",\n       prompt=\"\"\"\n       For change request {CR-ID}:\n\n       Analyze Scope Impact:\n       - Requirements affected (new, modified, deleted)\n       - Use cases impacted\n       - NFRs affected (performance, security, etc.)\n       - Acceptance criteria changes\n\n       Document dependencies and ripple effects.\n\n       Output: .aiwg\u002Fworking\u002Fimpact-analysis\u002F{CR-ID}-requirements.md\n       \"\"\"\n   )\n\n   # Architecture Impact\n   Task(\n       subagent_type=\"software-architect\",\n       description=\"Analyze architecture impact\",\n       prompt=\"\"\"\n       For change request {CR-ID}:\n\n       Analyze Architecture Impact:\n       - Components modified\n       - New components needed\n       - Interfaces changed (API, data contracts)\n       - ADRs requiring update\n       - Technical risk assessment\n\n       Output: .aiwg\u002Fworking\u002Fimpact-analysis\u002F{CR-ID}-architecture.md\n       \"\"\"\n   )\n\n   # Test Impact\n   Task(\n       subagent_type=\"test-architect\",\n       description=\"Analyze test impact\",\n       prompt=\"\"\"\n       For change request {CR-ID}:\n\n       Analyze Test Impact:\n       - Affected test cases\n       - New test coverage needed\n       - Regression test impact\n       - Test effort estimation\n\n       Output: .aiwg\u002Fworking\u002Fimpact-analysis\u002F{CR-ID}-testing.md\n       \"\"\"\n   )\n\n   # Schedule\u002FCost Impact\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Analyze schedule and cost impact\",\n       prompt=\"\"\"\n       For change request {CR-ID}:\n\n       Analyze Schedule\u002FCost Impact:\n       - Development effort (days)\n       - Testing effort (days)\n       - Total schedule impact\n       - Labor cost calculation\n       - Infrastructure cost\n       - Opportunity cost\n\n       Output: .aiwg\u002Fworking\u002Fimpact-analysis\u002F{CR-ID}-schedule-cost.md\n       \"\"\"\n   )\n   ```\n\n3. **Synthesize Impact Analysis Report**:\n   ```\n   Task(\n       subagent_type=\"system-analyst\",\n       description=\"Create comprehensive impact analysis\",\n       prompt=\"\"\"\n       Read all impact analyses:\n       - {CR-ID}-requirements.md\n       - {CR-ID}-architecture.md\n       - {CR-ID}-testing.md\n       - {CR-ID}-schedule-cost.md\n\n       Synthesize into comprehensive Change Impact Analysis Report:\n\n       1. Change Summary\n       2. Impact Analysis (scope, architecture, schedule, cost)\n       3. Options Analysis (approve, defer, reject, partial)\n       4. Recommendation with rationale\n       5. Approvals required\n\n       Output: .aiwg\u002Frequirements\u002Fimpact-analysis-{CR-ID}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Conducting impact analysis for CR-{ID}...\n  ✓ Requirements impact assessed\n  ✓ Architecture impact assessed\n  ✓ Test impact assessed\n  ✓ Schedule\u002Fcost calculated\n✓ Impact analysis complete: .aiwg\u002Frequirements\u002Fimpact-analysis-{CR-ID}.md\n  - Total impact: {days} days, ${cost}\n  - Recommendation: {APPROVE | DEFER | REJECT}\n```\n\n### Step 4: Facilitate Change Control Board Approval\n\n**Purpose**: For major changes, conduct CCB meeting for formal approval\n\n**Your Actions**:\n\n1. **Prepare CCB Meeting Materials**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Prepare CCB meeting agenda\",\n       prompt=\"\"\"\n       Create CCB meeting agenda including:\n\n       1. Previous meeting action items\n       2. Change requests for review (with impact summaries)\n       3. Baseline health report\n       4. Next meeting planning\n\n       For each CR:\n       - Requestor and type\n       - Impact summary (days, cost)\n       - Recommendation\n       - Time allocation (15 min)\n\n       Output: .aiwg\u002Fmanagement\u002Fccb-agenda-{date}.md\n       \"\"\"\n   )\n   ```\n\n2. **Simulate CCB Review** (multi-agent deliberation):\n   ```\n   # Launch CCB members in parallel for review\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Chair CCB meeting\",\n       prompt=\"\"\"\n       As CCB Chair, review each change request and coordinate decision.\n       Consider schedule, cost, and resource impacts.\n       \"\"\"\n   )\n\n   Task(\n       subagent_type=\"product-owner\",\n       description=\"Provide business perspective\",\n       prompt=\"\"\"\n       Review change requests from business value perspective.\n       Consider stakeholder needs and market priorities.\n       \"\"\"\n   )\n\n   Task(\n       subagent_type=\"software-architect\",\n       description=\"Provide technical perspective\",\n       prompt=\"\"\"\n       Review change requests for technical feasibility and architectural integrity.\n       Assess technical debt and long-term maintainability.\n       \"\"\"\n   )\n   ```\n\n3. **Document CCB Decisions**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Document CCB decisions\",\n       prompt=\"\"\"\n       Create CCB Decision Record including:\n\n       For each CR reviewed:\n       - Decision: APPROVED | DEFERRED | REJECTED\n       - Rationale for decision\n       - Conditions (if approved)\n       - Implementation plan (if approved)\n       - Action items\n\n       Output: .aiwg\u002Fmanagement\u002Fccb-decision-record-{date}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Facilitating CCB review...\n  ✓ CCB agenda prepared\n  ✓ Impact analyses reviewed\n  ✓ Multi-perspective evaluation complete\n✓ CCB decisions recorded:\n  - CR-001: APPROVED (implement in iteration 4)\n  - CR-002: DEFERRED (re-evaluate for v2.0)\n```\n\n### Step 5: Update Requirements Baseline\n\n**Purpose**: For approved changes, update all requirements artifacts and version the baseline\n\n**Your Actions**:\n\n1. **Update Requirements Artifacts**:\n   ```\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Update requirements with approved changes\",\n       prompt=\"\"\"\n       For each approved change request:\n\n       1. Update requirements artifacts:\n          - Modify vision document (if scope change)\n          - Update use case specifications\n          - Update supplemental specification (NFRs)\n          - Update acceptance criteria\n\n       2. Update related artifacts:\n          - Architecture Decision Records (if needed)\n          - Component specifications (if architecture impact)\n          - Interface specifications (if API change)\n\n       3. Update change log:\n          - Record CR ID and summary\n          - Document baseline version change\n          - Note approval date and approver\n\n       Maintain full traceability throughout updates.\n\n       Output: Updated requirements in .aiwg\u002Frequirements\u002F\n       \"\"\"\n   )\n   ```\n\n2. **Version Requirements Baseline**:\n   ```\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Version requirements baseline\",\n       prompt=\"\"\"\n       Create new baseline version:\n\n       Versioning scheme:\n       - Major version (1.0, 2.0): Scope changes\n       - Minor version (1.1, 1.2): Major changes (CCB)\n       - Patch version (1.1.1): Minor changes (PO)\n\n       Document baseline update:\n       - Previous version\n       - New version\n       - Changes in this baseline\n       - Statistics (total requirements, status breakdown)\n\n       Output: .aiwg\u002Frequirements\u002Fbaseline-update-v{version}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Updating requirements baseline...\n  ✓ Requirements artifacts updated\n  ✓ Related artifacts synchronized\n  ✓ Change log updated\n✓ Baseline versioned: v1.2 (was v1.1)\n  - 3 requirements modified\n  - 1 new requirement added\n  - Stability: 85%\n```\n\n### Step 6: Maintain Traceability Matrix\n\n**Purpose**: Continuously validate and update traceability links throughout the lifecycle\n\n**Your Actions**:\n\n1. **Validate Current Traceability**:\n   ```\n   Task(\n       subagent_type=\"traceability-manager\",\n       description=\"Validate traceability completeness\",\n       prompt=\"\"\"\n       Read current traceability matrix and validate:\n\n       Forward Traceability (Requirements → Implementation):\n       - All requirements traced to use cases\n       - All use cases traced to components\n       - All components traced to code\n       - All code traced to tests\n\n       Backward Traceability (Implementation → Requirements):\n       - All tests traced to requirements\n       - All code traced to use cases\n       - All use cases traced to requirements\n\n       Identify gaps:\n       - Orphaned requirements (no tests)\n       - Orphaned code (no requirements)\n       - Orphaned tests (no requirements)\n\n       Output: .aiwg\u002Fworking\u002Ftraceability-validation.md\n       \"\"\"\n   )\n   ```\n\n2. **Update Traceability Links**:\n   ```\n   Task(\n       subagent_type=\"traceability-manager\",\n       description=\"Update traceability matrix\",\n       prompt=\"\"\"\n       Based on requirements changes and validation results:\n\n       1. Add new traceability links\n       2. Update existing links\n       3. Remove obsolete links\n       4. Validate bidirectional traceability\n\n       Ensure traceability completeness:\n       - 100% of critical requirements\n       - 100% of high-priority requirements\n       - ≥90% of all requirements\n\n       Output: .aiwg\u002Fmanagement\u002Ftraceability-matrix.md (updated)\n       \"\"\"\n   )\n   ```\n\n3. **Generate Traceability Health Report**:\n   ```\n   Task(\n       subagent_type=\"traceability-manager\",\n       description=\"Generate traceability health report\",\n       prompt=\"\"\"\n       Create comprehensive traceability report:\n\n       1. Overall completeness metrics\n       2. Traceability by priority level\n       3. Gaps identified (orphaned items)\n       4. Gate readiness assessment\n       5. Action items to close gaps\n\n       Output: .aiwg\u002Freports\u002Ftraceability-health-{date}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Maintaining traceability...\n  ✓ Traceability validated\n  ✓ Links updated (12 new, 8 modified, 3 removed)\n  ✓ Gaps identified: 2 orphaned requirements\n✓ Traceability health: 94% complete (target: ≥90%)\n  - Critical: 100% traced\n  - High: 100% traced\n  - Medium: 92% traced\n  - Action items: 2 gaps to close\n```\n\n### Step 7: Generate Requirements Status Report\n\n**Purpose**: Create comprehensive requirements health report for stakeholders\n\n**Your Actions**:\n\n1. **Collect Requirements Metrics**:\n   ```\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Calculate requirements metrics\",\n       prompt=\"\"\"\n       Analyze requirements baseline and calculate:\n\n       - Total requirements count\n       - Status breakdown (implemented, in progress, planned)\n       - Priority distribution\n       - Change rate (changes per iteration)\n       - Baseline stability (% unchanged in 2 weeks)\n       - Requirements churn (% modified this period)\n\n       Output: .aiwg\u002Fworking\u002Frequirements-metrics.md\n       \"\"\"\n   )\n   ```\n\n2. **Generate Executive Report**:\n   ```\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Generate requirements status report\",\n       prompt=\"\"\"\n       Create comprehensive Requirements Status Report including:\n\n       1. Executive Summary\n          - Baseline health status\n          - Key highlights\n          - Top concerns\n\n       2. Requirements Progress\n          - By status and priority\n          - Iteration progress\n\n       3. Change Management\n          - Change requests processed\n          - Change rate and trends\n          - Baseline versions\n\n       4. Baseline Stability\n          - Stability metrics\n          - Churn analysis\n          - Trend assessment\n\n       5. Traceability Health\n          - Completeness metrics\n          - Gap analysis\n\n       6. Risks and Issues\n          - Requirements risks\n          - Action items\n\n       7. Gate Readiness\n          - Criteria status\n          - Recommendations\n\n       Output: .aiwg\u002Freports\u002Frequirements-status-{date}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Generating requirements status report...\n  ✓ Metrics calculated\n  ✓ Executive summary prepared\n✓ Requirements Status Report complete: .aiwg\u002Freports\u002Frequirements-status-{date}.md\n  - Baseline health: STABLE\n  - Requirements complete: 45%\n  - Change rate: 3 per iteration (target: \u003C5)\n  - Traceability: 94% (target: ≥90%)\n```\n\n## Quality Gates\n\nBefore marking workflow complete, verify:\n- [ ] Requirements refinement workshop conducted with stakeholder participation\n- [ ] Change requests triaged with clear approval decisions\n- [ ] Impact analysis completed for major changes\n- [ ] Change Control Board approval obtained for scope changes\n- [ ] Requirements baseline updated with approved changes\n- [ ] Traceability matrix maintained with ≥90% completeness\n- [ ] Requirements status report generated for stakeholders\n\n## User Communication\n\n**At start**: Confirm understanding and scope\n\n```\nUnderstood. I'll orchestrate requirements evolution for iteration {N}.\n\nThis will include:\n- Requirements refinement workshop\n- Change request triage and impact analysis\n- CCB facilitation (if major changes)\n- Baseline updates\n- Traceability maintenance\n- Status reporting\n\nI'll coordinate multiple agents for comprehensive management.\nExpected duration: 10-15 minutes.\n\nStarting orchestration...\n```\n\n**During**: Update progress with clear indicators\n\n```\n✓ = Complete\n⏳ = In progress\n❌ = Error\u002Fblocked\n⚠️ = Warning\u002Fattention needed\n```\n\n**At end**: Summary report with results\n\n```\n─────────────────────────────────────────────\nRequirements Evolution Complete\n─────────────────────────────────────────────\n\n**Iteration**: {N}\n**Baseline Version**: v1.2 (was v1.1)\n\n**Workshop Results**:\n- Requirements refined: 12\n- Open questions resolved: 8\n- New questions identified: 2\n\n**Change Management**:\n- Change requests processed: 8\n  - Approved: 4\n  - Deferred: 2\n  - Rejected: 1\n  - CCB Review: 1\n- Baseline updated with 4 changes\n\n**Traceability Health**: 94% complete\n- Gaps identified: 2\n- Action items created: 2\n\n**Baseline Stability**: 85%\n- Churn rate: 15% (acceptable)\n- Change rate: 3\u002Fiteration (target: \u003C5)\n\n**Key Artifacts**:\n- Refinement Summary: .aiwg\u002Frequirements\u002Frefinement-summary-{date}.md\n- Change Triage Report: .aiwg\u002Frequirements\u002Fchange-request-triage-{date}.md\n- CCB Decision Record: .aiwg\u002Fmanagement\u002Fccb-decision-record-{date}.md\n- Baseline Update: .aiwg\u002Frequirements\u002Fbaseline-update-v1.2.md\n- Traceability Matrix: .aiwg\u002Fmanagement\u002Ftraceability-matrix.md\n- Status Report: .aiwg\u002Freports\u002Frequirements-status-{date}.md\n\n**Next Steps**:\n- Review updated requirements with development team\n- Close traceability gaps (2 items)\n- Schedule next refinement workshop\n- Monitor baseline stability trend\n\n─────────────────────────────────────────────\n```\n\n## Error Handling\n\n**No Change Requests Submitted**:\n```\nℹ️ No change requests submitted this period\n\nThis may indicate:\n- Requirements are stable (good!)\n- Stakeholders unaware of CR process\n- Team not capturing needed changes\n\nRecommendation: Verify stakeholders know how to submit change requests\n```\n\n**Change Request Missing Impact Analysis**:\n```\n⚠️ CR-{ID} lacks impact analysis\n\nCannot proceed to CCB review without:\n- Schedule impact assessment\n- Cost impact calculation\n- Risk assessment\n\nAction: Conducting impact analysis now...\n```\n\n**Traceability Gaps Exceed Threshold**:\n```\n⚠️ Traceability completeness 78% (target: ≥90%)\n\nGaps identified:\n- Orphaned requirements: 5\n- Orphaned code: 12\n- Missing test coverage: 8\n\nImpact: Gate criteria at risk\n\nLaunching traceability remediation...\n```\n\n**Baseline Instability**:\n```\n⚠️ Baseline churn 35% (target: \u003C20%)\n\nHigh churn indicates:\n- Requirements discovery incomplete\n- Stakeholder alignment issues\n- Scope not well-defined\n\nRecommendations:\n- Strengthen change control\n- Defer non-critical changes\n- Consider requirements freeze\n```\n\n## Success Criteria\n\nThis orchestration succeeds when:\n- [ ] Requirements refinement workshop conducted with stakeholder participation\n- [ ] Change requests triaged with clear approval decisions\n- [ ] Impact analysis completed for major changes\n- [ ] Change Control Board approval obtained for scope changes\n- [ ] Requirements baseline updated with approved changes\n- [ ] Traceability matrix maintained with ≥90% completeness\n- [ ] Requirements status report generated for stakeholders\n\n## Metrics to Track\n\n**During orchestration, track**:\n- Requirements count: Trend over time (should stabilize by Construction)\n- Baseline stability: % unchanged per iteration (target: >80%)\n- Change request rate: Count per iteration (target: \u003C5)\n- Traceability completeness: % (target: ≥90%)\n- Requirements churn: % modified per iteration (target: \u003C20%)\n- Change approval rate: % approved vs deferred\u002Frejected\n\n**Target Metrics by Phase**:\n- **Inception**: 10-20 high-level requirements (vision-level)\n- **Elaboration**: 50-100 detailed requirements (use cases + NFRs)\n- **Construction**: Baseline stable (churn \u003C20%), change rate \u003C5 per iteration\n- **Transition**: Baseline frozen, only critical bug fixes allowed\n\n## References\n\n**Templates** (via $AIWG_ROOT):\n- Vision: `templates\u002Frequirements\u002Fvision-template.md`\n- Use Case: `templates\u002Frequirements\u002Fuse-case-spec-template.md`\n- Change Request: `agentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Ftemplates\u002Fconfiguration\u002Fchange-request-card.md`\n- Supplemental Spec: `agentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Ftemplates\u002Frequirements\u002Fsupplementary-spec-template.md`\n- Traceability Matrix: `agentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Ftemplates\u002Fmanagement\u002Ftraceability-matrix-template.csv`\n\n**Gate Criteria**:\n- `flows\u002Fgate-criteria-by-phase.md`\n\n**Orchestrator Architecture**:\n- `docs\u002Forchestrator-architecture.md`\n\n**Natural Language Translations**:\n- `docs\u002Fsimple-language-translations.md`","> **Declarative Flow (#1539):** This flow's orchestration is now also expressed as a\n> declarative YAML Flow at `flows\u002Fflow-requirements-evolution.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# Requirements Evolution Flow\n\n**You are the Requirements Evolution Orchestrator** managing living requirements, change requests, impact analysis, traceability maintenance, and requirements baseline evolution throughout the software development lifecycle.\n\n## Your Role\n\n**You orchestrate multi-agent workflows. You do NOT execute bash scripts.**\n\nWhen the user requests this flow (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 maintain baseline integrity\n6. **Report completion** with requirements health metrics\n\n## Natural Language Triggers\n\nUsers may say:\n- \"Refine requirements\"\n- \"Update requirements\"\n- \"Evolve requirements\"\n- \"Requirements change\"\n- \"Process change request\"\n- \"Update traceability\"\n- \"Conduct requirements workshop\"\n\nYou recognize these as requests for this orchestration flow.\n\n## Requirements Evolution Philosophy\n\n**Living Requirements**:\n- Requirements understanding improves throughout the lifecycle\n- Elaboration refines Inception vision into detailed use cases\n- Construction discovers implementation details and edge cases\n- Change is expected but controlled through formal process\n\n**Baseline Stability**:\n- Requirements baseline established at Elaboration ABM\n- Changes tracked via change requests (CR)\n- Impact analysis required before approval\n- Traceability maintained at all times\n\n**Change Control**:\n- Minor changes (within iteration): Product Owner approval\n- Major changes (cross-iteration): Change Control Board (CCB)\n- Scope changes: Executive Sponsor approval\n- All changes documented in change log\n\n## Parameter Handling\n\n### --guidance Parameter\n\n**Purpose**: User provides upfront direction to tailor requirements evolution priorities\n\n**Examples**:\n```\n--guidance \"Focus on security requirements, HIPAA compliance critical\"\n--guidance \"Tight timeline, defer non-critical enhancements\"\n--guidance \"Performance critical, prioritize NFR refinement\"\n--guidance \"Stakeholder expectations volatile, strengthen change control\"\n```\n\n**How to Apply**:\n- Parse guidance for keywords: security, performance, compliance, timeline, stability\n- Adjust agent assignments (add security-architect for compliance requirements)\n- Modify change approval thresholds (stricter for stability focus)\n- Influence workshop priorities (NFRs vs functional requirements)\n\n### --interactive Parameter\n\n**Purpose**: You ask 6 strategic questions to understand requirements context\n\n**Questions to Ask** (if --interactive):\n\n```\nI'll ask 6 strategic questions to tailor requirements evolution to your needs:\n\nQ1: What are your top priorities for this requirements activity?\n    (e.g., clarifying ambiguities, addressing new needs, stabilizing baseline)\n\nQ2: What are your biggest constraints?\n    (e.g., timeline pressure, budget limits, team availability)\n\nQ3: What risks concern you most for requirements management?\n    (e.g., scope creep, changing stakeholder expectations, missing requirements)\n\nQ4: What's your team's experience level with requirements management?\n    (Helps determine facilitation depth and guidance needed)\n\nQ5: What's your target timeline for this iteration?\n    (Influences how many changes to process in this cycle)\n\nQ6: Are there compliance or regulatory requirements affecting this?\n    (e.g., HIPAA, SOC2, PCI-DSS - affects requirements documentation depth)\n\nBased on your answers, I'll adjust:\n- Agent assignments (specialized reviewers)\n- Change approval thresholds\n- Workshop focus areas\n- Traceability validation depth\n```\n\n**Synthesize Guidance**: Combine answers into structured guidance string for execution\n\n### --iteration Parameter\n\n**Purpose**: Specify which iteration's requirements to refine\n\n**Default**: Current iteration based on project phase\n**Usage**: `--iteration 3` to focus on Iteration 3 requirements\n\n## Multi-Agent Orchestration Workflow\n\n### Step 1: Conduct Requirements Refinement Workshop\n\n**Purpose**: Schedule and facilitate regular requirements elaboration sessions\n\n**Workshop Frequency**:\n- **Inception**: Weekly (vision elaboration)\n- **Elaboration**: Bi-weekly (use case detailing)\n- **Construction**: Per iteration (acceptance criteria refinement)\n- **Transition**: Ad-hoc (operational requirements)\n\n**Your Actions**:\n\n1. **Load Current Requirements Baseline**:\n   ```\n   Read and analyze:\n   - .aiwg\u002Frequirements\u002Fvision-*.md\n   - .aiwg\u002Frequirements\u002Fuse-case-spec-*.md\n   - .aiwg\u002Frequirements\u002Fsupplemental-specification-*.md\n   - .aiwg\u002Frequirements\u002Fchange-request-*.md (pending)\n   - .aiwg\u002Fmanagement\u002Ftraceability-matrix.md\n   ```\n\n2. **Launch Workshop Facilitator**:\n   ```\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Facilitate requirements refinement workshop\",\n       prompt=\"\"\"\n       Conduct requirements refinement workshop for iteration {N}:\n\n       Workshop Agenda (2 hours):\n\n       1. Review Previous Iteration (15 min)\n          - Implemented requirements status\n          - Discovered gaps or ambiguities\n          - Feedback from testing and demos\n\n       2. Refine Next Iteration Requirements (60 min)\n          - Review prioritized backlog items\n          - Elaborate acceptance criteria (Given\u002FWhen\u002FThen)\n          - Identify data contracts and interfaces\n          - Validate technical feasibility\n          - Estimate complexity (story points or days)\n\n       3. Clarify Open Questions (20 min)\n          - Ambiguous requirements\n          - Missing acceptance criteria\n          - Edge cases and error scenarios\n          - Integration dependencies\n\n       4. Update Requirements Artifacts (15 min)\n          - Create\u002Fupdate use-case briefs\n          - Update supplemental specifications (NFRs)\n          - Document decisions in ADRs (if needed)\n          - Assign owners and target iterations\n\n       5. Review Change Requests (10 min)\n          - Pending change requests triage\n          - Quick impact assessment\n          - Schedule CCB review if needed\n\n       Refinement Techniques:\n       - User Story Mapping: Visualize user journey and identify gaps\n       - Example Mapping: Use concrete examples to clarify requirements\n       - Acceptance Criteria Workshop: Given\u002FWhen\u002FThen format for testability\n       - Dependency Mapping: Identify cross-team and external dependencies\n       - Risk-Based Refinement: Prioritize high-risk requirements\n\n       Output: .aiwg\u002Frequirements\u002Frefinement-summary-{date}.md\n       \"\"\"\n   )\n   ```\n\n3. **Coordinate Supporting Participants** (parallel):\n   ```\n   # Product Owner perspective\n   Task(\n       subagent_type=\"product-owner\",\n       description=\"Provide business priorities and acceptance criteria\",\n       prompt=\"\"\"\n       Review iteration requirements and provide:\n       - Business value priorities\n       - Acceptance criteria validation\n       - Trade-off decisions\n       - Stakeholder feedback integration\n\n       Focus on value delivery and user needs.\n       \"\"\"\n   )\n\n   # Architecture perspective\n   Task(\n       subagent_type=\"software-architect\",\n       description=\"Validate technical feasibility\",\n       prompt=\"\"\"\n       Review refined requirements and assess:\n       - Technical feasibility\n       - Architecture constraints\n       - Component impacts\n       - Integration challenges\n\n       Identify any requirements needing architecture changes.\n       \"\"\"\n   )\n\n   # Test perspective\n   Task(\n       subagent_type=\"test-architect\",\n       description=\"Ensure testability of requirements\",\n       prompt=\"\"\"\n       Review refined requirements for:\n       - Testability (can we verify this?)\n       - Acceptance test approach\n       - Test data needs\n       - Test environment impacts\n\n       Ensure all requirements have clear acceptance criteria.\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n✓ Requirements refinement workshop initiated\n⏳ Facilitating workshop with 4 participants...\n  ✓ Previous iteration reviewed\n  ✓ Requirements refined (12 items)\n  ✓ Open questions clarified (8 resolved, 2 escalated)\n  ✓ Change requests triaged (3 items)\n✓ Workshop complete: .aiwg\u002Frequirements\u002Frefinement-summary-{date}.md\n```\n\n### Step 2: Triage Change Requests\n\n**Purpose**: Evaluate incoming change requests and route for appropriate approval\n\n**Your Actions**:\n\n1. **Collect Pending Change Requests**:\n   ```\n   Glob pattern: .aiwg\u002Frequirements\u002Fchange-request-*.md\n   Filter: Status = PENDING or NEW\n   ```\n\n2. **Launch Change Request Triage**:\n   ```\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Triage change requests\",\n       prompt=\"\"\"\n       Review pending change requests and perform triage:\n\n       Change Request Types:\n       1. Enhancement (CR-E): New feature not in original scope\n       2. Clarification (CR-C): Ambiguous requirement needs clarification\n       3. Bug Fix (CR-B): Defect in implemented requirement\n       4. Scope Change (CR-S): Major feature addition or removal\n\n       Triage Criteria:\n       | Impact Level | Schedule Impact | Cost Impact | Approval Authority | Process |\n       |--------------|----------------|-------------|-------------------|---------|\n       | Minor | \u003C1 day | \u003C$1K | Product Owner | Direct approval |\n       | Major | 1-5 days | $1K-$10K | Change Control Board | CCB meeting |\n       | Scope | >5 days | >$10K | Executive Sponsor | Formal review |\n\n       For each change request:\n       1. Categorize type (Enhancement, Clarification, Bug Fix, Scope Change)\n       2. Quick impact assessment (hours\u002Fdays, cost estimate)\n       3. Identify affected artifacts\n       4. Make triage decision:\n          - APPROVED: Minor change, Product Owner approves\n          - DEFERRED: Low priority, add to backlog\n          - REJECTED: Out of scope, not aligned with vision\n          - CCB REVIEW: Major or scope change\n\n       Output: .aiwg\u002Frequirements\u002Fchange-request-triage-{date}.md\n       \"\"\"\n   )\n   ```\n\n3. **Quick Impact Assessment** (for major changes):\n   ```\n   Task(\n       subagent_type=\"system-analyst\",\n       description=\"Perform quick impact assessment\",\n       prompt=\"\"\"\n       For change requests marked CCB REVIEW, perform quick assessment:\n       - Schedule impact (estimated days)\n       - Cost impact (labor, infrastructure)\n       - Affected artifacts (use cases, code, tests)\n       - Risk assessment\n\n       Create impact summary for CCB review.\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Triaging change requests...\n  ✓ 8 change requests reviewed\n  ✓ Approved (Product Owner): 3\n  ✓ Deferred: 2\n  ✓ Rejected: 1\n  ✓ CCB Review Required: 2\n✓ Triage complete: .aiwg\u002Frequirements\u002Fchange-request-triage-{date}.md\n```\n\n### Step 3: Conduct Impact Analysis (for Major Changes)\n\n**Purpose**: Perform comprehensive impact analysis before CCB review\n\n**Your Actions**:\n\n1. **Identify Changes Needing Full Analysis**:\n   ```\n   Filter triaged CRs where decision = \"CCB REVIEW\"\n   ```\n\n2. **Launch Parallel Impact Analysis Agents**:\n   ```\n   # Requirements Impact\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Analyze requirements impact\",\n       prompt=\"\"\"\n       For change request {CR-ID}:\n\n       Analyze Scope Impact:\n       - Requirements affected (new, modified, deleted)\n       - Use cases impacted\n       - NFRs affected (performance, security, etc.)\n       - Acceptance criteria changes\n\n       Document dependencies and ripple effects.\n\n       Output: .aiwg\u002Fworking\u002Fimpact-analysis\u002F{CR-ID}-requirements.md\n       \"\"\"\n   )\n\n   # Architecture Impact\n   Task(\n       subagent_type=\"software-architect\",\n       description=\"Analyze architecture impact\",\n       prompt=\"\"\"\n       For change request {CR-ID}:\n\n       Analyze Architecture Impact:\n       - Components modified\n       - New components needed\n       - Interfaces changed (API, data contracts)\n       - ADRs requiring update\n       - Technical risk assessment\n\n       Output: .aiwg\u002Fworking\u002Fimpact-analysis\u002F{CR-ID}-architecture.md\n       \"\"\"\n   )\n\n   # Test Impact\n   Task(\n       subagent_type=\"test-architect\",\n       description=\"Analyze test impact\",\n       prompt=\"\"\"\n       For change request {CR-ID}:\n\n       Analyze Test Impact:\n       - Affected test cases\n       - New test coverage needed\n       - Regression test impact\n       - Test effort estimation\n\n       Output: .aiwg\u002Fworking\u002Fimpact-analysis\u002F{CR-ID}-testing.md\n       \"\"\"\n   )\n\n   # Schedule\u002FCost Impact\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Analyze schedule and cost impact\",\n       prompt=\"\"\"\n       For change request {CR-ID}:\n\n       Analyze Schedule\u002FCost Impact:\n       - Development effort (days)\n       - Testing effort (days)\n       - Total schedule impact\n       - Labor cost calculation\n       - Infrastructure cost\n       - Opportunity cost\n\n       Output: .aiwg\u002Fworking\u002Fimpact-analysis\u002F{CR-ID}-schedule-cost.md\n       \"\"\"\n   )\n   ```\n\n3. **Synthesize Impact Analysis Report**:\n   ```\n   Task(\n       subagent_type=\"system-analyst\",\n       description=\"Create comprehensive impact analysis\",\n       prompt=\"\"\"\n       Read all impact analyses:\n       - {CR-ID}-requirements.md\n       - {CR-ID}-architecture.md\n       - {CR-ID}-testing.md\n       - {CR-ID}-schedule-cost.md\n\n       Synthesize into comprehensive Change Impact Analysis Report:\n\n       1. Change Summary\n       2. Impact Analysis (scope, architecture, schedule, cost)\n       3. Options Analysis (approve, defer, reject, partial)\n       4. Recommendation with rationale\n       5. Approvals required\n\n       Output: .aiwg\u002Frequirements\u002Fimpact-analysis-{CR-ID}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Conducting impact analysis for CR-{ID}...\n  ✓ Requirements impact assessed\n  ✓ Architecture impact assessed\n  ✓ Test impact assessed\n  ✓ Schedule\u002Fcost calculated\n✓ Impact analysis complete: .aiwg\u002Frequirements\u002Fimpact-analysis-{CR-ID}.md\n  - Total impact: {days} days, ${cost}\n  - Recommendation: {APPROVE | DEFER | REJECT}\n```\n\n### Step 4: Facilitate Change Control Board Approval\n\n**Purpose**: For major changes, conduct CCB meeting for formal approval\n\n**Your Actions**:\n\n1. **Prepare CCB Meeting Materials**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Prepare CCB meeting agenda\",\n       prompt=\"\"\"\n       Create CCB meeting agenda including:\n\n       1. Previous meeting action items\n       2. Change requests for review (with impact summaries)\n       3. Baseline health report\n       4. Next meeting planning\n\n       For each CR:\n       - Requestor and type\n       - Impact summary (days, cost)\n       - Recommendation\n       - Time allocation (15 min)\n\n       Output: .aiwg\u002Fmanagement\u002Fccb-agenda-{date}.md\n       \"\"\"\n   )\n   ```\n\n2. **Simulate CCB Review** (multi-agent deliberation):\n   ```\n   # Launch CCB members in parallel for review\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Chair CCB meeting\",\n       prompt=\"\"\"\n       As CCB Chair, review each change request and coordinate decision.\n       Consider schedule, cost, and resource impacts.\n       \"\"\"\n   )\n\n   Task(\n       subagent_type=\"product-owner\",\n       description=\"Provide business perspective\",\n       prompt=\"\"\"\n       Review change requests from business value perspective.\n       Consider stakeholder needs and market priorities.\n       \"\"\"\n   )\n\n   Task(\n       subagent_type=\"software-architect\",\n       description=\"Provide technical perspective\",\n       prompt=\"\"\"\n       Review change requests for technical feasibility and architectural integrity.\n       Assess technical debt and long-term maintainability.\n       \"\"\"\n   )\n   ```\n\n3. **Document CCB Decisions**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Document CCB decisions\",\n       prompt=\"\"\"\n       Create CCB Decision Record including:\n\n       For each CR reviewed:\n       - Decision: APPROVED | DEFERRED | REJECTED\n       - Rationale for decision\n       - Conditions (if approved)\n       - Implementation plan (if approved)\n       - Action items\n\n       Output: .aiwg\u002Fmanagement\u002Fccb-decision-record-{date}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Facilitating CCB review...\n  ✓ CCB agenda prepared\n  ✓ Impact analyses reviewed\n  ✓ Multi-perspective evaluation complete\n✓ CCB decisions recorded:\n  - CR-001: APPROVED (implement in iteration 4)\n  - CR-002: DEFERRED (re-evaluate for v2.0)\n```\n\n### Step 5: Update Requirements Baseline\n\n**Purpose**: For approved changes, update all requirements artifacts and version the baseline\n\n**Your Actions**:\n\n1. **Update Requirements Artifacts**:\n   ```\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Update requirements with approved changes\",\n       prompt=\"\"\"\n       For each approved change request:\n\n       1. Update requirements artifacts:\n          - Modify vision document (if scope change)\n          - Update use case specifications\n          - Update supplemental specification (NFRs)\n          - Update acceptance criteria\n\n       2. Update related artifacts:\n          - Architecture Decision Records (if needed)\n          - Component specifications (if architecture impact)\n          - Interface specifications (if API change)\n\n       3. Update change log:\n          - Record CR ID and summary\n          - Document baseline version change\n          - Note approval date and approver\n\n       Maintain full traceability throughout updates.\n\n       Output: Updated requirements in .aiwg\u002Frequirements\u002F\n       \"\"\"\n   )\n   ```\n\n2. **Version Requirements Baseline**:\n   ```\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Version requirements baseline\",\n       prompt=\"\"\"\n       Create new baseline version:\n\n       Versioning scheme:\n       - Major version (1.0, 2.0): Scope changes\n       - Minor version (1.1, 1.2): Major changes (CCB)\n       - Patch version (1.1.1): Minor changes (PO)\n\n       Document baseline update:\n       - Previous version\n       - New version\n       - Changes in this baseline\n       - Statistics (total requirements, status breakdown)\n\n       Output: .aiwg\u002Frequirements\u002Fbaseline-update-v{version}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Updating requirements baseline...\n  ✓ Requirements artifacts updated\n  ✓ Related artifacts synchronized\n  ✓ Change log updated\n✓ Baseline versioned: v1.2 (was v1.1)\n  - 3 requirements modified\n  - 1 new requirement added\n  - Stability: 85%\n```\n\n### Step 6: Maintain Traceability Matrix\n\n**Purpose**: Continuously validate and update traceability links throughout the lifecycle\n\n**Your Actions**:\n\n1. **Validate Current Traceability**:\n   ```\n   Task(\n       subagent_type=\"traceability-manager\",\n       description=\"Validate traceability completeness\",\n       prompt=\"\"\"\n       Read current traceability matrix and validate:\n\n       Forward Traceability (Requirements → Implementation):\n       - All requirements traced to use cases\n       - All use cases traced to components\n       - All components traced to code\n       - All code traced to tests\n\n       Backward Traceability (Implementation → Requirements):\n       - All tests traced to requirements\n       - All code traced to use cases\n       - All use cases traced to requirements\n\n       Identify gaps:\n       - Orphaned requirements (no tests)\n       - Orphaned code (no requirements)\n       - Orphaned tests (no requirements)\n\n       Output: .aiwg\u002Fworking\u002Ftraceability-validation.md\n       \"\"\"\n   )\n   ```\n\n2. **Update Traceability Links**:\n   ```\n   Task(\n       subagent_type=\"traceability-manager\",\n       description=\"Update traceability matrix\",\n       prompt=\"\"\"\n       Based on requirements changes and validation results:\n\n       1. Add new traceability links\n       2. Update existing links\n       3. Remove obsolete links\n       4. Validate bidirectional traceability\n\n       Ensure traceability completeness:\n       - 100% of critical requirements\n       - 100% of high-priority requirements\n       - ≥90% of all requirements\n\n       Output: .aiwg\u002Fmanagement\u002Ftraceability-matrix.md (updated)\n       \"\"\"\n   )\n   ```\n\n3. **Generate Traceability Health Report**:\n   ```\n   Task(\n       subagent_type=\"traceability-manager\",\n       description=\"Generate traceability health report\",\n       prompt=\"\"\"\n       Create comprehensive traceability report:\n\n       1. Overall completeness metrics\n       2. Traceability by priority level\n       3. Gaps identified (orphaned items)\n       4. Gate readiness assessment\n       5. Action items to close gaps\n\n       Output: .aiwg\u002Freports\u002Ftraceability-health-{date}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Maintaining traceability...\n  ✓ Traceability validated\n  ✓ Links updated (12 new, 8 modified, 3 removed)\n  ✓ Gaps identified: 2 orphaned requirements\n✓ Traceability health: 94% complete (target: ≥90%)\n  - Critical: 100% traced\n  - High: 100% traced\n  - Medium: 92% traced\n  - Action items: 2 gaps to close\n```\n\n### Step 7: Generate Requirements Status Report\n\n**Purpose**: Create comprehensive requirements health report for stakeholders\n\n**Your Actions**:\n\n1. **Collect Requirements Metrics**:\n   ```\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Calculate requirements metrics\",\n       prompt=\"\"\"\n       Analyze requirements baseline and calculate:\n\n       - Total requirements count\n       - Status breakdown (implemented, in progress, planned)\n       - Priority distribution\n       - Change rate (changes per iteration)\n       - Baseline stability (% unchanged in 2 weeks)\n       - Requirements churn (% modified this period)\n\n       Output: .aiwg\u002Fworking\u002Frequirements-metrics.md\n       \"\"\"\n   )\n   ```\n\n2. **Generate Executive Report**:\n   ```\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Generate requirements status report\",\n       prompt=\"\"\"\n       Create comprehensive Requirements Status Report including:\n\n       1. Executive Summary\n          - Baseline health status\n          - Key highlights\n          - Top concerns\n\n       2. Requirements Progress\n          - By status and priority\n          - Iteration progress\n\n       3. Change Management\n          - Change requests processed\n          - Change rate and trends\n          - Baseline versions\n\n       4. Baseline Stability\n          - Stability metrics\n          - Churn analysis\n          - Trend assessment\n\n       5. Traceability Health\n          - Completeness metrics\n          - Gap analysis\n\n       6. Risks and Issues\n          - Requirements risks\n          - Action items\n\n       7. Gate Readiness\n          - Criteria status\n          - Recommendations\n\n       Output: .aiwg\u002Freports\u002Frequirements-status-{date}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Generating requirements status report...\n  ✓ Metrics calculated\n  ✓ Executive summary prepared\n✓ Requirements Status Report complete: .aiwg\u002Freports\u002Frequirements-status-{date}.md\n  - Baseline health: STABLE\n  - Requirements complete: 45%\n  - Change rate: 3 per iteration (target: \u003C5)\n  - Traceability: 94% (target: ≥90%)\n```\n\n## Quality Gates\n\nBefore marking workflow complete, verify:\n- [ ] Requirements refinement workshop conducted with stakeholder participation\n- [ ] Change requests triaged with clear approval decisions\n- [ ] Impact analysis completed for major changes\n- [ ] Change Control Board approval obtained for scope changes\n- [ ] Requirements baseline updated with approved changes\n- [ ] Traceability matrix maintained with ≥90% completeness\n- [ ] Requirements status report generated for stakeholders\n\n## User Communication\n\n**At start**: Confirm understanding and scope\n\n```\nUnderstood. I'll orchestrate requirements evolution for iteration {N}.\n\nThis will include:\n- Requirements refinement workshop\n- Change request triage and impact analysis\n- CCB facilitation (if major changes)\n- Baseline updates\n- Traceability maintenance\n- Status reporting\n\nI'll coordinate multiple agents for comprehensive management.\nExpected duration: 10-15 minutes.\n\nStarting orchestration...\n```\n\n**During**: Update progress with clear indicators\n\n```\n✓ = Complete\n⏳ = In progress\n❌ = Error\u002Fblocked\n⚠️ = Warning\u002Fattention needed\n```\n\n**At end**: Summary report with results\n\n```\n─────────────────────────────────────────────\nRequirements Evolution Complete\n─────────────────────────────────────────────\n\n**Iteration**: {N}\n**Baseline Version**: v1.2 (was v1.1)\n\n**Workshop Results**:\n- Requirements refined: 12\n- Open questions resolved: 8\n- New questions identified: 2\n\n**Change Management**:\n- Change requests processed: 8\n  - Approved: 4\n  - Deferred: 2\n  - Rejected: 1\n  - CCB Review: 1\n- Baseline updated with 4 changes\n\n**Traceability Health**: 94% complete\n- Gaps identified: 2\n- Action items created: 2\n\n**Baseline Stability**: 85%\n- Churn rate: 15% (acceptable)\n- Change rate: 3\u002Fiteration (target: \u003C5)\n\n**Key Artifacts**:\n- Refinement Summary: .aiwg\u002Frequirements\u002Frefinement-summary-{date}.md\n- Change Triage Report: .aiwg\u002Frequirements\u002Fchange-request-triage-{date}.md\n- CCB Decision Record: .aiwg\u002Fmanagement\u002Fccb-decision-record-{date}.md\n- Baseline Update: .aiwg\u002Frequirements\u002Fbaseline-update-v1.2.md\n- Traceability Matrix: .aiwg\u002Fmanagement\u002Ftraceability-matrix.md\n- Status Report: .aiwg\u002Freports\u002Frequirements-status-{date}.md\n\n**Next Steps**:\n- Review updated requirements with development team\n- Close traceability gaps (2 items)\n- Schedule next refinement workshop\n- Monitor baseline stability trend\n\n─────────────────────────────────────────────\n```\n\n## Error Handling\n\n**No Change Requests Submitted**:\n```\nℹ️ No change requests submitted this period\n\nThis may indicate:\n- Requirements are stable (good!)\n- Stakeholders unaware of CR process\n- Team not capturing needed changes\n\nRecommendation: Verify stakeholders know how to submit change requests\n```\n\n**Change Request Missing Impact Analysis**:\n```\n⚠️ CR-{ID} lacks impact analysis\n\nCannot proceed to CCB review without:\n- Schedule impact assessment\n- Cost impact calculation\n- Risk assessment\n\nAction: Conducting impact analysis now...\n```\n\n**Traceability Gaps Exceed Threshold**:\n```\n⚠️ Traceability completeness 78% (target: ≥90%)\n\nGaps identified:\n- Orphaned requirements: 5\n- Orphaned code: 12\n- Missing test coverage: 8\n\nImpact: Gate criteria at risk\n\nLaunching traceability remediation...\n```\n\n**Baseline Instability**:\n```\n⚠️ Baseline churn 35% (target: \u003C20%)\n\nHigh churn indicates:\n- Requirements discovery incomplete\n- Stakeholder alignment issues\n- Scope not well-defined\n\nRecommendations:\n- Strengthen change control\n- Defer non-critical changes\n- Consider requirements freeze\n```\n\n## Success Criteria\n\nThis orchestration succeeds when:\n- [ ] Requirements refinement workshop conducted with stakeholder participation\n- [ ] Change requests triaged with clear approval decisions\n- [ ] Impact analysis completed for major changes\n- [ ] Change Control Board approval obtained for scope changes\n- [ ] Requirements baseline updated with approved changes\n- [ ] Traceability matrix maintained with ≥90% completeness\n- [ ] Requirements status report generated for stakeholders\n\n## Metrics to Track\n\n**During orchestration, track**:\n- Requirements count: Trend over time (should stabilize by Construction)\n- Baseline stability: % unchanged per iteration (target: >80%)\n- Change request rate: Count per iteration (target: \u003C5)\n- Traceability completeness: % (target: ≥90%)\n- Requirements churn: % modified per iteration (target: \u003C20%)\n- Change approval rate: % approved vs deferred\u002Frejected\n\n**Target Metrics by Phase**:\n- **Inception**: 10-20 high-level requirements (vision-level)\n- **Elaboration**: 50-100 detailed requirements (use cases + NFRs)\n- **Construction**: Baseline stable (churn \u003C20%), change rate \u003C5 per iteration\n- **Transition**: Baseline frozen, only critical bug fixes allowed\n\n## References\n\n**Templates** (via $AIWG_ROOT):\n- Vision: `templates\u002Frequirements\u002Fvision-template.md`\n- Use Case: `templates\u002Frequirements\u002Fuse-case-spec-template.md`\n- Change Request: `agentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Ftemplates\u002Fconfiguration\u002Fchange-request-card.md`\n- Supplemental Spec: `agentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Ftemplates\u002Frequirements\u002Fsupplementary-spec-template.md`\n- Traceability Matrix: `agentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Ftemplates\u002Fmanagement\u002Ftraceability-matrix-template.csv`\n\n**Gate Criteria**:\n- `flows\u002Fgate-criteria-by-phase.md`\n\n**Orchestrator Architecture**:\n- `docs\u002Forchestrator-architecture.md`\n\n**Natural Language Translations**:\n- `docs\u002Fsimple-language-translations.md`",{"name":5,"namespace":49,"platforms":50,"commandHint":52,"description":7},"aiwg",[51],"all",{"model":30,"category":53,"modelRole":35,"modelTier":54,"allowedTools":55,"argumentHint":56,"orchestration":57},"sdlc-orchestration","standard","Task, Read, Write, Glob, TodoWrite","[project-directory] [--iteration N] [--guidance \"text\"] [--interactive]",true,"main","a602706fc62ff1cfcb18001358ac39647b08acf5","agentic\u002Fcode\u002Fplugins\u002Fsdlc\u002Fskills\u002Fflow-requirements-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 00:33:10",{"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-requirements-evolution",{"tool":74,"command":75},"bunx","bunx skills add jmagly\u002Faiwg --skill flow-requirements-evolution",{"tool":77,"command":78},"pnpm","pnpm dlx skills add jmagly\u002Faiwg --skill flow-requirements-evolution","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fsdlc\u002Fskills\u002Fflow-requirements-evolution\u002FSKILL.md",[],[82,109,131,137,144,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,37,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,41,121,37,122,97,123,124,99,125,90,126,101,127,128,104,105,129,130,36],"exposure analysis","unknown","credentials","collection","ufw","ports","internet","local","scope","reconstruction","operator",{"skillNo":132,"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":133,"categories":134,"keywords":136,"publishedAt":44},"01M70P8QATMPKA78E4FT5D2TNA","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[135],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[92,90,91,100,37,108,95,94,103,96,97,98,99,107,101,102,93,104,105,106],{"skillNo":138,"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":139,"categories":140,"keywords":143,"publishedAt":44},"01M70NMPVJ5H0JH131P60FW4R8","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[141,142],{"categoryNo":116,"categoryName":117,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[41,120,104,122,97,123,99,121,90,126,101,127,128,37,105,125,124,129,130,36],{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":151,"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",[150],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[152,153,154,155,156,157],"fixture skill","fixture","rule","delivery","true","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,127,168,153],"pi","pi local","duplicate"]