[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CADPJP18EBC5B02RM5W239":3,"skill-same:01M6CADPJP18EBC5B02RM5W239":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},"01M6CADPJP18EBC5B02RM5W239","flow-iteration-dual-track",null,"Orchestrate dual-track iteration with synchronized Discovery (next) and Delivery (current) workflows","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-iteration-dual-track\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 iteration dual track","flow","track","iteration","true","sonnet","delivery","next","number","project","interactive","discovery","coding","write","read","directory","text","orchestration","workflows","orchestrate","2026-11-10 10:12:30",false,"---\nnamespace: aiwg\nname: flow-iteration-dual-track\nplatforms: [all]\ndescription: Orchestrate dual-track iteration with synchronized Discovery (next) and Delivery (current) workflows\ncommandHint:\n  argumentHint: \u003Citeration-number> [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-iteration-dual-track.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# Dual-Track Iteration Flow\n\n**You are the Core Orchestrator** for dual-track agile iteration management.\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 finalize artifacts\n6. **Report completion** with summary\n\n## Dual-Track Overview\n\n**Discovery Track**: Planning iteration N+1 (next iteration's work)\n- Requirements refinement\n- Design elaboration\n- Risk investigation\n- Acceptance criteria definition\n\n**Delivery Track**: Implementing iteration N (current iteration's work)\n- Coding committed stories\n- Testing implementation\n- Integration work\n- Quality assurance\n\n**Key Principle**: Discovery stays 1 iteration ahead to ensure Delivery always has ready backlog.\n\n## Natural Language Triggers\n\nUsers may say:\n- \"Run iteration 3\"\n- \"Start iteration 5\"\n- \"Execute dual-track iteration\"\n- \"Begin next sprint\"\n- \"Start iteration planning\"\n- \"Run sprint 4 with dual tracks\"\n\nYou recognize these as requests for this orchestration flow.\n\n## Parameter Handling\n\n### --guidance Parameter\n\n**Purpose**: User provides upfront direction to tailor iteration priorities\n\n**Examples**:\n```\n--guidance \"Focus on security stories first, compliance audit next week\"\n--guidance \"Performance optimization critical, defer UI polish\"\n--guidance \"Team velocity reduced this sprint, plan conservatively\"\n--guidance \"Integration with payment gateway is blocking, prioritize spikes\"\n```\n\n**How to Apply**:\n- Parse guidance for keywords: security, performance, integration, velocity\n- Adjust Discovery focus (requirements vs. spikes vs. design)\n- Modify Delivery priorities (feature vs. tech debt vs. fixes)\n- Influence synchronization points (more\u002Fless frequent)\n\n### --interactive Parameter\n\n**Purpose**: You ask 5-7 strategic questions to understand iteration context\n\n**Questions to Ask** (if --interactive):\n\n```\nI'll ask 7 questions to optimize this dual-track iteration:\n\nQ1: What's the primary goal for this iteration?\n    (e.g., feature delivery, technical debt, integration, quality)\n\nQ2: How much ready backlog do you have?\n    (Helps me assess Discovery urgency and Delivery capacity)\n\nQ3: What's your team's current velocity?\n    (Story points per iteration - influences planning)\n\nQ4: Are there any blocking risks or dependencies?\n    (Integration points, external teams, technical unknowns)\n\nQ5: What's the team composition this iteration?\n    (Available developers, testers, any absences)\n\nQ6: What's the deadline pressure?\n    (Release date, demo, compliance deadline)\n\nQ7: Any carry-over work from previous iteration?\n    (Incomplete stories that need to be finished)\n\nBased on your answers, I'll adjust:\n- Discovery\u002FDelivery balance\n- Story allocation\n- Risk investigation priority\n- Synchronization frequency\n```\n\n**Synthesize Guidance**: Combine answers into structured guidance for execution\n\n## Iteration Structure\n\n### Day 1: Kickoff (Week Start)\n\n**Delivery Track Kickoff**:\n- Review ready backlog from previous Discovery\n- Commit to iteration goals\n- Assign work to team members\n- Set success criteria\n\n**Discovery Track Planning**:\n- Identify next iteration candidates\n- Schedule stakeholder sessions\n- Plan spikes and investigations\n- Allocate Discovery capacity\n\n### Midpoint: Checkpoint (Mid-Week)\n\n**Delivery Progress Check**:\n- Review implementation status\n- Identify blockers\n- Run quality gates\n- Adjust if needed\n\n**Discovery Validation**:\n- Review refined requirements\n- Check acceptance criteria\n- Validate architectural decisions\n- Prepare handoff materials\n\n### End: Handoff and Retrospective (Week End)\n\n**Delivery Completion**:\n- Finalize work to Definition of Done\n- Run all quality gates\n- Deploy to staging\n- Generate metrics\n\n**Discovery Handoff**:\n- Complete Definition of Ready\n- Package backlog items\n- Transfer to Delivery backlog\n- Document decisions\n\n**Joint Activities**:\n- Handoff meeting\n- Retrospective\n- Metrics review\n- Next iteration planning\n\n## Multi-Agent Orchestration Workflow\n\n### Step 1: Initialize Iteration\n\n**Purpose**: Set up iteration structure and read context\n\n**Your Actions**:\n\n1. **Create Iteration Workspace**:\n   ```\n   mkdir -p .aiwg\u002Fiterations\u002Fiteration-{N}\u002F\n   mkdir -p .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdiscovery\u002F\n   mkdir -p .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdelivery\u002F\n   mkdir -p .aiwg\u002Fiterations\u002Fiteration-{N}\u002Freports\u002F\n   ```\n\n2. **Read Current State**:\n   ```\n   Read:\n   - .aiwg\u002Fplanning\u002Fiteration-plan-*.md (previous plans)\n   - .aiwg\u002Frequirements\u002Fready-backlog.md (if exists)\n   - .aiwg\u002Freports\u002Fiteration-*-report.md (previous iterations)\n   - .aiwg\u002Fmetrics\u002Fvelocity-tracking.md (if exists)\n   ```\n\n3. **Launch Iteration Planning**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Create iteration {N} plan\",\n       prompt=\"\"\"\n       Create dual-track iteration plan for iteration {N}:\n\n       Based on:\n       - Previous iteration velocity\n       - Ready backlog size\n       - Team capacity\n       - Risk register\n\n       Define:\n       1. Delivery Track Goals (iteration N)\n          - Story points to commit\n          - Work items to complete\n          - Quality targets\n\n       2. Discovery Track Goals (iteration N+1)\n          - Requirements to refine\n          - Spikes to execute\n          - Designs to validate\n\n       3. Success Criteria\n          - Delivery: What defines \"done\"\n          - Discovery: What defines \"ready\"\n\n       4. Schedule\n          - Key milestones\n          - Synchronization points\n          - Review sessions\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fiteration-plan.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n✓ Initialized iteration {N} workspace\n⏳ Creating iteration plan...\n✓ Iteration plan complete\n```\n\n### Step 2: Kickoff Delivery Track (Iteration N)\n\n**Purpose**: Start current iteration implementation work\n\n**Your Actions**:\n\n1. **Launch Delivery Planning** (parallel agents):\n   ```\n   # Agent 1: Requirements Analyst\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Validate ready backlog for Delivery\",\n       prompt=\"\"\"\n       Read ready backlog items for iteration {N}\n\n       For each item, verify:\n       - Acceptance criteria complete\n       - Test cases defined\n       - Dependencies identified\n       - Estimates confirmed\n\n       Flag any items not meeting Definition of Ready.\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdelivery\u002Fbacklog-validation.md\n       \"\"\"\n   )\n\n   # Agent 2: Software Implementer\n   Task(\n       subagent_type=\"software-implementer\",\n       description=\"Plan implementation approach\",\n       prompt=\"\"\"\n       Read validated backlog items\n\n       Create implementation plan:\n       - Technical approach for each story\n       - Component assignments\n       - Integration points\n       - Testing strategy\n\n       Identify technical risks or blockers.\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdelivery\u002Fimplementation-plan.md\n       \"\"\"\n   )\n\n   # Agent 3: Test Engineer\n   Task(\n       subagent_type=\"test-engineer\",\n       description=\"Create iteration test plan\",\n       prompt=\"\"\"\n       Read backlog items and acceptance criteria\n\n       Create test plan:\n       - Test scenarios per story\n       - Test data requirements\n       - Automation opportunities\n       - Regression suite updates\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdelivery\u002Ftest-plan.md\n       \"\"\"\n   )\n   ```\n\n2. **Synthesize Delivery Kickoff**:\n   ```\n   Task(\n       subagent_type=\"scrum-master\",\n       description=\"Finalize Delivery track kickoff\",\n       prompt=\"\"\"\n       Read all Delivery planning artifacts:\n       - backlog-validation.md\n       - implementation-plan.md\n       - test-plan.md\n\n       Create Delivery Kickoff Summary:\n       - Committed work items\n       - Team assignments\n       - Success criteria\n       - Daily standup schedule\n       - Blockers to watch\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdelivery\u002Fkickoff-summary.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Kicking off Delivery track (iteration {N})...\n  ✓ Backlog validated: {X} items ready\n  ✓ Implementation planned\n  ✓ Test scenarios defined\n✓ Delivery track kicked off: {Y} story points committed\n```\n\n### Step 3: Start Discovery Track (Iteration N+1)\n\n**Purpose**: Begin planning next iteration's work\n\n**Your Actions**:\n\n1. **Launch Discovery Planning** (parallel agents):\n   ```\n   # Agent 1: Product Designer\n   Task(\n       subagent_type=\"product-designer\",\n       description=\"Identify design needs for iteration {N+1}\",\n       prompt=\"\"\"\n       Read product backlog and stakeholder requests\n\n       Identify items needing design work:\n       - UI\u002FUX designs\n       - Workflow definitions\n       - Information architecture\n       - Interaction patterns\n\n       Schedule design sessions.\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdiscovery\u002Fdesign-plan.md\n       \"\"\"\n   )\n\n   # Agent 2: Requirements Analyst\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Plan requirements refinement for iteration {N+1}\",\n       prompt=\"\"\"\n       Read product backlog and priority items\n\n       Select 1.5x-2x next iteration capacity for refinement:\n       - User stories to elaborate\n       - Acceptance criteria to define\n       - Dependencies to investigate\n       - Stakeholder validation needed\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdiscovery\u002Frefinement-plan.md\n       \"\"\"\n   )\n\n   # Agent 3: Architecture Designer\n   Task(\n       subagent_type=\"architecture-designer\",\n       description=\"Identify architectural work for iteration {N+1}\",\n       prompt=\"\"\"\n       Read upcoming features and technical backlog\n\n       Identify architectural needs:\n       - Design decisions required\n       - Technical spikes needed\n       - POCs to validate\n       - Integration planning\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdiscovery\u002Farchitecture-plan.md\n       \"\"\"\n   )\n   ```\n\n2. **Synthesize Discovery Plan**:\n   ```\n   Task(\n       subagent_type=\"iteration-coordinator\",\n       description=\"Create Discovery track plan\",\n       prompt=\"\"\"\n       Read all Discovery planning artifacts:\n       - design-plan.md\n       - refinement-plan.md\n       - architecture-plan.md\n\n       Create Discovery Plan for iteration {N+1}:\n       - Priority items to refine\n       - Spikes to execute\n       - Stakeholder sessions\n       - Target ready backlog size\n       - Handoff date to Delivery\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdiscovery\u002Fdiscovery-plan.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Starting Discovery track (iteration {N+1})...\n  ✓ Design work identified\n  ✓ Requirements selected for refinement\n  ✓ Architectural spikes planned\n✓ Discovery track started: {Z} items in refinement\n```\n\n### Step 4: Midpoint Checkpoint\n\n**Purpose**: Assess progress and adjust both tracks\n\n**Your Actions**:\n\n1. **Check Delivery Progress**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Assess Delivery track progress\",\n       prompt=\"\"\"\n       Evaluate iteration {N} Delivery progress:\n\n       Check:\n       - Work items completed vs. planned\n       - Velocity tracking (on track?)\n       - Quality gates passed\n       - Blockers encountered\n       - Risk to iteration goals\n\n       Determine:\n       - Status: GREEN | YELLOW | RED\n       - Adjustments needed\n       - Items to defer or drop\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdelivery\u002Fmidpoint-assessment.md\n       \"\"\"\n   )\n   ```\n\n2. **Validate Discovery Refinement**:\n   ```\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Validate Discovery track progress\",\n       prompt=\"\"\"\n       Evaluate iteration {N+1} Discovery progress:\n\n       Check:\n       - Requirements refined vs. planned\n       - Acceptance criteria completeness\n       - Spike results\n       - Stakeholder feedback received\n       - Definition of Ready compliance\n\n       Determine:\n       - Ready backlog size projection\n       - Items needing more work\n       - Risks to next iteration\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdiscovery\u002Fmidpoint-validation.md\n       \"\"\"\n   )\n   ```\n\n3. **Run Quality Gates** (parallel):\n   ```\n   # Security Gate\n   Task(\n       subagent_type=\"security-gatekeeper\",\n       description=\"Run security gate check\",\n       prompt=\"\"\"\n       Check Delivery work for security compliance:\n       - Code security scanning results\n       - Authentication\u002Fauthorization implementation\n       - Data protection measures\n       - Security test coverage\n\n       Status: PASS | FAIL | WARNING\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdelivery\u002Fsecurity-gate.md\n       \"\"\"\n   )\n\n   # Test Coverage Gate\n   Task(\n       subagent_type=\"test-engineer\",\n       description=\"Run test coverage gate\",\n       prompt=\"\"\"\n       Check test coverage metrics:\n       - Unit test coverage %\n       - Integration test status\n       - Acceptance test automation\n       - Regression suite health\n\n       Status: PASS | FAIL | WARNING\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdelivery\u002Ftest-gate.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Midpoint checkpoint...\n  ✓ Delivery: {percentage}% complete, status {GREEN|YELLOW|RED}\n  ✓ Discovery: {X} items ready, {Y} in progress\n  ✓ Quality gates: Security {PASS|FAIL}, Testing {PASS|FAIL}\n✓ Checkpoint complete, adjustments identified\n```\n\n### Step 5: Discovery to Delivery Handoff\n\n**Purpose**: Transfer ready items from Discovery to Delivery backlog\n\n**Your Actions**:\n\n1. **Validate Definition of Ready**:\n   ```\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Validate items meet Definition of Ready\",\n       prompt=\"\"\"\n       For each Discovery item planned for handoff:\n\n       Validate DoR checklist:\n       - [ ] User story clear and complete\n       - [ ] Acceptance criteria testable\n       - [ ] Dependencies identified\n       - [ ] Estimated by team\n       - [ ] Design complete (if UI)\n       - [ ] Technical approach defined\n       - [ ] Test scenarios documented\n\n       Create handoff package per item.\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdiscovery\u002Fdor-validation.md\n       \"\"\"\n   )\n   ```\n\n2. **Create Handoff Package**:\n   ```\n   Task(\n       subagent_type=\"iteration-coordinator\",\n       description=\"Package Discovery items for handoff\",\n       prompt=\"\"\"\n       Create handoff package for iteration {N+1}:\n\n       Include:\n       - Ready user stories\n       - Acceptance criteria\n       - Design mockups\u002Fspecs\n       - Technical decisions (ADRs)\n       - Test scenarios\n       - Dependencies map\n\n       Organize by priority and component.\n\n       Output: .aiwg\u002Frequirements\u002Fiteration-{N+1}-ready-backlog.md\n       \"\"\"\n   )\n   ```\n\n3. **Conduct Handoff Meeting** (simulated):\n   ```\n   Task(\n       subagent_type=\"scrum-master\",\n       description=\"Document handoff meeting outcomes\",\n       prompt=\"\"\"\n       Simulate Discovery→Delivery handoff meeting:\n\n       Review each item:\n       - Clarify requirements\n       - Confirm estimates\n       - Identify risks\n       - Assign preliminary owners\n\n       Document:\n       - Items accepted\n       - Items needing more work\n       - Questions for stakeholders\n       - Next iteration capacity\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fhandoff-meeting-notes.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Processing Discovery→Delivery handoff...\n  ✓ DoR validation: {X}\u002F{Y} items ready\n  ✓ Handoff package created\n  ✓ Ready backlog size: {Z} story points (target: 1.5x-2x capacity)\n✓ Handoff complete for iteration {N+1}\n```\n\n### Step 6: Complete Iteration and Retrospective\n\n**Purpose**: Finalize iteration, capture lessons learned\n\n**Your Actions**:\n\n1. **Finalize Delivery Work**:\n   ```\n   Task(\n       subagent_type=\"test-engineer\",\n       description=\"Complete iteration testing\",\n       prompt=\"\"\"\n       Final testing for iteration {N}:\n\n       Execute:\n       - Acceptance tests for completed stories\n       - Regression test suite\n       - Integration tests\n       - Performance validation\n\n       Document:\n       - Test results\n       - Defects found\u002Ffixed\n       - Coverage metrics\n       - Quality assessment\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdelivery\u002Ffinal-test-report.md\n       \"\"\"\n   )\n   ```\n\n2. **Generate Iteration Metrics**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Calculate iteration metrics\",\n       prompt=\"\"\"\n       Generate metrics for iteration {N}:\n\n       Delivery Metrics:\n       - Velocity: planned vs. actual\n       - Completion rate: stories done\u002Fcommitted\n       - Defect density\n       - Quality gate pass rate\n\n       Discovery Metrics:\n       - Ready backlog size achieved\n       - DoR compliance rate\n       - Lead time (Discovery complete to Delivery start)\n       - Refinement efficiency\n\n       Synchronization Metrics:\n       - Handoff quality (rework rate)\n       - Idle time\n       - Wait time\n       - Defect leakage\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fmetrics-summary.md\n       \"\"\"\n   )\n   ```\n\n3. **Conduct Retrospective**:\n   ```\n   Task(\n       subagent_type=\"retrospective-analyzer\",\n       description=\"Facilitate iteration retrospective\",\n       prompt=\"\"\"\n       Analyze iteration {N} for improvements:\n\n       What Went Well:\n       - Delivery achievements\n       - Discovery successes\n       - Synchronization wins\n\n       What Could Improve:\n       - Process bottlenecks\n       - Communication gaps\n       - Quality issues\n\n       Action Items:\n       - Specific improvements\n       - Owner assignments\n       - Implementation timeline\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fretrospective.md\n       \"\"\"\n   )\n   ```\n\n4. **Generate Final Report**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Create dual-track iteration report\",\n       prompt=\"\"\"\n       Create comprehensive iteration {N} report:\n\n       Executive Summary:\n       - Overall status\n       - Goals achieved\n       - Key metrics\n\n       Delivery Track:\n       - Work completed\n       - Quality results\n       - Velocity analysis\n\n       Discovery Track:\n       - Backlog prepared\n       - Spikes completed\n       - Risks addressed\n\n       Synchronization:\n       - Lead time metrics\n       - Handoff quality\n       - Process efficiency\n\n       Next Iteration:\n       - Capacity planning\n       - Priority items\n       - Risk mitigation\n\n       Include all metrics, lessons learned, and action items.\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fiteration-report.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Completing iteration {N}...\n  ✓ Final testing complete: {X} stories accepted\n  ✓ Metrics calculated: Velocity {Y} points\n  ✓ Retrospective conducted: {Z} action items\n✓ Iteration {N} complete\n```\n\n### Step 7: Present Results\n\n**Purpose**: Summarize iteration outcomes for user\n\n**Your Actions**:\n\n```\nRead final report and present:\n\n═══════════════════════════════════════════════\nDual-Track Iteration {N} Summary\n═══════════════════════════════════════════════\n\n**Overall Status**: {COMPLETE | PARTIAL | BLOCKED}\n\n**Delivery Track (Iteration {N})**:\n✓ Completed: {X}\u002F{Y} stories ({percentage}%)\n✓ Velocity: {actual} points (planned: {planned})\n✓ Quality: All gates {PASSED|FAILED}\n✓ Defects: {found}\u002F{fixed}\n\n**Discovery Track (Iteration {N+1})**:\n✓ Refined: {A} stories\n✓ Ready Backlog: {B} points ({ratio}x capacity)\n✓ Spikes Completed: {C}\u002F{D}\n✓ DoR Compliance: {percentage}%\n\n**Synchronization Health**:\n✓ Lead Time: {weeks} (target: 1 iteration)\n✓ Handoff Quality: {percentage}% clean\n✓ Defect Leakage: {percentage}% (target: \u003C10%)\n✓ Ready Buffer: {ratio}x (target: 1.5x-2x)\n\n**Key Achievements**:\n- {achievement-1}\n- {achievement-2}\n- {achievement-3}\n\n**Action Items for Next Iteration**:\n1. {action-1} - Owner: {name}\n2. {action-2} - Owner: {name}\n3. {action-3} - Owner: {name}\n\n**Generated Artifacts**:\n- Iteration Plan: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fiteration-plan.md\n- Test Report: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdelivery\u002Ffinal-test-report.md\n- Metrics: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fmetrics-summary.md\n- Retrospective: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fretrospective.md\n- Full Report: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fiteration-report.md\n- Ready Backlog: .aiwg\u002Frequirements\u002Fiteration-{N+1}-ready-backlog.md\n\n**Next Steps**:\n- Review iteration report with team\n- Start iteration {N+1} planning\n- Address retrospective action items\n- Adjust capacity based on velocity\n\n═══════════════════════════════════════════════\n```\n\n## Quality Gates\n\nBefore marking workflow complete, verify:\n- [ ] Delivery work meets Definition of Done\n- [ ] Discovery items meet Definition of Ready\n- [ ] All quality gates passed or risks accepted\n- [ ] Metrics calculated and within targets\n- [ ] Retrospective conducted with action items\n- [ ] Ready backlog sufficient for next iteration\n\n## User Communication\n\n**At start**: Confirm understanding and set expectations\n\n```\nUnderstood. I'll orchestrate dual-track iteration {N}.\n\nThis will coordinate:\n- Delivery Track: Implementing iteration {N} work\n- Discovery Track: Refining iteration {N+1} work\n- Synchronization points and handoffs\n- Quality gates and metrics\n\nI'll manage the parallel tracks with multiple specialized agents.\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⚠️ = Warning\u002Fattention needed\n❌ = Blocked\u002Ffailed\n```\n\n**At end**: Present comprehensive summary (see Step 7)\n\n## Error Handling\n\n**If Delivery Blocked**:\n```\n⚠️ Delivery track blocked on iteration {N}\n\nBlocker: {description}\nImpact: {stories affected}\n\nOptions:\n1. Remove blocked stories from iteration\n2. Find alternative implementation\n3. Escalate to stakeholder\n\nRecommendation: {suggested action}\n```\n\n**If Discovery Behind**:\n```\n⚠️ Discovery track behind schedule\n\nReady backlog: {ratio}x capacity (target: 1.5x-2x)\nRisk: Iteration {N+1} may have insufficient work\n\nActions:\n1. Accelerate refinement sessions\n2. Simplify acceptance criteria\n3. Pull from future backlog\n\nImpact: Next iteration may have reduced scope\n```\n\n**If Quality Gate Failed**:\n```\n❌ Quality gate failed: {gate-name}\n\nFailure reason: {details}\nImpact: Cannot complete iteration without resolution\n\nRequired actions:\n1. {remediation-step-1}\n2. {remediation-step-2}\n\nEscalating to technical lead...\n```\n\n**If Handoff Incomplete**:\n```\n⚠️ Discovery→Delivery handoff incomplete\n\nItems not ready: {count}\nDoR compliance: {percentage}%\n\nImpact: Iteration {N+1} backlog insufficient\n\nOptions:\n1. Extend Discovery refinement\n2. Accept partial backlog\n3. Pull buffer stories\n\nDecision needed from Product Owner...\n```\n\n## Success Criteria\n\nThis orchestration succeeds when:\n- [ ] Delivery completes ≥80% committed work\n- [ ] Discovery achieves 1.5x-2x ready backlog\n- [ ] Quality gates pass (or risks accepted)\n- [ ] Handoff clean (≥90% DoR compliance)\n- [ ] Metrics within healthy ranges\n- [ ] Retrospective identifies improvements\n- [ ] Next iteration has sufficient backlog\n\n## Metrics to Track\n\n**During orchestration, track**:\n- Velocity: Story points completed vs. planned\n- Lead time: Discovery completion to Delivery start\n- Cycle time: Story start to done\n- Defect leakage: Discovery gaps causing Delivery issues\n- Ready backlog ratio: Ready items \u002F team capacity\n- Quality gate pass rate: First-time pass percentage\n- Synchronization efficiency: Wait time and idle time\n\n## References\n\n**Templates**:\n- Iteration Plan: `agentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Ftemplates\u002Fmanagement\u002Fiteration-plan-template.md`\n- Test Plan: `templates\u002Ftest\u002Fiteration-test-plan-template.md`\n- Retrospective: `agentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Ftemplates\u002Fmanagement\u002Fsprint-retrospective-template.md`\n- Metrics: `metrics\u002Fdelivery-metrics-catalog.md`\n\n**Workflows**:\n- Discovery Track: `flows\u002Fdiscovery-track-template.md`\n- Delivery Track: `flows\u002Fdelivery-track-template.md`\n- Handoff Checklist: `flows\u002Fhandoff-checklist-template.md`\n\n**Gate Criteria**:\n- `flows\u002Fgate-criteria-by-phase.md` (Construction section)\n\n**Dual-Track Guidance**:\n- `docs\u002Fdual-track-agile-guide.md`\n- `metrics\u002Fsynchronization-metrics.md`","> **Declarative Flow (#1539):** This flow's orchestration is now also expressed as a\n> declarative YAML Flow at `flows\u002Fflow-iteration-dual-track.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# Dual-Track Iteration Flow\n\n**You are the Core Orchestrator** for dual-track agile iteration management.\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 finalize artifacts\n6. **Report completion** with summary\n\n## Dual-Track Overview\n\n**Discovery Track**: Planning iteration N+1 (next iteration's work)\n- Requirements refinement\n- Design elaboration\n- Risk investigation\n- Acceptance criteria definition\n\n**Delivery Track**: Implementing iteration N (current iteration's work)\n- Coding committed stories\n- Testing implementation\n- Integration work\n- Quality assurance\n\n**Key Principle**: Discovery stays 1 iteration ahead to ensure Delivery always has ready backlog.\n\n## Natural Language Triggers\n\nUsers may say:\n- \"Run iteration 3\"\n- \"Start iteration 5\"\n- \"Execute dual-track iteration\"\n- \"Begin next sprint\"\n- \"Start iteration planning\"\n- \"Run sprint 4 with dual tracks\"\n\nYou recognize these as requests for this orchestration flow.\n\n## Parameter Handling\n\n### --guidance Parameter\n\n**Purpose**: User provides upfront direction to tailor iteration priorities\n\n**Examples**:\n```\n--guidance \"Focus on security stories first, compliance audit next week\"\n--guidance \"Performance optimization critical, defer UI polish\"\n--guidance \"Team velocity reduced this sprint, plan conservatively\"\n--guidance \"Integration with payment gateway is blocking, prioritize spikes\"\n```\n\n**How to Apply**:\n- Parse guidance for keywords: security, performance, integration, velocity\n- Adjust Discovery focus (requirements vs. spikes vs. design)\n- Modify Delivery priorities (feature vs. tech debt vs. fixes)\n- Influence synchronization points (more\u002Fless frequent)\n\n### --interactive Parameter\n\n**Purpose**: You ask 5-7 strategic questions to understand iteration context\n\n**Questions to Ask** (if --interactive):\n\n```\nI'll ask 7 questions to optimize this dual-track iteration:\n\nQ1: What's the primary goal for this iteration?\n    (e.g., feature delivery, technical debt, integration, quality)\n\nQ2: How much ready backlog do you have?\n    (Helps me assess Discovery urgency and Delivery capacity)\n\nQ3: What's your team's current velocity?\n    (Story points per iteration - influences planning)\n\nQ4: Are there any blocking risks or dependencies?\n    (Integration points, external teams, technical unknowns)\n\nQ5: What's the team composition this iteration?\n    (Available developers, testers, any absences)\n\nQ6: What's the deadline pressure?\n    (Release date, demo, compliance deadline)\n\nQ7: Any carry-over work from previous iteration?\n    (Incomplete stories that need to be finished)\n\nBased on your answers, I'll adjust:\n- Discovery\u002FDelivery balance\n- Story allocation\n- Risk investigation priority\n- Synchronization frequency\n```\n\n**Synthesize Guidance**: Combine answers into structured guidance for execution\n\n## Iteration Structure\n\n### Day 1: Kickoff (Week Start)\n\n**Delivery Track Kickoff**:\n- Review ready backlog from previous Discovery\n- Commit to iteration goals\n- Assign work to team members\n- Set success criteria\n\n**Discovery Track Planning**:\n- Identify next iteration candidates\n- Schedule stakeholder sessions\n- Plan spikes and investigations\n- Allocate Discovery capacity\n\n### Midpoint: Checkpoint (Mid-Week)\n\n**Delivery Progress Check**:\n- Review implementation status\n- Identify blockers\n- Run quality gates\n- Adjust if needed\n\n**Discovery Validation**:\n- Review refined requirements\n- Check acceptance criteria\n- Validate architectural decisions\n- Prepare handoff materials\n\n### End: Handoff and Retrospective (Week End)\n\n**Delivery Completion**:\n- Finalize work to Definition of Done\n- Run all quality gates\n- Deploy to staging\n- Generate metrics\n\n**Discovery Handoff**:\n- Complete Definition of Ready\n- Package backlog items\n- Transfer to Delivery backlog\n- Document decisions\n\n**Joint Activities**:\n- Handoff meeting\n- Retrospective\n- Metrics review\n- Next iteration planning\n\n## Multi-Agent Orchestration Workflow\n\n### Step 1: Initialize Iteration\n\n**Purpose**: Set up iteration structure and read context\n\n**Your Actions**:\n\n1. **Create Iteration Workspace**:\n   ```\n   mkdir -p .aiwg\u002Fiterations\u002Fiteration-{N}\u002F\n   mkdir -p .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdiscovery\u002F\n   mkdir -p .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdelivery\u002F\n   mkdir -p .aiwg\u002Fiterations\u002Fiteration-{N}\u002Freports\u002F\n   ```\n\n2. **Read Current State**:\n   ```\n   Read:\n   - .aiwg\u002Fplanning\u002Fiteration-plan-*.md (previous plans)\n   - .aiwg\u002Frequirements\u002Fready-backlog.md (if exists)\n   - .aiwg\u002Freports\u002Fiteration-*-report.md (previous iterations)\n   - .aiwg\u002Fmetrics\u002Fvelocity-tracking.md (if exists)\n   ```\n\n3. **Launch Iteration Planning**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Create iteration {N} plan\",\n       prompt=\"\"\"\n       Create dual-track iteration plan for iteration {N}:\n\n       Based on:\n       - Previous iteration velocity\n       - Ready backlog size\n       - Team capacity\n       - Risk register\n\n       Define:\n       1. Delivery Track Goals (iteration N)\n          - Story points to commit\n          - Work items to complete\n          - Quality targets\n\n       2. Discovery Track Goals (iteration N+1)\n          - Requirements to refine\n          - Spikes to execute\n          - Designs to validate\n\n       3. Success Criteria\n          - Delivery: What defines \"done\"\n          - Discovery: What defines \"ready\"\n\n       4. Schedule\n          - Key milestones\n          - Synchronization points\n          - Review sessions\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fiteration-plan.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n✓ Initialized iteration {N} workspace\n⏳ Creating iteration plan...\n✓ Iteration plan complete\n```\n\n### Step 2: Kickoff Delivery Track (Iteration N)\n\n**Purpose**: Start current iteration implementation work\n\n**Your Actions**:\n\n1. **Launch Delivery Planning** (parallel agents):\n   ```\n   # Agent 1: Requirements Analyst\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Validate ready backlog for Delivery\",\n       prompt=\"\"\"\n       Read ready backlog items for iteration {N}\n\n       For each item, verify:\n       - Acceptance criteria complete\n       - Test cases defined\n       - Dependencies identified\n       - Estimates confirmed\n\n       Flag any items not meeting Definition of Ready.\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdelivery\u002Fbacklog-validation.md\n       \"\"\"\n   )\n\n   # Agent 2: Software Implementer\n   Task(\n       subagent_type=\"software-implementer\",\n       description=\"Plan implementation approach\",\n       prompt=\"\"\"\n       Read validated backlog items\n\n       Create implementation plan:\n       - Technical approach for each story\n       - Component assignments\n       - Integration points\n       - Testing strategy\n\n       Identify technical risks or blockers.\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdelivery\u002Fimplementation-plan.md\n       \"\"\"\n   )\n\n   # Agent 3: Test Engineer\n   Task(\n       subagent_type=\"test-engineer\",\n       description=\"Create iteration test plan\",\n       prompt=\"\"\"\n       Read backlog items and acceptance criteria\n\n       Create test plan:\n       - Test scenarios per story\n       - Test data requirements\n       - Automation opportunities\n       - Regression suite updates\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdelivery\u002Ftest-plan.md\n       \"\"\"\n   )\n   ```\n\n2. **Synthesize Delivery Kickoff**:\n   ```\n   Task(\n       subagent_type=\"scrum-master\",\n       description=\"Finalize Delivery track kickoff\",\n       prompt=\"\"\"\n       Read all Delivery planning artifacts:\n       - backlog-validation.md\n       - implementation-plan.md\n       - test-plan.md\n\n       Create Delivery Kickoff Summary:\n       - Committed work items\n       - Team assignments\n       - Success criteria\n       - Daily standup schedule\n       - Blockers to watch\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdelivery\u002Fkickoff-summary.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Kicking off Delivery track (iteration {N})...\n  ✓ Backlog validated: {X} items ready\n  ✓ Implementation planned\n  ✓ Test scenarios defined\n✓ Delivery track kicked off: {Y} story points committed\n```\n\n### Step 3: Start Discovery Track (Iteration N+1)\n\n**Purpose**: Begin planning next iteration's work\n\n**Your Actions**:\n\n1. **Launch Discovery Planning** (parallel agents):\n   ```\n   # Agent 1: Product Designer\n   Task(\n       subagent_type=\"product-designer\",\n       description=\"Identify design needs for iteration {N+1}\",\n       prompt=\"\"\"\n       Read product backlog and stakeholder requests\n\n       Identify items needing design work:\n       - UI\u002FUX designs\n       - Workflow definitions\n       - Information architecture\n       - Interaction patterns\n\n       Schedule design sessions.\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdiscovery\u002Fdesign-plan.md\n       \"\"\"\n   )\n\n   # Agent 2: Requirements Analyst\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Plan requirements refinement for iteration {N+1}\",\n       prompt=\"\"\"\n       Read product backlog and priority items\n\n       Select 1.5x-2x next iteration capacity for refinement:\n       - User stories to elaborate\n       - Acceptance criteria to define\n       - Dependencies to investigate\n       - Stakeholder validation needed\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdiscovery\u002Frefinement-plan.md\n       \"\"\"\n   )\n\n   # Agent 3: Architecture Designer\n   Task(\n       subagent_type=\"architecture-designer\",\n       description=\"Identify architectural work for iteration {N+1}\",\n       prompt=\"\"\"\n       Read upcoming features and technical backlog\n\n       Identify architectural needs:\n       - Design decisions required\n       - Technical spikes needed\n       - POCs to validate\n       - Integration planning\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdiscovery\u002Farchitecture-plan.md\n       \"\"\"\n   )\n   ```\n\n2. **Synthesize Discovery Plan**:\n   ```\n   Task(\n       subagent_type=\"iteration-coordinator\",\n       description=\"Create Discovery track plan\",\n       prompt=\"\"\"\n       Read all Discovery planning artifacts:\n       - design-plan.md\n       - refinement-plan.md\n       - architecture-plan.md\n\n       Create Discovery Plan for iteration {N+1}:\n       - Priority items to refine\n       - Spikes to execute\n       - Stakeholder sessions\n       - Target ready backlog size\n       - Handoff date to Delivery\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdiscovery\u002Fdiscovery-plan.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Starting Discovery track (iteration {N+1})...\n  ✓ Design work identified\n  ✓ Requirements selected for refinement\n  ✓ Architectural spikes planned\n✓ Discovery track started: {Z} items in refinement\n```\n\n### Step 4: Midpoint Checkpoint\n\n**Purpose**: Assess progress and adjust both tracks\n\n**Your Actions**:\n\n1. **Check Delivery Progress**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Assess Delivery track progress\",\n       prompt=\"\"\"\n       Evaluate iteration {N} Delivery progress:\n\n       Check:\n       - Work items completed vs. planned\n       - Velocity tracking (on track?)\n       - Quality gates passed\n       - Blockers encountered\n       - Risk to iteration goals\n\n       Determine:\n       - Status: GREEN | YELLOW | RED\n       - Adjustments needed\n       - Items to defer or drop\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdelivery\u002Fmidpoint-assessment.md\n       \"\"\"\n   )\n   ```\n\n2. **Validate Discovery Refinement**:\n   ```\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Validate Discovery track progress\",\n       prompt=\"\"\"\n       Evaluate iteration {N+1} Discovery progress:\n\n       Check:\n       - Requirements refined vs. planned\n       - Acceptance criteria completeness\n       - Spike results\n       - Stakeholder feedback received\n       - Definition of Ready compliance\n\n       Determine:\n       - Ready backlog size projection\n       - Items needing more work\n       - Risks to next iteration\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdiscovery\u002Fmidpoint-validation.md\n       \"\"\"\n   )\n   ```\n\n3. **Run Quality Gates** (parallel):\n   ```\n   # Security Gate\n   Task(\n       subagent_type=\"security-gatekeeper\",\n       description=\"Run security gate check\",\n       prompt=\"\"\"\n       Check Delivery work for security compliance:\n       - Code security scanning results\n       - Authentication\u002Fauthorization implementation\n       - Data protection measures\n       - Security test coverage\n\n       Status: PASS | FAIL | WARNING\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdelivery\u002Fsecurity-gate.md\n       \"\"\"\n   )\n\n   # Test Coverage Gate\n   Task(\n       subagent_type=\"test-engineer\",\n       description=\"Run test coverage gate\",\n       prompt=\"\"\"\n       Check test coverage metrics:\n       - Unit test coverage %\n       - Integration test status\n       - Acceptance test automation\n       - Regression suite health\n\n       Status: PASS | FAIL | WARNING\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdelivery\u002Ftest-gate.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Midpoint checkpoint...\n  ✓ Delivery: {percentage}% complete, status {GREEN|YELLOW|RED}\n  ✓ Discovery: {X} items ready, {Y} in progress\n  ✓ Quality gates: Security {PASS|FAIL}, Testing {PASS|FAIL}\n✓ Checkpoint complete, adjustments identified\n```\n\n### Step 5: Discovery to Delivery Handoff\n\n**Purpose**: Transfer ready items from Discovery to Delivery backlog\n\n**Your Actions**:\n\n1. **Validate Definition of Ready**:\n   ```\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Validate items meet Definition of Ready\",\n       prompt=\"\"\"\n       For each Discovery item planned for handoff:\n\n       Validate DoR checklist:\n       - [ ] User story clear and complete\n       - [ ] Acceptance criteria testable\n       - [ ] Dependencies identified\n       - [ ] Estimated by team\n       - [ ] Design complete (if UI)\n       - [ ] Technical approach defined\n       - [ ] Test scenarios documented\n\n       Create handoff package per item.\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdiscovery\u002Fdor-validation.md\n       \"\"\"\n   )\n   ```\n\n2. **Create Handoff Package**:\n   ```\n   Task(\n       subagent_type=\"iteration-coordinator\",\n       description=\"Package Discovery items for handoff\",\n       prompt=\"\"\"\n       Create handoff package for iteration {N+1}:\n\n       Include:\n       - Ready user stories\n       - Acceptance criteria\n       - Design mockups\u002Fspecs\n       - Technical decisions (ADRs)\n       - Test scenarios\n       - Dependencies map\n\n       Organize by priority and component.\n\n       Output: .aiwg\u002Frequirements\u002Fiteration-{N+1}-ready-backlog.md\n       \"\"\"\n   )\n   ```\n\n3. **Conduct Handoff Meeting** (simulated):\n   ```\n   Task(\n       subagent_type=\"scrum-master\",\n       description=\"Document handoff meeting outcomes\",\n       prompt=\"\"\"\n       Simulate Discovery→Delivery handoff meeting:\n\n       Review each item:\n       - Clarify requirements\n       - Confirm estimates\n       - Identify risks\n       - Assign preliminary owners\n\n       Document:\n       - Items accepted\n       - Items needing more work\n       - Questions for stakeholders\n       - Next iteration capacity\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fhandoff-meeting-notes.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Processing Discovery→Delivery handoff...\n  ✓ DoR validation: {X}\u002F{Y} items ready\n  ✓ Handoff package created\n  ✓ Ready backlog size: {Z} story points (target: 1.5x-2x capacity)\n✓ Handoff complete for iteration {N+1}\n```\n\n### Step 6: Complete Iteration and Retrospective\n\n**Purpose**: Finalize iteration, capture lessons learned\n\n**Your Actions**:\n\n1. **Finalize Delivery Work**:\n   ```\n   Task(\n       subagent_type=\"test-engineer\",\n       description=\"Complete iteration testing\",\n       prompt=\"\"\"\n       Final testing for iteration {N}:\n\n       Execute:\n       - Acceptance tests for completed stories\n       - Regression test suite\n       - Integration tests\n       - Performance validation\n\n       Document:\n       - Test results\n       - Defects found\u002Ffixed\n       - Coverage metrics\n       - Quality assessment\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdelivery\u002Ffinal-test-report.md\n       \"\"\"\n   )\n   ```\n\n2. **Generate Iteration Metrics**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Calculate iteration metrics\",\n       prompt=\"\"\"\n       Generate metrics for iteration {N}:\n\n       Delivery Metrics:\n       - Velocity: planned vs. actual\n       - Completion rate: stories done\u002Fcommitted\n       - Defect density\n       - Quality gate pass rate\n\n       Discovery Metrics:\n       - Ready backlog size achieved\n       - DoR compliance rate\n       - Lead time (Discovery complete to Delivery start)\n       - Refinement efficiency\n\n       Synchronization Metrics:\n       - Handoff quality (rework rate)\n       - Idle time\n       - Wait time\n       - Defect leakage\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fmetrics-summary.md\n       \"\"\"\n   )\n   ```\n\n3. **Conduct Retrospective**:\n   ```\n   Task(\n       subagent_type=\"retrospective-analyzer\",\n       description=\"Facilitate iteration retrospective\",\n       prompt=\"\"\"\n       Analyze iteration {N} for improvements:\n\n       What Went Well:\n       - Delivery achievements\n       - Discovery successes\n       - Synchronization wins\n\n       What Could Improve:\n       - Process bottlenecks\n       - Communication gaps\n       - Quality issues\n\n       Action Items:\n       - Specific improvements\n       - Owner assignments\n       - Implementation timeline\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fretrospective.md\n       \"\"\"\n   )\n   ```\n\n4. **Generate Final Report**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Create dual-track iteration report\",\n       prompt=\"\"\"\n       Create comprehensive iteration {N} report:\n\n       Executive Summary:\n       - Overall status\n       - Goals achieved\n       - Key metrics\n\n       Delivery Track:\n       - Work completed\n       - Quality results\n       - Velocity analysis\n\n       Discovery Track:\n       - Backlog prepared\n       - Spikes completed\n       - Risks addressed\n\n       Synchronization:\n       - Lead time metrics\n       - Handoff quality\n       - Process efficiency\n\n       Next Iteration:\n       - Capacity planning\n       - Priority items\n       - Risk mitigation\n\n       Include all metrics, lessons learned, and action items.\n\n       Output: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fiteration-report.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Completing iteration {N}...\n  ✓ Final testing complete: {X} stories accepted\n  ✓ Metrics calculated: Velocity {Y} points\n  ✓ Retrospective conducted: {Z} action items\n✓ Iteration {N} complete\n```\n\n### Step 7: Present Results\n\n**Purpose**: Summarize iteration outcomes for user\n\n**Your Actions**:\n\n```\nRead final report and present:\n\n═══════════════════════════════════════════════\nDual-Track Iteration {N} Summary\n═══════════════════════════════════════════════\n\n**Overall Status**: {COMPLETE | PARTIAL | BLOCKED}\n\n**Delivery Track (Iteration {N})**:\n✓ Completed: {X}\u002F{Y} stories ({percentage}%)\n✓ Velocity: {actual} points (planned: {planned})\n✓ Quality: All gates {PASSED|FAILED}\n✓ Defects: {found}\u002F{fixed}\n\n**Discovery Track (Iteration {N+1})**:\n✓ Refined: {A} stories\n✓ Ready Backlog: {B} points ({ratio}x capacity)\n✓ Spikes Completed: {C}\u002F{D}\n✓ DoR Compliance: {percentage}%\n\n**Synchronization Health**:\n✓ Lead Time: {weeks} (target: 1 iteration)\n✓ Handoff Quality: {percentage}% clean\n✓ Defect Leakage: {percentage}% (target: \u003C10%)\n✓ Ready Buffer: {ratio}x (target: 1.5x-2x)\n\n**Key Achievements**:\n- {achievement-1}\n- {achievement-2}\n- {achievement-3}\n\n**Action Items for Next Iteration**:\n1. {action-1} - Owner: {name}\n2. {action-2} - Owner: {name}\n3. {action-3} - Owner: {name}\n\n**Generated Artifacts**:\n- Iteration Plan: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fiteration-plan.md\n- Test Report: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fdelivery\u002Ffinal-test-report.md\n- Metrics: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fmetrics-summary.md\n- Retrospective: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fretrospective.md\n- Full Report: .aiwg\u002Fiterations\u002Fiteration-{N}\u002Fiteration-report.md\n- Ready Backlog: .aiwg\u002Frequirements\u002Fiteration-{N+1}-ready-backlog.md\n\n**Next Steps**:\n- Review iteration report with team\n- Start iteration {N+1} planning\n- Address retrospective action items\n- Adjust capacity based on velocity\n\n═══════════════════════════════════════════════\n```\n\n## Quality Gates\n\nBefore marking workflow complete, verify:\n- [ ] Delivery work meets Definition of Done\n- [ ] Discovery items meet Definition of Ready\n- [ ] All quality gates passed or risks accepted\n- [ ] Metrics calculated and within targets\n- [ ] Retrospective conducted with action items\n- [ ] Ready backlog sufficient for next iteration\n\n## User Communication\n\n**At start**: Confirm understanding and set expectations\n\n```\nUnderstood. I'll orchestrate dual-track iteration {N}.\n\nThis will coordinate:\n- Delivery Track: Implementing iteration {N} work\n- Discovery Track: Refining iteration {N+1} work\n- Synchronization points and handoffs\n- Quality gates and metrics\n\nI'll manage the parallel tracks with multiple specialized agents.\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⚠️ = Warning\u002Fattention needed\n❌ = Blocked\u002Ffailed\n```\n\n**At end**: Present comprehensive summary (see Step 7)\n\n## Error Handling\n\n**If Delivery Blocked**:\n```\n⚠️ Delivery track blocked on iteration {N}\n\nBlocker: {description}\nImpact: {stories affected}\n\nOptions:\n1. Remove blocked stories from iteration\n2. Find alternative implementation\n3. Escalate to stakeholder\n\nRecommendation: {suggested action}\n```\n\n**If Discovery Behind**:\n```\n⚠️ Discovery track behind schedule\n\nReady backlog: {ratio}x capacity (target: 1.5x-2x)\nRisk: Iteration {N+1} may have insufficient work\n\nActions:\n1. Accelerate refinement sessions\n2. Simplify acceptance criteria\n3. Pull from future backlog\n\nImpact: Next iteration may have reduced scope\n```\n\n**If Quality Gate Failed**:\n```\n❌ Quality gate failed: {gate-name}\n\nFailure reason: {details}\nImpact: Cannot complete iteration without resolution\n\nRequired actions:\n1. {remediation-step-1}\n2. {remediation-step-2}\n\nEscalating to technical lead...\n```\n\n**If Handoff Incomplete**:\n```\n⚠️ Discovery→Delivery handoff incomplete\n\nItems not ready: {count}\nDoR compliance: {percentage}%\n\nImpact: Iteration {N+1} backlog insufficient\n\nOptions:\n1. Extend Discovery refinement\n2. Accept partial backlog\n3. Pull buffer stories\n\nDecision needed from Product Owner...\n```\n\n## Success Criteria\n\nThis orchestration succeeds when:\n- [ ] Delivery completes ≥80% committed work\n- [ ] Discovery achieves 1.5x-2x ready backlog\n- [ ] Quality gates pass (or risks accepted)\n- [ ] Handoff clean (≥90% DoR compliance)\n- [ ] Metrics within healthy ranges\n- [ ] Retrospective identifies improvements\n- [ ] Next iteration has sufficient backlog\n\n## Metrics to Track\n\n**During orchestration, track**:\n- Velocity: Story points completed vs. planned\n- Lead time: Discovery completion to Delivery start\n- Cycle time: Story start to done\n- Defect leakage: Discovery gaps causing Delivery issues\n- Ready backlog ratio: Ready items \u002F team capacity\n- Quality gate pass rate: First-time pass percentage\n- Synchronization efficiency: Wait time and idle time\n\n## References\n\n**Templates**:\n- Iteration Plan: `agentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Ftemplates\u002Fmanagement\u002Fiteration-plan-template.md`\n- Test Plan: `templates\u002Ftest\u002Fiteration-test-plan-template.md`\n- Retrospective: `agentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Ftemplates\u002Fmanagement\u002Fsprint-retrospective-template.md`\n- Metrics: `metrics\u002Fdelivery-metrics-catalog.md`\n\n**Workflows**:\n- Discovery Track: `flows\u002Fdiscovery-track-template.md`\n- Delivery Track: `flows\u002Fdelivery-track-template.md`\n- Handoff Checklist: `flows\u002Fhandoff-checklist-template.md`\n\n**Gate Criteria**:\n- `flows\u002Fgate-criteria-by-phase.md` (Construction section)\n\n**Dual-Track Guidance**:\n- `docs\u002Fdual-track-agile-guide.md`\n- `metrics\u002Fsynchronization-metrics.md`",{"name":5,"namespace":49,"platforms":50,"commandHint":52,"description":7},"aiwg",[51],"all",{"model":29,"category":53,"modelRole":36,"modelTier":54,"allowedTools":55,"argumentHint":56,"orchestration":57},"sdlc-orchestration","standard","Task, Read, Write, Glob, TodoWrite","\u003Citeration-number> [project-directory] [--guidance \"text\"] [--interactive]",true,"main","a602706fc62ff1cfcb18001358ac39647b08acf5","agentic\u002Fcode\u002Fplugins\u002Fsdlc\u002Fskills\u002Fflow-iteration-dual-track",36,"https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg","https:\u002F\u002Faiwg.io","https:\u002F\u002Fgithub.com\u002Fjmagly","https:\u002F\u002Fintegrolabs.io","ml\u002Fai, industrial automation, safety\u002Fsecurity, ssi\r\n\r\nmagly.net\r\nintegrolabs.io\r\naiwg.io\r\nfortemi.com\r\npagenary.com\r\nbytecask.com","2026-11-12 21:57:33",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":57},[70,73,76],{"tool":71,"command":72},"npx","npx skills add jmagly\u002Faiwg --skill flow-iteration-dual-track",{"tool":74,"command":75},"bunx","bunx skills add jmagly\u002Faiwg --skill flow-iteration-dual-track",{"tool":77,"command":78},"pnpm","pnpm dlx skills add jmagly\u002Faiwg --skill flow-iteration-dual-track","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fsdlc\u002Fskills\u002Fflow-iteration-dual-track\u002FSKILL.md",[],[82,109,132,138,145,157],{"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,38,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,38,123,97,124,125,99,126,90,127,101,128,129,104,105,130,131,37],"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,38,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,38,105,126,125,130,131,37],{"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,30,28,156],"fixture skill","fixture","rule","exercise",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":164,"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",[163],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[165,166,128,167,154],"pi","pi local","duplicate"]