[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C26Y8ASMVPR08DXD72NX47":3,"skill-same:01M6C26Y8ASMVPR08DXD72NX47":89},{"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":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":68,"updatedAt":69,"install":70,"resources":82},"01M6C26Y8ASMVPR08DXD72NX47","flow-handoff-checklist",null,"Orchestrate handoff validation between SDLC phases and tracks (Discovery→Delivery, Delivery→Ops, phase transitions)","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\u002Fframeworks\u002Fsdlc-complete\u002Fskills\u002Fflow-handoff-checklist\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,44,45],"handoff","flow","checklist","flow handoff checklist","phase","directory","true","tracks","sonnet","project","delivery","ops","sdlc","interactive","write","read","coding","text","discovery","orchestrate","validation","orchestration","2026-11-10 10:12:30",false,"---\nnamespace: aiwg\nname: flow-handoff-checklist\nplatforms: [all]\ndescription: Orchestrate handoff validation between SDLC phases and tracks (Discovery→Delivery, Delivery→Ops, phase transitions)\ncommandHint:\n  argumentHint: \u003Cfrom-phase> \u003Cto-phase> [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-handoff-checklist.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# SDLC Handoff Checklist Flow\n\n**You are the Core Orchestrator** for validating and executing handoffs between SDLC phases and tracks.\n\n## Threat-assessment gate\n\nBefore signoff or packaging, resolve the active workspace member's\n`security.threatAssessment` policy and assess the synthesized handoff as\n`handoff` with `tools\u002Fsecurity\u002Fthreat-assessment.mjs`. Store the report with\nthe handoff evidence. Audit mode records `wouldAction` without interrupting;\nenforce-mode `flag`\u002F`require-authorization` pauses and `reject` blocks the\nhandoff. Off mode disables only this AIWG classifier.\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## Natural Language Triggers\n\nUsers may say:\n- \"Check handoff readiness to Delivery\"\n- \"Validate handoff from Discovery\"\n- \"Verify handoff readiness for Operations\"\n- \"Review handoff checklist\"\n- \"Check if we're ready for phase transition\"\n- \"Validate Definition of Ready\"\n- \"Run operational readiness review\"\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 handoff validation priorities\n\n**Examples**:\n```\n--guidance \"Focus on security compliance, SOC2 audit next month\"\n--guidance \"Quick validation, team is waiting to start\"\n--guidance \"Pay special attention to test coverage and documentation\"\n--guidance \"First handoff, need detailed validation\"\n```\n\n**How to Apply**:\n- Parse guidance for keywords: security, documentation, testing, compliance, speed\n- Adjust validation depth (comprehensive vs. essential checks)\n- Modify agent assignments (add specialized validators)\n- Influence priority ordering (critical checks first)\n\n### --interactive Parameter\n\n**Purpose**: You ask 5-7 strategic questions to understand handoff context\n\n**Questions to Ask** (if --interactive):\n\n```\nI'll ask 7 strategic questions to tailor the handoff validation:\n\nQ1: Is this your first handoff of this type?\n    (Helps me determine validation thoroughness needed)\n\nQ2: What's your biggest concern about this handoff?\n    (e.g., incomplete requirements, missing tests, documentation gaps)\n\nQ3: How urgent is this handoff?\n    (Influences whether to do comprehensive or essential checks)\n\nQ4: Are there any known gaps you're already aware of?\n    (Helps focus validation on unknown issues)\n\nQ5: Who are the key stakeholders who need to sign off?\n    (Determines which reviewers to engage)\n\nQ6: Are there any special compliance or regulatory requirements?\n    (e.g., HIPAA, SOC2, PCI-DSS affects validation criteria)\n\nQ7: What's your fallback plan if handoff is blocked?\n    (Helps prepare contingency recommendations)\n\nBased on your answers, I'll adjust:\n- Validation depth (comprehensive vs. streamlined)\n- Agent assignments (add specialized reviewers)\n- Priority ordering (critical items first)\n- Remediation recommendations\n```\n\n**Synthesize Guidance**: Combine answers into structured guidance for execution\n\n## Supported Handoffs\n\n### Phase Transitions\n- **inception → elaboration**: Lifecycle Objective Milestone handoff\n- **elaboration → construction**: Lifecycle Architecture Milestone handoff\n- **construction → transition**: Operational Capability Milestone handoff\n- **transition → operations**: Product Release Milestone handoff\n\n### Track Handoffs\n- **discovery → delivery**: Definition of Ready (DoR) validation\n- **delivery → operations**: Operational Readiness Review (ORR)\n- **delivery → discovery**: Feedback loop for rework\u002Fclarification\n\n### Special Handoffs\n- **intake → inception**: Project Intake to Inception kickoff\n- **concept → inception**: Concept to Inception flow start\n\n## Multi-Agent Orchestration Workflow\n\n### Step 1: Identify and Load Handoff Checklist\n\n**Purpose**: Determine which handoff checklist applies and load criteria\n\n**Your Actions**:\n\n1. **Parse Handoff Type**:\n   ```\n   Determine from user input:\n   - From phase\u002Ftrack\n   - To phase\u002Ftrack\n   - Type: Phase transition, Track handoff, or Special\n   ```\n\n2. **Load Checklist Criteria**:\n   ```\n   Based on handoff type, identify:\n   - Required artifacts\n   - Validation criteria\n   - Signoff requirements\n   - Pass threshold\n   ```\n\n3. **Initialize Validation Workspace**:\n   ```\n   Create workspace structure:\n   .aiwg\u002Fworking\u002Fhandoff\u002F\n   ├── artifacts\u002F      # Artifact validation results\n   ├── checklist\u002F      # Checklist item validation\n   ├── signoffs\u002F       # Signoff status tracking\n   └── report\u002F         # Final handoff report\n   ```\n\n**Communicate Progress**:\n```\n✓ Handoff identified: {from-phase} → {to-phase}\n✓ Checklist loaded: {checklist-name}\n⏳ Starting validation...\n```\n\n### Step 2: Validate Required Artifacts\n\n**Purpose**: Check presence and completeness of required artifacts\n\n**Your Actions**:\n\n1. **For Discovery → Delivery (Definition of Ready)**:\n   ```\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Validate Definition of Ready artifacts\",\n       prompt=\"\"\"\n       Check for required artifacts per backlog item:\n\n       Requirements:\n       - requirements\u002Fuse-case-brief-{ID}.md\n       - test\u002Facceptance-test-card-{ID}.md\n\n       Design (if applicable):\n       - analysis-design\u002Fdata-contract-card-{ID}.md\n       - analysis-design\u002Finterface-card-{ID}.md\n\n       Risk Management:\n       - management\u002Frisk-card-{ID}.md (if high-risk)\n       - analysis-design\u002Fspike-card-{ID}.md (if spike conducted)\n\n       For each artifact:\n       1. Check existence (file present)\n       2. Validate completeness (all sections filled)\n       3. Check approval status (stakeholder signoff)\n       4. Verify currency (last updated within sprint)\n\n       Output validation report:\n       .aiwg\u002Fworking\u002Fhandoff\u002Fartifacts\u002Fdor-artifacts-validation.md\n       \"\"\"\n   )\n   ```\n\n2. **For Delivery → Operations (Operational Readiness)**:\n   ```\n   Task(\n       subagent_type=\"documentation-archivist\",\n       description=\"Validate Operational Readiness artifacts\",\n       prompt=\"\"\"\n       Check for required deployment artifacts:\n\n       Deployment:\n       - deployment\u002Fdeployment-plan-template.md\n       - deployment\u002Frelease-notes-template.md\n       - deployment\u002Frunbook-*.md\n\n       Testing:\n       - test\u002Ftest-evaluation-summary-template.md\n       - test\u002Facceptance-test-results-*.md\n\n       Operations:\n       - deployment\u002Foperational-readiness-review-template.md\n       - support\u002Fsupport-plan-template.md\n       - training\u002Fuser-guide-template.md\n\n       For each artifact:\n       1. Verify existence and completeness\n       2. Check version currency (matches release)\n       3. Validate technical accuracy\n       4. Confirm operational procedures documented\n\n       Output validation report:\n       .aiwg\u002Fworking\u002Fhandoff\u002Fartifacts\u002Forr-artifacts-validation.md\n       \"\"\"\n   )\n   ```\n\n3. **For Phase Transitions**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Validate phase transition artifacts\",\n       prompt=\"\"\"\n       Based on transition {from-phase} → {to-phase}:\n\n       For inception → elaboration:\n       - intake\u002Fproject-intake-template.md\n       - requirements\u002Fvision-*.md\n       - management\u002Fbusiness-case-*.md\n       - management\u002Frisk-list.md\n       - security\u002Fdata-classification-template.md\n\n       For elaboration → construction:\n       - analysis-design\u002Fsoftware-architecture-doc-template.md\n       - requirements\u002Fsupplemental-specification-template.md\n       - test\u002Fmaster-test-plan-template.md\n       - management\u002Fdevelopment-case-template.md\n\n       Validate each artifact:\n       1. Present and complete\n       2. Reviewed and approved\n       3. Baselined (version tagged)\n\n       Output validation report:\n       .aiwg\u002Fworking\u002Fhandoff\u002Fartifacts\u002Fphase-artifacts-validation.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Validating artifacts...\n✓ Required artifacts: {found}\u002F{required}\n✓ Artifact completeness: {percentage}%\n```\n\n### Step 3: Execute Checklist Validation (Multi-Agent)\n\n**Purpose**: Validate all checklist items using specialized agents\n\n**Your Actions**:\n\n1. **Launch Parallel Checklist Validators**:\n\n   ```\n   # For Discovery → Delivery (DoR)\n\n   # Requirements Validator\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Validate requirements completeness\",\n       prompt=\"\"\"\n       Check Definition of Ready requirements criteria:\n\n       - [ ] Use-case brief authored\n       - [ ] Acceptance criteria defined\n       - [ ] Pre-conditions and post-conditions documented\n       - [ ] Happy path and alternative flows identified\n\n       For each item:\n       - Status: PASS | FAIL\n       - Evidence: File path or reference\n       - Issues: Description if failed\n\n       Output: .aiwg\u002Fworking\u002Fhandoff\u002Fchecklist\u002Frequirements-validation.md\n       \"\"\"\n   )\n\n   # Design Validator\n   Task(\n       subagent_type=\"architecture-designer\",\n       description=\"Validate design completeness\",\n       prompt=\"\"\"\n       Check Definition of Ready design criteria:\n\n       - [ ] Data contracts defined (if new entities)\n       - [ ] Interface specifications complete (if API changes)\n       - [ ] Integration points identified\n       - [ ] Backward compatibility validated\n\n       For each item:\n       - Status: PASS | FAIL\n       - Evidence: Documentation reference\n       - Issues: Gaps identified\n\n       Output: .aiwg\u002Fworking\u002Fhandoff\u002Fchecklist\u002Fdesign-validation.md\n       \"\"\"\n   )\n\n   # Risk Validator\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Validate risk management\",\n       prompt=\"\"\"\n       Check Definition of Ready risk criteria:\n\n       - [ ] High-risk assumptions validated\n       - [ ] Technical risks documented\n       - [ ] Dependencies identified and resolved\n       - [ ] No blocking risks without mitigation\n\n       For each item:\n       - Status: PASS | FAIL\n       - Evidence: Risk cards, spike results\n       - Issues: Unmitigated risks\n\n       Output: .aiwg\u002Fworking\u002Fhandoff\u002Fchecklist\u002Frisk-validation.md\n       \"\"\"\n   )\n   ```\n\n2. **For Delivery → Operations (ORR)**:\n\n   ```\n   # Code Completeness\n   Task(\n       subagent_type=\"software-implementer\",\n       description=\"Validate code completeness\",\n       prompt=\"\"\"\n       Check code completeness criteria:\n\n       - [ ] All planned features implemented\n       - [ ] Code peer-reviewed and approved\n       - [ ] Code merged to main branch\n       - [ ] No compiler warnings or linter errors\n       - [ ] Technical debt documented\n\n       Validate against:\n       - Pull request history\n       - Code review comments\n       - Build logs\n       - Static analysis reports\n\n       Output: .aiwg\u002Fworking\u002Fhandoff\u002Fchecklist\u002Fcode-validation.md\n       \"\"\"\n   )\n\n   # Test Completeness\n   Task(\n       subagent_type=\"test-engineer\",\n       description=\"Validate test completeness\",\n       prompt=\"\"\"\n       Check test completeness criteria:\n\n       - [ ] Unit test coverage ≥ 80%\n       - [ ] Integration tests passing 100%\n       - [ ] Acceptance tests passing\n       - [ ] Regression tests passing\n       - [ ] Performance tests passing\n       - [ ] Security scans passing\n\n       Validate against:\n       - Coverage reports\n       - Test execution results\n       - Performance benchmarks\n       - Security scan reports\n\n       Output: .aiwg\u002Fworking\u002Fhandoff\u002Fchecklist\u002Ftest-validation.md\n       \"\"\"\n   )\n\n   # Quality Gates\n   Task(\n       subagent_type=\"security-gatekeeper\",\n       description=\"Validate quality gates\",\n       prompt=\"\"\"\n       Check quality gate criteria:\n\n       Security Gate:\n       - [ ] SAST\u002FDAST scans clean\n       - [ ] No Critical\u002FHigh vulnerabilities\n\n       Reliability Gate:\n       - [ ] SLIs within targets\n       - [ ] Performance SLOs met\n\n       Documentation Gate:\n       - [ ] Release notes updated\n       - [ ] Runbooks complete\n\n       Traceability Gate:\n       - [ ] Requirements → code → tests verified\n\n       Output: .aiwg\u002Fworking\u002Fhandoff\u002Fchecklist\u002Fgates-validation.md\n       \"\"\"\n   )\n\n   # Operational Readiness\n   Task(\n       subagent_type=\"operations-manager\",\n       description=\"Validate operational readiness\",\n       prompt=\"\"\"\n       Check operational readiness criteria:\n\n       Deployment:\n       - [ ] Deployed to dev\u002Ftest\u002Fstaging successfully\n       - [ ] Feature flags configured\n       - [ ] Configuration changes documented\n\n       Operations:\n       - [ ] Monitoring and alerting configured\n       - [ ] Logging configured\n       - [ ] Backup and recovery tested\n       - [ ] Rollback plan tested\n\n       Support:\n       - [ ] Support plan in place\n       - [ ] Operations team trained\n       - [ ] Support team trained\n\n       Output: .aiwg\u002Fworking\u002Fhandoff\u002Fchecklist\u002Foperations-validation.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Running checklist validation (parallel agents)...\n✓ Requirements validation: PASS\n✓ Design validation: PASS\n✓ Risk validation: CONDITIONAL\n✓ Code validation: PASS\n✓ Test validation: PASS\n✓ Gates validation: PASS\n✓ Operations validation: CONDITIONAL\n```\n\n### Step 4: Obtain Signoffs\n\n**Purpose**: Track and obtain required signoffs from stakeholders\n\n**Your Actions**:\n\n1. **Identify Required Signoffs**:\n   ```\n   Based on handoff type, determine required signoffs:\n\n   Discovery → Delivery:\n   - Requirements Reviewer\n   - Product Owner\n   - Project Manager\n\n   Delivery → Operations:\n   - Deployment Manager\n   - Reliability Engineer\n   - Security Gatekeeper\n   - Operations Lead\n   - Support Lead\n\n   Phase Transitions:\n   - Executive Sponsor\n   - Architecture Owner\n   - Project Manager\n   ```\n\n2. **Generate Signoff Requests**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Generate signoff tracking\",\n       prompt=\"\"\"\n       Create signoff tracking for {handoff-type}:\n\n       Required Signoffs:\n       - {Role}: Status [OBTAINED | PENDING | DECLINED]\n         - Request Date: {date}\n         - Response Date: {date if obtained}\n         - Comments: {feedback}\n\n       For pending signoffs:\n       - Generate request summary\n       - List items requiring attention\n       - Provide checklist status\n\n       Output: .aiwg\u002Fworking\u002Fhandoff\u002Fsignoffs\u002Fsignoff-tracking.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Tracking signoffs...\n✓ Signoffs obtained: {obtained}\u002F{required}\n⚠️ Pending: {list of pending signoffs}\n```\n\n### Step 5: Synthesize Handoff Report\n\n**Purpose**: Generate comprehensive handoff validation report\n\n**Your Actions**:\n\n```\nTask(\n    subagent_type=\"documentation-synthesizer\",\n    description=\"Generate handoff validation report\",\n    prompt=\"\"\"\n    Read all validation results:\n    - .aiwg\u002Fworking\u002Fhandoff\u002Fartifacts\u002F*.md\n    - .aiwg\u002Fworking\u002Fhandoff\u002Fchecklist\u002F*.md\n    - .aiwg\u002Fworking\u002Fhandoff\u002Fsignoffs\u002F*.md\n\n    Generate Handoff Validation Report:\n\n    # Handoff Validation Report\n\n    **Handoff**: {from-phase} → {to-phase}\n    **Project**: {project-name}\n    **Date**: {current-date}\n\n    ## Overall Status\n\n    **Readiness**: {READY | PARTIAL | BLOCKED}\n    **Checklist Compliance**: {percentage}% ({passed}\u002F{total} items)\n    **Signoff Status**: {percentage}% ({obtained}\u002F{required})\n\n    **Handoff Decision**: {APPROVED | CONDITIONAL | REJECTED}\n\n    ## Artifact Validation\n\n    ### Required Artifacts ({passed}\u002F{total})\n    {for each required artifact}\n    - [ ] {artifact-name}\n      - Status: {PRESENT | MISSING | INCOMPLETE}\n      - Location: {file-path}\n      - Completeness: {percentage}%\n      - Issues: {list problems}\n\n    ## Checklist Results\n\n    ### {Category} ({passed}\u002F{total})\n    {for each checklist item}\n    - [ ] {criterion-description}\n      - Status: {PASS | FAIL}\n      - Evidence: {file-path or reference}\n      - Issues: {description if failed}\n\n    ## Signoff Status\n\n    **Required Signoffs** ({obtained}\u002F{required}):\n    - [ ] {Role}: {OBTAINED | PENDING | DECLINED}\n      - Comments: {feedback}\n\n    ## Handoff Decision\n\n    **Decision**: {APPROVED | CONDITIONAL | REJECTED}\n\n    **Rationale**:\n    {detailed reasoning based on validation results}\n\n    **Conditions** (if CONDITIONAL):\n    1. {condition that must be met}\n    2. {condition that must be met}\n\n    **Blockers** (if REJECTED):\n    1. {critical issue blocking handoff}\n    2. {critical issue blocking handoff}\n\n    ## Gaps and Remediation\n\n    ### Critical Gaps (Must Fix)\n    {list critical missing items}\n\n    **Remediation Actions**:\n    1. {action} - Owner: {role} - Due: {date}\n    2. {action} - Owner: {role} - Due: {date}\n\n    ### Non-Critical Gaps (Can Defer)\n    {list minor missing items}\n\n    **Deferral Plan**:\n    {how these will be addressed post-handoff}\n\n    ## Next Steps\n\n    **If APPROVED**:\n    - [ ] Schedule {to-phase} kickoff\n    - [ ] Transfer artifacts\n    - [ ] Assign {to-phase} team\n\n    **If CONDITIONAL**:\n    - [ ] Complete conditions\n    - [ ] Re-validate within {timeframe}\n\n    **If REJECTED**:\n    - [ ] Address critical gaps\n    - [ ] Re-run validation\n    - [ ] Target date: {date}\n\n    ## Recommendations\n\n    {process improvements}\n    {risk mitigations}\n    {communication adjustments}\n\n    Save to: .aiwg\u002Fhandoffs\u002Fhandoff-report-{from}-to-{to}-{date}.md\n    \"\"\"\n)\n```\n\n**Communicate Progress**:\n```\n⏳ Generating handoff report...\n✓ Handoff report complete: .aiwg\u002Fhandoffs\u002Fhandoff-report-{from}-to-{to}.md\n```\n\n### Step 6: Execute Handoff Package Creation\n\n**Purpose**: Create handoff package with all artifacts and context\n\n**Your Actions**:\n\n1. **For APPROVED Handoffs**:\n   ```\n   Task(\n       subagent_type=\"documentation-archivist\",\n       description=\"Create handoff package\",\n       prompt=\"\"\"\n       Create handoff package for {from-phase} → {to-phase}:\n\n       1. Tag artifacts in version control:\n          git tag {phase}-handoff-{YYYY-MM-DD}\n\n       2. Create handoff package:\n          .aiwg\u002Fhandoffs\u002F{from}-to-{to}\u002F\n          ├── artifacts\u002F      # Copy of all artifacts\n          ├── context\u002F        # Context transfer docs\n          ├── report.md       # Handoff report\n          └── README.md       # Package overview\n\n       3. Generate context transfer document:\n          - Key decisions made\n          - Outstanding risks\n          - Technical debt\n          - Lessons learned\n          - Team recommendations\n\n       4. Schedule handoff meeting:\n          - Date: Within 1 week\n          - Attendees: From and To teams\n          - Agenda: Context transfer\n\n       Output: .aiwg\u002Fhandoffs\u002F{from}-to-{to}\u002FREADME.md\n       \"\"\"\n   )\n   ```\n\n2. **For CONDITIONAL Handoffs**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Create conditional handoff plan\",\n       prompt=\"\"\"\n       Create action plan for conditional handoff:\n\n       1. List conditions to be met:\n          - {condition 1} - Owner - Due date\n          - {condition 2} - Owner - Due date\n\n       2. Create tracking mechanism:\n          - TodoWrite entries for each condition\n          - Daily check-ins scheduled\n\n       3. Set re-validation date:\n          - Target: {date}\n          - Validator: {role}\n\n       4. Define escalation path:\n          - If conditions not met by {date}\n          - Escalate to: {executive}\n\n       Output: .aiwg\u002Fhandoffs\u002Fconditional-plan-{from}-to-{to}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n✓ Handoff package created: .aiwg\u002Fhandoffs\u002F{from}-to-{to}\u002F\n✓ Version tagged: {phase}-handoff-{date}\n✓ Handoff meeting scheduled: {date}\n```\n\n## Quality Gates\n\nBefore marking workflow complete, verify:\n- [ ] All required artifacts validated\n- [ ] Checklist items assessed (100% coverage)\n- [ ] Signoff status tracked\n- [ ] Handoff decision clear (APPROVED\u002FCONDITIONAL\u002FREJECTED)\n- [ ] Remediation plan provided for gaps\n- [ ] Handoff package created (if approved)\n- [ ] Next steps documented\n\n## User Communication\n\n**At start**: Confirm understanding and handoff type\n\n```\nUnderstood. I'll validate the {from-phase} → {to-phase} handoff.\n\nThis will check:\n- Required artifacts presence and completeness\n- Checklist criteria compliance\n- Signoff status from stakeholders\n- Overall handoff readiness\n\nI'll coordinate multiple specialized agents for validation.\nExpected duration: 10-15 minutes.\n\nStarting handoff validation...\n```\n\n**During**: Update progress with clear indicators\n\n```\n✓ = Complete\u002FPass\n⏳ = In progress\n❌ = Failed\u002FMissing\n⚠️ = Warning\u002FConditional\n```\n\n**At end**: Summary report with decision and next steps\n\n```\n─────────────────────────────────────────────\nHandoff Validation Complete\n─────────────────────────────────────────────\n\n**Handoff**: Discovery → Delivery\n**Decision**: APPROVED\n\n**Summary**:\n✓ Artifacts: 12\u002F12 complete\n✓ Checklist: 95% compliant (19\u002F20 items)\n✓ Signoffs: 3\u002F3 obtained\n\n**Minor Gaps** (non-blocking):\n- Performance test scenarios need enhancement\n  → Can be addressed during sprint\n\n**Next Steps**:\n1. Review handoff report: .aiwg\u002Fhandoffs\u002Fhandoff-report-discovery-to-delivery.md\n2. Handoff meeting scheduled: Tuesday 10am\n3. Delivery team can begin sprint planning\n\n**Artifacts Transferred**:\n- 5 use case briefs\n- 5 acceptance test cards\n- 3 interface specifications\n- 2 spike results\n\nReady to proceed with Delivery phase.\n─────────────────────────────────────────────\n```\n\n## Error Handling\n\n**Unknown Handoff**:\n```\n❌ Unknown handoff: {from-phase} → {to-phase}\n\nSupported handoffs:\n- Phase: inception→elaboration, elaboration→construction, construction→transition\n- Track: discovery→delivery, delivery→operations\n- Special: intake→inception, concept→inception\n\nPlease specify a valid handoff type.\n```\n\n**Missing Critical Artifacts**:\n```\n❌ Critical artifacts missing - handoff BLOCKED\n\nMissing:\n- {artifact-1}: Required for {reason}\n- {artifact-2}: Required for {reason}\n\nThese must be completed before handoff.\nRecommended actions:\n1. Complete {artifact-1} using template\n2. Obtain stakeholder approval\n3. Re-run handoff validation\n\nImpact: Cannot proceed to {to-phase} until resolved.\n```\n\n**Failed Checklist Items**:\n```\n⚠️ Checklist compliance: {percentage}% (target: 100%)\n\nFailed items:\n- {item-1}: {reason for failure}\n- {item-2}: {reason for failure}\n\nRecommendation: Address failed items or obtain exception approval\n```\n\n**Declined Signoff**:\n```\n❌ Signoff declined by {role}\n\nReason: {feedback from role}\n\nActions required:\n1. Address concerns raised\n2. Update artifacts as needed\n3. Request re-review\n\nEscalation: Contact Project Manager if disagreement persists\n```\n\n## Success Criteria\n\nThis orchestration succeeds when:\n- [ ] Handoff type identified and validated\n- [ ] All required artifacts checked for presence\n- [ ] Artifact completeness assessed\n- [ ] Checklist items validated (100% coverage)\n- [ ] Signoff status determined\n- [ ] Handoff decision clear (APPROVED\u002FCONDITIONAL\u002FREJECTED)\n- [ ] Remediation plan provided for any gaps\n- [ ] Handoff report generated\n- [ ] Next steps documented\n\n## Metrics to Track\n\n**During orchestration, track**:\n- Artifact completeness: % of required artifacts present and complete\n- Checklist compliance: % of checklist items passing\n- Signoff rate: % of required signoffs obtained\n- Gap severity: Critical vs. non-critical gaps identified\n- Remediation effort: Estimated hours to close gaps\n- Handoff cycle time: Days from request to approval\n\n## References\n\n**Templates** (via $AIWG_ROOT):\n- Handoff checklists: `flows\u002Fhandoff-checklist-template.md`\n- Gate criteria: `flows\u002Fgate-criteria-by-phase.md`\n- ORR template: `deployment\u002Foperational-readiness-review-template.md`\n\n**Related Commands**:\n- Traceability: `commands\u002Fcheck-traceability.md`\n- Gate checks: `commands\u002Fflow-gate-check.md`\n- Phase transitions: `commands\u002Fflow-inception-to-elaboration.md`\n\n**Handoff Patterns**:\n- Definition of Ready: `docs\u002Fdefinition-of-ready-pattern.md`\n- Operational Readiness: `docs\u002Foperational-readiness-pattern.md`\n","> **Declarative Flow (#1539):** This flow's orchestration is now also expressed as a\n> declarative YAML Flow at `flows\u002Fflow-handoff-checklist.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# SDLC Handoff Checklist Flow\n\n**You are the Core Orchestrator** for validating and executing handoffs between SDLC phases and tracks.\n\n## Threat-assessment gate\n\nBefore signoff or packaging, resolve the active workspace member's\n`security.threatAssessment` policy and assess the synthesized handoff as\n`handoff` with `tools\u002Fsecurity\u002Fthreat-assessment.mjs`. Store the report with\nthe handoff evidence. Audit mode records `wouldAction` without interrupting;\nenforce-mode `flag`\u002F`require-authorization` pauses and `reject` blocks the\nhandoff. Off mode disables only this AIWG classifier.\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## Natural Language Triggers\n\nUsers may say:\n- \"Check handoff readiness to Delivery\"\n- \"Validate handoff from Discovery\"\n- \"Verify handoff readiness for Operations\"\n- \"Review handoff checklist\"\n- \"Check if we're ready for phase transition\"\n- \"Validate Definition of Ready\"\n- \"Run operational readiness review\"\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 handoff validation priorities\n\n**Examples**:\n```\n--guidance \"Focus on security compliance, SOC2 audit next month\"\n--guidance \"Quick validation, team is waiting to start\"\n--guidance \"Pay special attention to test coverage and documentation\"\n--guidance \"First handoff, need detailed validation\"\n```\n\n**How to Apply**:\n- Parse guidance for keywords: security, documentation, testing, compliance, speed\n- Adjust validation depth (comprehensive vs. essential checks)\n- Modify agent assignments (add specialized validators)\n- Influence priority ordering (critical checks first)\n\n### --interactive Parameter\n\n**Purpose**: You ask 5-7 strategic questions to understand handoff context\n\n**Questions to Ask** (if --interactive):\n\n```\nI'll ask 7 strategic questions to tailor the handoff validation:\n\nQ1: Is this your first handoff of this type?\n    (Helps me determine validation thoroughness needed)\n\nQ2: What's your biggest concern about this handoff?\n    (e.g., incomplete requirements, missing tests, documentation gaps)\n\nQ3: How urgent is this handoff?\n    (Influences whether to do comprehensive or essential checks)\n\nQ4: Are there any known gaps you're already aware of?\n    (Helps focus validation on unknown issues)\n\nQ5: Who are the key stakeholders who need to sign off?\n    (Determines which reviewers to engage)\n\nQ6: Are there any special compliance or regulatory requirements?\n    (e.g., HIPAA, SOC2, PCI-DSS affects validation criteria)\n\nQ7: What's your fallback plan if handoff is blocked?\n    (Helps prepare contingency recommendations)\n\nBased on your answers, I'll adjust:\n- Validation depth (comprehensive vs. streamlined)\n- Agent assignments (add specialized reviewers)\n- Priority ordering (critical items first)\n- Remediation recommendations\n```\n\n**Synthesize Guidance**: Combine answers into structured guidance for execution\n\n## Supported Handoffs\n\n### Phase Transitions\n- **inception → elaboration**: Lifecycle Objective Milestone handoff\n- **elaboration → construction**: Lifecycle Architecture Milestone handoff\n- **construction → transition**: Operational Capability Milestone handoff\n- **transition → operations**: Product Release Milestone handoff\n\n### Track Handoffs\n- **discovery → delivery**: Definition of Ready (DoR) validation\n- **delivery → operations**: Operational Readiness Review (ORR)\n- **delivery → discovery**: Feedback loop for rework\u002Fclarification\n\n### Special Handoffs\n- **intake → inception**: Project Intake to Inception kickoff\n- **concept → inception**: Concept to Inception flow start\n\n## Multi-Agent Orchestration Workflow\n\n### Step 1: Identify and Load Handoff Checklist\n\n**Purpose**: Determine which handoff checklist applies and load criteria\n\n**Your Actions**:\n\n1. **Parse Handoff Type**:\n   ```\n   Determine from user input:\n   - From phase\u002Ftrack\n   - To phase\u002Ftrack\n   - Type: Phase transition, Track handoff, or Special\n   ```\n\n2. **Load Checklist Criteria**:\n   ```\n   Based on handoff type, identify:\n   - Required artifacts\n   - Validation criteria\n   - Signoff requirements\n   - Pass threshold\n   ```\n\n3. **Initialize Validation Workspace**:\n   ```\n   Create workspace structure:\n   .aiwg\u002Fworking\u002Fhandoff\u002F\n   ├── artifacts\u002F      # Artifact validation results\n   ├── checklist\u002F      # Checklist item validation\n   ├── signoffs\u002F       # Signoff status tracking\n   └── report\u002F         # Final handoff report\n   ```\n\n**Communicate Progress**:\n```\n✓ Handoff identified: {from-phase} → {to-phase}\n✓ Checklist loaded: {checklist-name}\n⏳ Starting validation...\n```\n\n### Step 2: Validate Required Artifacts\n\n**Purpose**: Check presence and completeness of required artifacts\n\n**Your Actions**:\n\n1. **For Discovery → Delivery (Definition of Ready)**:\n   ```\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Validate Definition of Ready artifacts\",\n       prompt=\"\"\"\n       Check for required artifacts per backlog item:\n\n       Requirements:\n       - requirements\u002Fuse-case-brief-{ID}.md\n       - test\u002Facceptance-test-card-{ID}.md\n\n       Design (if applicable):\n       - analysis-design\u002Fdata-contract-card-{ID}.md\n       - analysis-design\u002Finterface-card-{ID}.md\n\n       Risk Management:\n       - management\u002Frisk-card-{ID}.md (if high-risk)\n       - analysis-design\u002Fspike-card-{ID}.md (if spike conducted)\n\n       For each artifact:\n       1. Check existence (file present)\n       2. Validate completeness (all sections filled)\n       3. Check approval status (stakeholder signoff)\n       4. Verify currency (last updated within sprint)\n\n       Output validation report:\n       .aiwg\u002Fworking\u002Fhandoff\u002Fartifacts\u002Fdor-artifacts-validation.md\n       \"\"\"\n   )\n   ```\n\n2. **For Delivery → Operations (Operational Readiness)**:\n   ```\n   Task(\n       subagent_type=\"documentation-archivist\",\n       description=\"Validate Operational Readiness artifacts\",\n       prompt=\"\"\"\n       Check for required deployment artifacts:\n\n       Deployment:\n       - deployment\u002Fdeployment-plan-template.md\n       - deployment\u002Frelease-notes-template.md\n       - deployment\u002Frunbook-*.md\n\n       Testing:\n       - test\u002Ftest-evaluation-summary-template.md\n       - test\u002Facceptance-test-results-*.md\n\n       Operations:\n       - deployment\u002Foperational-readiness-review-template.md\n       - support\u002Fsupport-plan-template.md\n       - training\u002Fuser-guide-template.md\n\n       For each artifact:\n       1. Verify existence and completeness\n       2. Check version currency (matches release)\n       3. Validate technical accuracy\n       4. Confirm operational procedures documented\n\n       Output validation report:\n       .aiwg\u002Fworking\u002Fhandoff\u002Fartifacts\u002Forr-artifacts-validation.md\n       \"\"\"\n   )\n   ```\n\n3. **For Phase Transitions**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Validate phase transition artifacts\",\n       prompt=\"\"\"\n       Based on transition {from-phase} → {to-phase}:\n\n       For inception → elaboration:\n       - intake\u002Fproject-intake-template.md\n       - requirements\u002Fvision-*.md\n       - management\u002Fbusiness-case-*.md\n       - management\u002Frisk-list.md\n       - security\u002Fdata-classification-template.md\n\n       For elaboration → construction:\n       - analysis-design\u002Fsoftware-architecture-doc-template.md\n       - requirements\u002Fsupplemental-specification-template.md\n       - test\u002Fmaster-test-plan-template.md\n       - management\u002Fdevelopment-case-template.md\n\n       Validate each artifact:\n       1. Present and complete\n       2. Reviewed and approved\n       3. Baselined (version tagged)\n\n       Output validation report:\n       .aiwg\u002Fworking\u002Fhandoff\u002Fartifacts\u002Fphase-artifacts-validation.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Validating artifacts...\n✓ Required artifacts: {found}\u002F{required}\n✓ Artifact completeness: {percentage}%\n```\n\n### Step 3: Execute Checklist Validation (Multi-Agent)\n\n**Purpose**: Validate all checklist items using specialized agents\n\n**Your Actions**:\n\n1. **Launch Parallel Checklist Validators**:\n\n   ```\n   # For Discovery → Delivery (DoR)\n\n   # Requirements Validator\n   Task(\n       subagent_type=\"requirements-analyst\",\n       description=\"Validate requirements completeness\",\n       prompt=\"\"\"\n       Check Definition of Ready requirements criteria:\n\n       - [ ] Use-case brief authored\n       - [ ] Acceptance criteria defined\n       - [ ] Pre-conditions and post-conditions documented\n       - [ ] Happy path and alternative flows identified\n\n       For each item:\n       - Status: PASS | FAIL\n       - Evidence: File path or reference\n       - Issues: Description if failed\n\n       Output: .aiwg\u002Fworking\u002Fhandoff\u002Fchecklist\u002Frequirements-validation.md\n       \"\"\"\n   )\n\n   # Design Validator\n   Task(\n       subagent_type=\"architecture-designer\",\n       description=\"Validate design completeness\",\n       prompt=\"\"\"\n       Check Definition of Ready design criteria:\n\n       - [ ] Data contracts defined (if new entities)\n       - [ ] Interface specifications complete (if API changes)\n       - [ ] Integration points identified\n       - [ ] Backward compatibility validated\n\n       For each item:\n       - Status: PASS | FAIL\n       - Evidence: Documentation reference\n       - Issues: Gaps identified\n\n       Output: .aiwg\u002Fworking\u002Fhandoff\u002Fchecklist\u002Fdesign-validation.md\n       \"\"\"\n   )\n\n   # Risk Validator\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Validate risk management\",\n       prompt=\"\"\"\n       Check Definition of Ready risk criteria:\n\n       - [ ] High-risk assumptions validated\n       - [ ] Technical risks documented\n       - [ ] Dependencies identified and resolved\n       - [ ] No blocking risks without mitigation\n\n       For each item:\n       - Status: PASS | FAIL\n       - Evidence: Risk cards, spike results\n       - Issues: Unmitigated risks\n\n       Output: .aiwg\u002Fworking\u002Fhandoff\u002Fchecklist\u002Frisk-validation.md\n       \"\"\"\n   )\n   ```\n\n2. **For Delivery → Operations (ORR)**:\n\n   ```\n   # Code Completeness\n   Task(\n       subagent_type=\"software-implementer\",\n       description=\"Validate code completeness\",\n       prompt=\"\"\"\n       Check code completeness criteria:\n\n       - [ ] All planned features implemented\n       - [ ] Code peer-reviewed and approved\n       - [ ] Code merged to main branch\n       - [ ] No compiler warnings or linter errors\n       - [ ] Technical debt documented\n\n       Validate against:\n       - Pull request history\n       - Code review comments\n       - Build logs\n       - Static analysis reports\n\n       Output: .aiwg\u002Fworking\u002Fhandoff\u002Fchecklist\u002Fcode-validation.md\n       \"\"\"\n   )\n\n   # Test Completeness\n   Task(\n       subagent_type=\"test-engineer\",\n       description=\"Validate test completeness\",\n       prompt=\"\"\"\n       Check test completeness criteria:\n\n       - [ ] Unit test coverage ≥ 80%\n       - [ ] Integration tests passing 100%\n       - [ ] Acceptance tests passing\n       - [ ] Regression tests passing\n       - [ ] Performance tests passing\n       - [ ] Security scans passing\n\n       Validate against:\n       - Coverage reports\n       - Test execution results\n       - Performance benchmarks\n       - Security scan reports\n\n       Output: .aiwg\u002Fworking\u002Fhandoff\u002Fchecklist\u002Ftest-validation.md\n       \"\"\"\n   )\n\n   # Quality Gates\n   Task(\n       subagent_type=\"security-gatekeeper\",\n       description=\"Validate quality gates\",\n       prompt=\"\"\"\n       Check quality gate criteria:\n\n       Security Gate:\n       - [ ] SAST\u002FDAST scans clean\n       - [ ] No Critical\u002FHigh vulnerabilities\n\n       Reliability Gate:\n       - [ ] SLIs within targets\n       - [ ] Performance SLOs met\n\n       Documentation Gate:\n       - [ ] Release notes updated\n       - [ ] Runbooks complete\n\n       Traceability Gate:\n       - [ ] Requirements → code → tests verified\n\n       Output: .aiwg\u002Fworking\u002Fhandoff\u002Fchecklist\u002Fgates-validation.md\n       \"\"\"\n   )\n\n   # Operational Readiness\n   Task(\n       subagent_type=\"operations-manager\",\n       description=\"Validate operational readiness\",\n       prompt=\"\"\"\n       Check operational readiness criteria:\n\n       Deployment:\n       - [ ] Deployed to dev\u002Ftest\u002Fstaging successfully\n       - [ ] Feature flags configured\n       - [ ] Configuration changes documented\n\n       Operations:\n       - [ ] Monitoring and alerting configured\n       - [ ] Logging configured\n       - [ ] Backup and recovery tested\n       - [ ] Rollback plan tested\n\n       Support:\n       - [ ] Support plan in place\n       - [ ] Operations team trained\n       - [ ] Support team trained\n\n       Output: .aiwg\u002Fworking\u002Fhandoff\u002Fchecklist\u002Foperations-validation.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Running checklist validation (parallel agents)...\n✓ Requirements validation: PASS\n✓ Design validation: PASS\n✓ Risk validation: CONDITIONAL\n✓ Code validation: PASS\n✓ Test validation: PASS\n✓ Gates validation: PASS\n✓ Operations validation: CONDITIONAL\n```\n\n### Step 4: Obtain Signoffs\n\n**Purpose**: Track and obtain required signoffs from stakeholders\n\n**Your Actions**:\n\n1. **Identify Required Signoffs**:\n   ```\n   Based on handoff type, determine required signoffs:\n\n   Discovery → Delivery:\n   - Requirements Reviewer\n   - Product Owner\n   - Project Manager\n\n   Delivery → Operations:\n   - Deployment Manager\n   - Reliability Engineer\n   - Security Gatekeeper\n   - Operations Lead\n   - Support Lead\n\n   Phase Transitions:\n   - Executive Sponsor\n   - Architecture Owner\n   - Project Manager\n   ```\n\n2. **Generate Signoff Requests**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Generate signoff tracking\",\n       prompt=\"\"\"\n       Create signoff tracking for {handoff-type}:\n\n       Required Signoffs:\n       - {Role}: Status [OBTAINED | PENDING | DECLINED]\n         - Request Date: {date}\n         - Response Date: {date if obtained}\n         - Comments: {feedback}\n\n       For pending signoffs:\n       - Generate request summary\n       - List items requiring attention\n       - Provide checklist status\n\n       Output: .aiwg\u002Fworking\u002Fhandoff\u002Fsignoffs\u002Fsignoff-tracking.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n⏳ Tracking signoffs...\n✓ Signoffs obtained: {obtained}\u002F{required}\n⚠️ Pending: {list of pending signoffs}\n```\n\n### Step 5: Synthesize Handoff Report\n\n**Purpose**: Generate comprehensive handoff validation report\n\n**Your Actions**:\n\n```\nTask(\n    subagent_type=\"documentation-synthesizer\",\n    description=\"Generate handoff validation report\",\n    prompt=\"\"\"\n    Read all validation results:\n    - .aiwg\u002Fworking\u002Fhandoff\u002Fartifacts\u002F*.md\n    - .aiwg\u002Fworking\u002Fhandoff\u002Fchecklist\u002F*.md\n    - .aiwg\u002Fworking\u002Fhandoff\u002Fsignoffs\u002F*.md\n\n    Generate Handoff Validation Report:\n\n    # Handoff Validation Report\n\n    **Handoff**: {from-phase} → {to-phase}\n    **Project**: {project-name}\n    **Date**: {current-date}\n\n    ## Overall Status\n\n    **Readiness**: {READY | PARTIAL | BLOCKED}\n    **Checklist Compliance**: {percentage}% ({passed}\u002F{total} items)\n    **Signoff Status**: {percentage}% ({obtained}\u002F{required})\n\n    **Handoff Decision**: {APPROVED | CONDITIONAL | REJECTED}\n\n    ## Artifact Validation\n\n    ### Required Artifacts ({passed}\u002F{total})\n    {for each required artifact}\n    - [ ] {artifact-name}\n      - Status: {PRESENT | MISSING | INCOMPLETE}\n      - Location: {file-path}\n      - Completeness: {percentage}%\n      - Issues: {list problems}\n\n    ## Checklist Results\n\n    ### {Category} ({passed}\u002F{total})\n    {for each checklist item}\n    - [ ] {criterion-description}\n      - Status: {PASS | FAIL}\n      - Evidence: {file-path or reference}\n      - Issues: {description if failed}\n\n    ## Signoff Status\n\n    **Required Signoffs** ({obtained}\u002F{required}):\n    - [ ] {Role}: {OBTAINED | PENDING | DECLINED}\n      - Comments: {feedback}\n\n    ## Handoff Decision\n\n    **Decision**: {APPROVED | CONDITIONAL | REJECTED}\n\n    **Rationale**:\n    {detailed reasoning based on validation results}\n\n    **Conditions** (if CONDITIONAL):\n    1. {condition that must be met}\n    2. {condition that must be met}\n\n    **Blockers** (if REJECTED):\n    1. {critical issue blocking handoff}\n    2. {critical issue blocking handoff}\n\n    ## Gaps and Remediation\n\n    ### Critical Gaps (Must Fix)\n    {list critical missing items}\n\n    **Remediation Actions**:\n    1. {action} - Owner: {role} - Due: {date}\n    2. {action} - Owner: {role} - Due: {date}\n\n    ### Non-Critical Gaps (Can Defer)\n    {list minor missing items}\n\n    **Deferral Plan**:\n    {how these will be addressed post-handoff}\n\n    ## Next Steps\n\n    **If APPROVED**:\n    - [ ] Schedule {to-phase} kickoff\n    - [ ] Transfer artifacts\n    - [ ] Assign {to-phase} team\n\n    **If CONDITIONAL**:\n    - [ ] Complete conditions\n    - [ ] Re-validate within {timeframe}\n\n    **If REJECTED**:\n    - [ ] Address critical gaps\n    - [ ] Re-run validation\n    - [ ] Target date: {date}\n\n    ## Recommendations\n\n    {process improvements}\n    {risk mitigations}\n    {communication adjustments}\n\n    Save to: .aiwg\u002Fhandoffs\u002Fhandoff-report-{from}-to-{to}-{date}.md\n    \"\"\"\n)\n```\n\n**Communicate Progress**:\n```\n⏳ Generating handoff report...\n✓ Handoff report complete: .aiwg\u002Fhandoffs\u002Fhandoff-report-{from}-to-{to}.md\n```\n\n### Step 6: Execute Handoff Package Creation\n\n**Purpose**: Create handoff package with all artifacts and context\n\n**Your Actions**:\n\n1. **For APPROVED Handoffs**:\n   ```\n   Task(\n       subagent_type=\"documentation-archivist\",\n       description=\"Create handoff package\",\n       prompt=\"\"\"\n       Create handoff package for {from-phase} → {to-phase}:\n\n       1. Tag artifacts in version control:\n          git tag {phase}-handoff-{YYYY-MM-DD}\n\n       2. Create handoff package:\n          .aiwg\u002Fhandoffs\u002F{from}-to-{to}\u002F\n          ├── artifacts\u002F      # Copy of all artifacts\n          ├── context\u002F        # Context transfer docs\n          ├── report.md       # Handoff report\n          └── README.md       # Package overview\n\n       3. Generate context transfer document:\n          - Key decisions made\n          - Outstanding risks\n          - Technical debt\n          - Lessons learned\n          - Team recommendations\n\n       4. Schedule handoff meeting:\n          - Date: Within 1 week\n          - Attendees: From and To teams\n          - Agenda: Context transfer\n\n       Output: .aiwg\u002Fhandoffs\u002F{from}-to-{to}\u002FREADME.md\n       \"\"\"\n   )\n   ```\n\n2. **For CONDITIONAL Handoffs**:\n   ```\n   Task(\n       subagent_type=\"project-manager\",\n       description=\"Create conditional handoff plan\",\n       prompt=\"\"\"\n       Create action plan for conditional handoff:\n\n       1. List conditions to be met:\n          - {condition 1} - Owner - Due date\n          - {condition 2} - Owner - Due date\n\n       2. Create tracking mechanism:\n          - TodoWrite entries for each condition\n          - Daily check-ins scheduled\n\n       3. Set re-validation date:\n          - Target: {date}\n          - Validator: {role}\n\n       4. Define escalation path:\n          - If conditions not met by {date}\n          - Escalate to: {executive}\n\n       Output: .aiwg\u002Fhandoffs\u002Fconditional-plan-{from}-to-{to}.md\n       \"\"\"\n   )\n   ```\n\n**Communicate Progress**:\n```\n✓ Handoff package created: .aiwg\u002Fhandoffs\u002F{from}-to-{to}\u002F\n✓ Version tagged: {phase}-handoff-{date}\n✓ Handoff meeting scheduled: {date}\n```\n\n## Quality Gates\n\nBefore marking workflow complete, verify:\n- [ ] All required artifacts validated\n- [ ] Checklist items assessed (100% coverage)\n- [ ] Signoff status tracked\n- [ ] Handoff decision clear (APPROVED\u002FCONDITIONAL\u002FREJECTED)\n- [ ] Remediation plan provided for gaps\n- [ ] Handoff package created (if approved)\n- [ ] Next steps documented\n\n## User Communication\n\n**At start**: Confirm understanding and handoff type\n\n```\nUnderstood. I'll validate the {from-phase} → {to-phase} handoff.\n\nThis will check:\n- Required artifacts presence and completeness\n- Checklist criteria compliance\n- Signoff status from stakeholders\n- Overall handoff readiness\n\nI'll coordinate multiple specialized agents for validation.\nExpected duration: 10-15 minutes.\n\nStarting handoff validation...\n```\n\n**During**: Update progress with clear indicators\n\n```\n✓ = Complete\u002FPass\n⏳ = In progress\n❌ = Failed\u002FMissing\n⚠️ = Warning\u002FConditional\n```\n\n**At end**: Summary report with decision and next steps\n\n```\n─────────────────────────────────────────────\nHandoff Validation Complete\n─────────────────────────────────────────────\n\n**Handoff**: Discovery → Delivery\n**Decision**: APPROVED\n\n**Summary**:\n✓ Artifacts: 12\u002F12 complete\n✓ Checklist: 95% compliant (19\u002F20 items)\n✓ Signoffs: 3\u002F3 obtained\n\n**Minor Gaps** (non-blocking):\n- Performance test scenarios need enhancement\n  → Can be addressed during sprint\n\n**Next Steps**:\n1. Review handoff report: .aiwg\u002Fhandoffs\u002Fhandoff-report-discovery-to-delivery.md\n2. Handoff meeting scheduled: Tuesday 10am\n3. Delivery team can begin sprint planning\n\n**Artifacts Transferred**:\n- 5 use case briefs\n- 5 acceptance test cards\n- 3 interface specifications\n- 2 spike results\n\nReady to proceed with Delivery phase.\n─────────────────────────────────────────────\n```\n\n## Error Handling\n\n**Unknown Handoff**:\n```\n❌ Unknown handoff: {from-phase} → {to-phase}\n\nSupported handoffs:\n- Phase: inception→elaboration, elaboration→construction, construction→transition\n- Track: discovery→delivery, delivery→operations\n- Special: intake→inception, concept→inception\n\nPlease specify a valid handoff type.\n```\n\n**Missing Critical Artifacts**:\n```\n❌ Critical artifacts missing - handoff BLOCKED\n\nMissing:\n- {artifact-1}: Required for {reason}\n- {artifact-2}: Required for {reason}\n\nThese must be completed before handoff.\nRecommended actions:\n1. Complete {artifact-1} using template\n2. Obtain stakeholder approval\n3. Re-run handoff validation\n\nImpact: Cannot proceed to {to-phase} until resolved.\n```\n\n**Failed Checklist Items**:\n```\n⚠️ Checklist compliance: {percentage}% (target: 100%)\n\nFailed items:\n- {item-1}: {reason for failure}\n- {item-2}: {reason for failure}\n\nRecommendation: Address failed items or obtain exception approval\n```\n\n**Declined Signoff**:\n```\n❌ Signoff declined by {role}\n\nReason: {feedback from role}\n\nActions required:\n1. Address concerns raised\n2. Update artifacts as needed\n3. Request re-review\n\nEscalation: Contact Project Manager if disagreement persists\n```\n\n## Success Criteria\n\nThis orchestration succeeds when:\n- [ ] Handoff type identified and validated\n- [ ] All required artifacts checked for presence\n- [ ] Artifact completeness assessed\n- [ ] Checklist items validated (100% coverage)\n- [ ] Signoff status determined\n- [ ] Handoff decision clear (APPROVED\u002FCONDITIONAL\u002FREJECTED)\n- [ ] Remediation plan provided for any gaps\n- [ ] Handoff report generated\n- [ ] Next steps documented\n\n## Metrics to Track\n\n**During orchestration, track**:\n- Artifact completeness: % of required artifacts present and complete\n- Checklist compliance: % of checklist items passing\n- Signoff rate: % of required signoffs obtained\n- Gap severity: Critical vs. non-critical gaps identified\n- Remediation effort: Estimated hours to close gaps\n- Handoff cycle time: Days from request to approval\n\n## References\n\n**Templates** (via $AIWG_ROOT):\n- Handoff checklists: `flows\u002Fhandoff-checklist-template.md`\n- Gate criteria: `flows\u002Fgate-criteria-by-phase.md`\n- ORR template: `deployment\u002Foperational-readiness-review-template.md`\n\n**Related Commands**:\n- Traceability: `commands\u002Fcheck-traceability.md`\n- Gate checks: `commands\u002Fflow-gate-check.md`\n- Phase transitions: `commands\u002Fflow-inception-to-elaboration.md`\n\n**Handoff Patterns**:\n- Definition of Ready: `docs\u002Fdefinition-of-ready-pattern.md`\n- Operational Readiness: `docs\u002Foperational-readiness-pattern.md`\n",{"name":5,"namespace":51,"platforms":52,"commandHint":54,"description":7},"aiwg",[53],"all",{"model":32,"category":55,"modelRole":40,"modelTier":56,"allowedTools":57,"argumentHint":58,"orchestration":59},"sdlc-orchestration","standard","Task, Read, Write, Glob, TodoWrite","\u003Cfrom-phase> \u003Cto-phase> [project-directory] [--guidance \"text\"] [--interactive]",true,"main","6754967c344ccb087a8de06972f55a41067b291b","agentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fskills\u002Fflow-handoff-checklist",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":71,"prompt":81,"zipAvailable":59},[72,75,78],{"tool":73,"command":74},"npx","npx skills add jmagly\u002Faiwg --skill flow-handoff-checklist",{"tool":76,"command":77},"bunx","bunx skills add jmagly\u002Faiwg --skill flow-handoff-checklist",{"tool":79,"command":80},"pnpm","pnpm dlx skills add jmagly\u002Faiwg --skill flow-handoff-checklist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fskills\u002Fflow-handoff-checklist\u002FSKILL.md",[83],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"agents\u002Fopenai.yaml","REFERENCE","参考文档",43,"https:\u002F\u002Fgithub.com\u002Foscarrenalias\u002Ftakt\u002Fblob\u002Fmain\u002Fsrc\u002Fagent_takt\u002F_data\u002Ftemplates\u002Fskills\u002Ftask\u002Fspec-intake\u002Fagents\u002Fopenai.yaml",[90,117,140,146,153,165],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":97,"publishedAt":46},"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",[96],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[98,99,100,39,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116],"host","host hardening","hardening","re","recommendations","remediation","plan","port","verification","Bash","access","only","retention","audit","never","firewall","bind","secrets","request",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":127,"publishedAt":46},"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",[123,126],{"categoryNo":124,"categoryName":125,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[128,129,130,39,131,105,132,133,107,134,98,135,109,136,137,112,113,138,139,38],"exposure analysis","analysis","unknown","credentials","collection","ufw","ports","internet","local","scope","reconstruction","operator",{"skillNo":141,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":145,"publishedAt":46},"01M70P8QATMPKA78E4FT5D2TNA","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[144],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[100,98,99,108,39,116,103,102,111,104,105,106,107,115,109,110,101,112,113,114],{"skillNo":147,"name":119,"nameZh":6,"description":120,"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":152,"publishedAt":46},"01M70NMPVJ5H0JH131P60FW4R8","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[150,151],{"categoryNo":124,"categoryName":125,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[129,128,112,131,105,132,107,130,98,135,109,136,137,39,113,134,133,138,139,38],{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":160,"publishedAt":46},"01M6CB4DDR0B4NNCFK7ZK7449H","fixture-skill","Exercise rule delivery.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Frule-delivery\u002Fskills\u002Ffixture-skill\u002FSKILL.md",[159],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[161,162,163,34,30,164],"fixture skill","fixture","rule","exercise",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":172,"publishedAt":46},"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",[171],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[173,174,136,175,162],"pi","pi local","duplicate"]