[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C2R7FWSV57TFCCPCBZSJT0":3,"skill-same:01M6C2R7FWSV57TFCCPCBZSJT0":84},{"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":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":69,"updatedAt":70,"install":71,"resources":83},"01M6C2R7FWSV57TFCCPCBZSJT0","flow-gate-check",null,"Orchestrate SDLC phase gate validation with multi-agent review and comprehensive reporting","jmagly\u002Faiwg","jmagly","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1159087?v=4","01M6C10AK8N2WCSQN11FYGTJWN","Joseph Magly","01M6C10AQ8A2RMED1Y1BSVY7NF",229,"MIT","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fcodex-sdlc\u002Fskills\u002Fflow-gate-check\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,46],"gate check","flow","gate","flow gate check","check","read","phase","phase gate","true","sonnet","project","sdlc","interactive","write","directory","coding","multi-agent","text","reporting","orchestrate","validation","orchestration","review","2026-11-10 10:12:30",false,"---\nnamespace: aiwg\nname: flow-gate-check\nplatforms: [all]\ndescription: Orchestrate SDLC phase gate validation with multi-agent review and comprehensive reporting\ncommandHint:\n  argumentHint: \u003Cphase-or-gate-name> [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-gate-check.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 Gate Check Orchestration\n\n**You are the Core Orchestrator** for SDLC phase gate validation.\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- \"Can we transition to {phase}?\"\n- \"Are we ready for {phase}?\"\n- \"Validate gate criteria\"\n- \"Check if we can proceed\"\n- \"Gate validation for {phase}\"\n- \"Check {phase} readiness\"\n- \"Is the {milestone} complete?\"\n- \"Run gate check for {phase}\"\n- \"Validate our readiness to move forward\"\n\nYou recognize these as requests for this orchestration flow.\n\n## Parameter Handling\n\n### Phase\u002FGate Identification\n\n**Supported Gates**:\n\n**Phase Milestones**:\n- `inception` \u002F `LOM` - Lifecycle Objective Milestone\n- `elaboration` \u002F `ABM` - Architecture Baseline Milestone\n- `construction` \u002F `IOC` - Initial Operational Capability\n- `transition` \u002F `PR` - Product Release\n\n**Workflow Gates**:\n- `discovery` - Discovery Track Definition of Ready\n- `delivery` - Delivery Track Definition of Done\n- `security` - Security validation\n- `reliability` - Performance and SLO compliance\n- `test-coverage` - Test coverage thresholds\n- `documentation` - Documentation completeness\n- `traceability` - Requirements → code → tests\n- `12-factor` - 12-factor app methodology compliance (opt-in, cloud-native targets)\n\n**Special Gates**:\n- `all` - Run all applicable gates\n- `pre-deploy` - Pre-deployment readiness\n- `orr` - Operational Readiness Review\n\n### --guidance Parameter\n\n**Purpose**: User provides upfront direction to tailor validation priorities\n\n**Examples**:\n```\n--guidance \"Focus on security compliance, HIPAA critical\"\n--guidance \"Time-constrained, prioritize minimum viable gates\"\n--guidance \"Enterprise deployment, need full compliance validation\"\n```\n\n**How to Apply**:\n- Parse guidance for keywords: security, compliance, timeline, quality\n- Adjust validation depth (comprehensive vs. essential)\n- Influence agent assignments (add specialized validators)\n- Modify reporting detail level\n\n### --interactive Parameter\n\n**Purpose**: You ask 3-5 strategic questions to understand context\n\n**Questions to Ask** (if --interactive):\n\n```\nI'll ask strategic questions to tailor the gate validation:\n\nQ1: What's your primary concern for this gate check?\n    (e.g., compliance readiness, technical quality, team preparedness)\n\nQ2: Are there any known issues or gaps you're concerned about?\n    (Help me focus validation on problem areas)\n\nQ3: What's your timeline for passing this gate?\n    (Influences whether to report quick-fixes vs. comprehensive remediation)\n\nQ4: Who needs to sign off on this gate?\n    (Helps identify which specialized reviewers to involve)\n\nQ5: What happens if the gate doesn't pass?\n    (Helps determine how strict validation should be)\n```\n\n## Multi-Agent Orchestration Workflow\n\n### Step 1: Determine Gate Context\n\n**Purpose**: Identify which gate to validate and current project state\n\n**Your Actions**:\n\n1. **Parse Gate Parameter**:\n   ```\n   Map user input to gate type:\n   - \"inception\" | \"LOM\" → Lifecycle Objective Milestone\n   - \"elaboration\" | \"ABM\" → Architecture Baseline Milestone\n   - \"construction\" | \"IOC\" → Initial Operational Capability\n   - \"transition\" | \"PR\" → Product Release\n   - Others → Workflow or special gates\n   ```\n\n2. **Scan Project State**:\n   ```\n   Use Glob to check for phase indicators:\n   - .aiwg\u002Fintake\u002F* → Likely in Inception\n   - .aiwg\u002Farchitecture\u002Fsoftware-architecture-doc.md → Likely post-Elaboration\n   - .aiwg\u002Ftesting\u002Ftest-results\u002F* → Likely in Construction\n   - .aiwg\u002Fdeployment\u002Fproduction-deploy.md → Likely in Transition\n   ```\n\n**Communicate Progress**:\n```\n✓ Gate identified: {gate-name}\n⏳ Scanning project state...\n✓ Current phase detected: {phase}\n```\n\n### Step 2: Phase Gate Validation (LOM\u002FABM\u002FIOC\u002FPR)\n\n#### 2.1: Inception Gate (LOM) Validation\n\n**When**: User requests \"inception\", \"LOM\", or system detects Inception phase\n\n**Launch Validation Agents**:\n\n```\n# Primary Validator\nTask(\n    subagent_type=\"project-manager\",\n    description=\"Validate Lifecycle Objective Milestone criteria\",\n    prompt=\"\"\"\n    Read gate criteria from: $AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fflows\u002Fgate-criteria-by-phase.md\n\n    Check for required Inception artifacts:\n    - .aiwg\u002Fintake\u002Fproject-intake.md (COMPLETE)\n    - .aiwg\u002Frequirements\u002Fvision-*.md (APPROVED)\n    - .aiwg\u002Fplanning\u002Fbusiness-case-*.md (APPROVED)\n    - .aiwg\u002Frisks\u002Frisk-list.md (BASELINED)\n    - .aiwg\u002Fsecurity\u002Fdata-classification.md (COMPLETE)\n\n    Validate LOM criteria:\n    - Vision document APPROVED (stakeholder signoff ≥75%)\n    - Business case APPROVED (funding secured)\n    - Risk list BASELINED (5-10 risks, top 3 have mitigation)\n    - Data classification COMPLETE\n    - Initial architecture documented\n    - Executive Sponsor approval obtained\n\n    Generate validation report:\n    - Status: PASS | FAIL | CONDITIONAL\n    - Missing artifacts list\n    - Failed criteria with reasons\n    - Signoff status\n    - Remediation actions\n\n    Save to: .aiwg\u002Fgates\u002Flom-validation-report.md\n    \"\"\"\n)\n\n# Parallel Specialized Reviewers\nTask(\n    subagent_type=\"business-analyst\",\n    description=\"Validate business readiness for LOM\",\n    prompt=\"\"\"\n    Review business artifacts:\n    - Business case viability\n    - Stakeholder alignment\n    - Funding adequacy\n    - Vision clarity\n\n    Report business readiness: READY | GAPS | BLOCKED\n    Save to: .aiwg\u002Fgates\u002Flom-business-review.md\n    \"\"\"\n)\n\nTask(\n    subagent_type=\"security-architect\",\n    description=\"Validate security readiness for LOM\",\n    prompt=\"\"\"\n    Review security artifacts:\n    - Data classification completeness\n    - Initial threat assessment\n    - Compliance requirements identified\n    - Security risks documented\n\n    Report security readiness: READY | GAPS | BLOCKED\n    Save to: .aiwg\u002Fgates\u002Flom-security-review.md\n    \"\"\"\n)\n```\n\n#### 2.2: Elaboration Gate (ABM) Validation\n\n**When**: User requests \"elaboration\", \"ABM\", or system detects Elaboration phase\n\n**Launch Validation Agents**:\n\n```\n# Primary Validator\nTask(\n    subagent_type=\"project-manager\",\n    description=\"Validate Architecture Baseline Milestone criteria\",\n    prompt=\"\"\"\n    Read gate criteria from: $AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fflows\u002Fgate-criteria-by-phase.md\n\n    Check for required Elaboration artifacts:\n    - .aiwg\u002Farchitecture\u002Fsoftware-architecture-doc.md (BASELINED)\n    - .aiwg\u002Farchitecture\u002Fadr\u002F*.md (3-5 ADRs)\n    - .aiwg\u002Frequirements\u002Fsupplemental-specification.md (COMPLETE)\n    - .aiwg\u002Ftesting\u002Fmaster-test-plan.md (APPROVED)\n    - .aiwg\u002Frisks\u002Frisk-retirement-report.md\n\n    Check for Layer 3 behavioral specifications:\n    - .aiwg\u002Frequirements\u002Frealizations\u002FDES-UCR-*.md (use case realizations)\n    - .aiwg\u002Farchitecture\u002Fstate-machines\u002FDES-SM-*.md (state machine specs)\n    - .aiwg\u002Farchitecture\u002Fdecision-tables\u002FDES-DT-*.md (decision tables)\n    - .aiwg\u002Farchitecture\u002Fmethod-contracts\u002FDES-MIC-*.md (method interface contracts)\n    - .aiwg\u002Farchitecture\u002Factivity-diagrams\u002FDES-ACT-*.md (activity diagrams)\n\n    Validate ABM criteria:\n    - Architecture BASELINED and peer-reviewed\n    - ADRs documented (3-5 major decisions)\n    - Risks ≥70% retired or mitigated\n    - Requirements baseline established\n    - Test strategy approved\n    - Development case tailored\n    - Behavioral spec coverage ≥80% of architecturally significant use cases\n    - Every behavioral spec has a completeness checklist satisfied\n    - Traceability: UC → behavioral spec IDs present in realizations\n\n    Generate validation report:\n    - List each use case and whether it has a behavioral spec (realization)\n    - Report behavioral spec coverage percentage\n    - Flag use cases without realizations as GAPS\n    - Overall status: PASS requires ≥80% coverage of architecturally significant UCs\n\n    Save to: .aiwg\u002Fgates\u002Fabm-validation-report.md\n    \"\"\"\n)\n\n# Architecture validation specialist\nTask(\n    subagent_type=\"architecture-designer\",\n    description=\"Deep validation of architecture readiness\",\n    prompt=\"\"\"\n    Validate architecture completeness:\n    - All views documented (logical, physical, deployment)\n    - Technology decisions justified\n    - Integration points defined\n    - Security architecture complete\n    - Performance architecture validated\n\n    Check architecture risks retired via POCs\n    Report: READY | GAPS | BLOCKED\n    Save to: .aiwg\u002Fgates\u002Fabm-architecture-review.md\n    \"\"\"\n)\n\n# Behavioral specification validation\nTask(\n    subagent_type=\"requirements-analyst\",\n    description=\"Validate behavioral specifications (Layer 3) completeness\",\n    prompt=\"\"\"\n    Validate Layer 3 behavioral specifications:\n\n    Check for use case realizations:\n    - .aiwg\u002Frequirements\u002Frealizations\u002FDES-UCR-*.md\n    - ≥80% coverage of architecturally significant use cases\n\n    Check for supporting specs:\n    - .aiwg\u002Farchitecture\u002Fstate-machines\u002FDES-SM-*.md (stateful entities)\n    - .aiwg\u002Farchitecture\u002Fdecision-tables\u002FDES-DT-*.md (branching logic)\n    - .aiwg\u002Farchitecture\u002Fmethod-contracts\u002FDES-MIC-*.md (method interfaces)\n    - .aiwg\u002Farchitecture\u002Factivity-diagrams\u002FDES-ACT-*.md (complex flows)\n\n    For each use case in .aiwg\u002Frequirements\u002F:\n    - List whether it has a corresponding realization\n    - Report coverage percentage\n    - Flag gaps\n\n    Report: READY | GAPS | BLOCKED\n    Include per-UC coverage table in report\n    Save to: .aiwg\u002Fgates\u002Fabm-behavioral-spec-review.md\n    \"\"\"\n)\n\n# Test readiness specialist\nTask(\n    subagent_type=\"test-architect\",\n    description=\"Validate test strategy readiness\",\n    prompt=\"\"\"\n    Review test planning:\n    - Master Test Plan completeness\n    - Test environment readiness\n    - Test data strategy defined\n    - Automation approach clear\n    - Coverage targets established\n\n    Report: READY | GAPS | BLOCKED\n    Save to: .aiwg\u002Fgates\u002Fabm-test-review.md\n    \"\"\"\n)\n```\n\n#### 2.3: Construction Gate (IOC) Validation\n\n**When**: User requests \"construction\", \"IOC\", or system detects Construction complete\n\n**Launch Validation Agents**:\n\n```\n# Primary Validator\nTask(\n    subagent_type=\"project-manager\",\n    description=\"Validate Initial Operational Capability\",\n    prompt=\"\"\"\n    Check for Construction completeness:\n    - All use cases implemented\n    - Test coverage targets met\n    - Performance within SLOs\n    - Security scans passing\n    - Documentation current\n\n    Check pseudo-code spec coverage (Layer 4):\n    - Every implemented method has a DES-PSC-*.md spec\n    - Spec coverage ≥80% of critical-path methods (configurable threshold)\n    - Error handling trees exist for critical paths\n    - Data structure specs match implementation\n\n    Validate IOC criteria:\n    - Unit test coverage ≥80%\n    - Integration tests 100% passing\n    - Acceptance tests validated\n    - No High\u002FCritical vulnerabilities\n    - Release notes complete\n    - Runbooks documented\n    - Traceability complete: UC → behavioral → pseudo-code → code → test\n\n    Generate comprehensive IOC report with:\n    - Behavioral spec → pseudo-code coverage matrix\n    - Spec-to-code traceability gaps\n    Save to: .aiwg\u002Fgates\u002Fioc-validation-report.md\n    \"\"\"\n)\n\n# Quality validation team (parallel)\nTask(\n    subagent_type=\"test-engineer\",\n    description=\"Validate test coverage and quality\",\n    prompt=\"\"\"\n    Analyze test metrics:\n    - Unit coverage percentage\n    - Integration test results\n    - Acceptance test status\n    - Performance test results\n    - Regression test status\n\n    Validate against Master Test Plan targets\n    Report: PASS | FAIL with specific gaps\n    Save to: .aiwg\u002Fgates\u002Fioc-test-validation.md\n    \"\"\"\n)\n\nTask(\n    subagent_type=\"security-gatekeeper\",\n    description=\"Security gate validation\",\n    prompt=\"\"\"\n    Review security posture:\n    - SAST\u002FDAST results\n    - Vulnerability scan status\n    - Dependency analysis\n    - Secret scanning results\n    - OWASP compliance\n\n    Validate: No High\u002FCritical without mitigation\n    Report: PASS | FAIL with remediation\n    Save to: .aiwg\u002Fgates\u002Fioc-security-validation.md\n    \"\"\"\n)\n\nTask(\n    subagent_type=\"reliability-engineer\",\n    description=\"Performance and reliability validation\",\n    prompt=\"\"\"\n    Validate SLOs:\n    - Response time (p50, p95, p99)\n    - Throughput capacity\n    - Error rates\n    - Resource utilization\n    - Scalability validation\n\n    Compare against targets in supplemental spec\n    Report: PASS | FAIL with metrics\n    Save to: .aiwg\u002Fgates\u002Fioc-reliability-validation.md\n    \"\"\"\n)\n```\n\n#### 2.4: Transition Gate (PR) Validation\n\n**When**: User requests \"transition\", \"PR\", \"orr\", or system detects Transition phase\n\n**Launch Validation Agents**:\n\n```\n# Primary Validator\nTask(\n    subagent_type=\"project-manager\",\n    description=\"Validate Product Release readiness\",\n    prompt=\"\"\"\n    Validate Transition\u002FRelease criteria:\n    - Operational Readiness Review complete\n    - Production deployment validated\n    - User training materials ready\n    - Support plan established\n    - Monitoring configured\n    - Rollback tested\n\n    Check for:\n    - User acceptance signoff\n    - Operations team readiness\n    - Support team training\n    - Business stakeholder approval\n\n    Generate Product Release validation report\n    Save to: .aiwg\u002Fgates\u002Fpr-validation-report.md\n    \"\"\"\n)\n\n# Operations readiness team\nTask(\n    subagent_type=\"devops-engineer\",\n    description=\"Validate operational readiness\",\n    prompt=\"\"\"\n    Review deployment readiness:\n    - Infrastructure provisioned\n    - Monitoring\u002Falerting configured\n    - Logging established\n    - Backup\u002Frecovery tested\n    - Rollback procedures validated\n    - Runbooks complete\n\n    Report: READY | GAPS | BLOCKED\n    Save to: .aiwg\u002Fgates\u002Fpr-operations-review.md\n    \"\"\"\n)\n\nTask(\n    subagent_type=\"support-engineer\",\n    description=\"Validate support readiness\",\n    prompt=\"\"\"\n    Review support preparedness:\n    - Support documentation complete\n    - Known issues documented\n    - Escalation paths defined\n    - Support team trained\n    - User guides available\n    - FAQ\u002Ftroubleshooting ready\n\n    Report: READY | GAPS | BLOCKED\n    Save to: .aiwg\u002Fgates\u002Fpr-support-review.md\n    \"\"\"\n)\n```\n\n### Step 3: Workflow Gate Validation\n\n**For non-phase gates** (security, reliability, test-coverage, etc.):\n\n```\n# Dispatch to appropriate specialist\nif gate == \"security\":\n    Task(\n        subagent_type=\"security-gatekeeper\",\n        description=\"Run security gate validation\",\n        prompt=\"\"\"\n        Comprehensive security validation:\n        - Run\u002Freview SAST results\n        - Run\u002Freview DAST results\n        - Check dependency vulnerabilities\n        - Scan for secrets\n        - Validate OWASP Top 10\n        - Review security architecture\n\n        Pass criteria: No High\u002FCritical without accepted risk\n        Generate detailed findings\n        Save to: .aiwg\u002Fgates\u002Fsecurity-gate-report.md\n        \"\"\"\n    )\n\nelif gate == \"reliability\":\n    Task(\n        subagent_type=\"reliability-engineer\",\n        description=\"Run reliability gate validation\",\n        prompt=\"\"\"\n        Validate performance and reliability:\n        - Load test results\n        - Stress test results\n        - SLI\u002FSLO compliance\n        - Resource utilization\n        - Scalability validation\n\n        Pass criteria: All SLOs met\n        Generate metrics report\n        Save to: .aiwg\u002Fgates\u002Freliability-gate-report.md\n        \"\"\"\n    )\n\nelif gate == \"test-coverage\":\n    Task(\n        subagent_type=\"test-engineer\",\n        description=\"Run test coverage validation\",\n        prompt=\"\"\"\n        Analyze test coverage:\n        - Unit test coverage\n        - Integration coverage\n        - Critical path coverage\n        - Error handling coverage\n        - Edge case coverage\n\n        Pass criteria: Meet Master Test Plan thresholds\n        Generate coverage report\n        Save to: .aiwg\u002Fgates\u002Ftest-coverage-report.md\n        \"\"\"\n    )\n\nelif gate == \"documentation\":\n    Task(\n        subagent_type=\"technical-writer\",\n        description=\"Run documentation gate validation\",\n        prompt=\"\"\"\n        Validate documentation completeness:\n        - User documentation\n        - API documentation\n        - Release notes\n        - Runbooks\n        - Architecture docs\n        - README files\n\n        Pass criteria: All user-facing docs complete\n        Generate completeness report\n        Save to: .aiwg\u002Fgates\u002Fdocumentation-gate-report.md\n        \"\"\"\n    )\n\nelif gate == \"traceability\":\n    Task(\n        subagent_type=\"requirements-analyst\",\n        description=\"Run traceability validation\",\n        prompt=\"\"\"\n        Validate bidirectional traceability:\n        - Requirements → Code\n        - Code → Tests\n        - Tests → Requirements\n        - Risks → Mitigations\n        - Decisions → Implementation\n\n        Pass criteria: 100% traceability\n        Generate traceability matrix\n        Save to: .aiwg\u002Fgates\u002Ftraceability-gate-report.md\n        \"\"\"\n    )\n\nelif gate == \"12-factor\":\n    # 12-Factor App methodology compliance gate (opt-in, cloud-native targets)\n    # Combines declarative lint (fast, deterministic) with architecture-designer\n    # review (semantic quality of SAD process architecture).\n    # Reference: .aiwg\u002Freports\u002F12-factor-gap-analysis.md, issue #821\n\n    # Layer 1: Declarative lint — structural checks (seconds)\n    Task(\n        subagent_type=\"project-manager\",\n        description=\"Run SDLC 12-factor lint ruleset\",\n        prompt=\"\"\"\n        Run the SDLC 12-factor lint ruleset against the project artifacts:\n\n        Command: aiwg lint .aiwg\u002F --ruleset sdlc --format json --ci --fail-on warn\n\n        The ruleset checks 10 structural conditions covering all 12 factors:\n        - dependency-manifest-present (II)\n        - sad-process-architecture (VI, VIII)\n        - sad-backing-services-locator (IV)\n        - sad-logging-architecture (XI)\n        - deployment-plan-deployments-table (I)\n        - deployment-plan-rolling-restart (IX)\n        - deployment-plan-admin-tasks (XII)\n        - env-parity-matrix (X)\n        - env-var-catalog (III)\n        - admin-processes-documented (XII)\n\n        Parse JSON output. Group diagnostics by factor.\n        Pass criteria: 0 errors; warnings documented with rationale if not addressed.\n        Save to: .aiwg\u002Fgates\u002F12-factor-lint-report.md\n        \"\"\"\n    )\n\n    # Layer 2: Architecture review — semantic quality of Process Architecture\n    Task(\n        subagent_type=\"architecture-designer\",\n        description=\"Validate Process Architecture section of SAD\",\n        prompt=\"\"\"\n        Deep review of the Software Architecture Document Section 9a (Process Architecture).\n        See .aiwg\u002Farchitecture\u002Fsoftware-architecture-doc.md.\n\n        Assess semantic quality (lint covers only presence, not correctness):\n\n        9a.1 Process Types — every process archetype listed with scaling axis, concurrency limits\n        9a.2 Process State Model — every state kind externalized to backing service, no in-process state\n        9a.3 Disposability — startup \u003C 10s target stated, SIGTERM handlers confirmed, crash recovery described\n        9a.4 Port Binding — self-contained services, no dependency on external web server (or ADR)\n        9a.5 Backing Services — every resource via env var, swap criteria realistic\n        9a.6 Logging Architecture — stdout\u002FJSON, no file handlers, correlation IDs propagated\n\n        For each: PASS | GAP | RISK | N\u002FA-with-ADR\n\n        Flag any section that lists state, disk writes, or log files that violate the corresponding rule:\n        - rules\u002Fstateless-processes.md\n        - rules\u002Fdisposable-processes.md\n        - rules\u002Flogs-as-event-streams.md\n        - rules\u002Fconfig-in-environment.md\n\n        Save to: .aiwg\u002Fgates\u002F12-factor-architecture-review.md\n        \"\"\"\n    )\n\n    # Layer 3: Deployment readiness — does the deployment plan reflect the process model?\n    Task(\n        subagent_type=\"deployment-manager\",\n        description=\"Validate deployment plan 12-factor compliance\",\n        prompt=\"\"\"\n        Review deployment artifacts for 12-factor deployment readiness.\n        See .aiwg\u002Fdeployment\u002Fdeployment-plan.md and deployment-environment.md.\n\n        Check:\n        - Deployments Table: every target environment enumerated? (Factor I)\n        - Rolling Restart Strategy: grace periods realistic? match SAD disposability SLA? (Factor IX)\n        - Admin Tasks: all migrations\u002Fbackfills reference admin-processes catalog? (Factor XII)\n        - Tech Stack Parity Matrix: dev\u002Fstaging\u002Fprod use same tech? parity violations ADR'd? (Factor X)\n        - Environment Variable Catalog: matches .env.example at project root? (Factor III)\n\n        Pass criteria: all 5 sections present and consistent with SAD Section 9a.\n        Save to: .aiwg\u002Fgates\u002F12-factor-deployment-review.md\n        \"\"\"\n    )\n```\n\n### Step 4: Synthesize Results\n\n**Purpose**: Combine all validation results into comprehensive gate report\n\n```\nTask(\n    subagent_type=\"project-manager\",\n    description=\"Synthesize gate validation results\",\n    prompt=\"\"\"\n    Read all validation reports from .aiwg\u002Fgates\u002F*.md\n\n    Create comprehensive Gate Validation Report:\n\n    # Gate Validation Report\n\n    **Gate**: {gate-name}\n    **Date**: {current-date}\n    **Overall Status**: PASS | FAIL | CONDITIONAL\n\n    ## Summary\n    - Pass Rate: X% (Y\u002FZ criteria)\n    - Decision: GO | NO-GO | CONDITIONAL GO\n\n    ## Validation Results\n\n    ### Required Artifacts\n    - List each with status (PRESENT\u002FMISSING\u002FINCOMPLETE)\n\n    ### Quality Gates\n    - List each gate with PASS\u002FFAIL status\n\n    ### Failed Criteria\n    - Detailed list with reasons\n\n    ### Signoff Status\n    - List required signoffs with status\n\n    ## Remediation Plan\n    - Prioritized list of actions to pass gate\n    - Owner assignments\n    - Timeline estimates\n\n    ## Recommendations\n    - Process improvements\n    - Risk mitigations\n    - Next steps\n\n    ## Decision\n    - Clear GO\u002FNO-GO\u002FCONDITIONAL recommendation\n    - Rationale based on findings\n    - Conditions if CONDITIONAL\n\n    Save to: .aiwg\u002Freports\u002Fgate-validation-{gate}-{date}.md\n    \"\"\"\n)\n```\n\n### Step 5: Present Results to User\n\n**Your Direct Communication**:\n\n```\n─────────────────────────────────────────────\n{Gate Name} Validation Complete\n─────────────────────────────────────────────\n\n**Overall Status**: {PASS | FAIL | CONDITIONAL}\n**Decision**: {GO | NO-GO | CONDITIONAL GO}\n\n**Validation Summary**:\n✓ Required Artifacts: {X\u002FY} complete\n✓ Quality Gates: {X\u002FY} passed\n✓ Signoffs: {X\u002FY} obtained\n\n{If FAIL or CONDITIONAL:}\n**Critical Issues**:\n- {Issue 1 with impact}\n- {Issue 2 with impact}\n\n**Remediation Required**:\n1. {Action} - Owner: {role} - Est: {time}\n2. {Action} - Owner: {role} - Est: {time}\n\n**Reports Generated**:\n- Full Report: .aiwg\u002Freports\u002Fgate-validation-{gate}-{date}.md\n- Specialist Reviews: .aiwg\u002Fgates\u002F*.md\n\n**Next Steps**:\n{If PASS}: Proceed to {next-phase}\n{If FAIL}: Complete remediation, then re-validate\n{If CONDITIONAL}: Address conditions within {timeframe}\n\n─────────────────────────────────────────────\n```\n\n## Special Gate Orchestration\n\n### \"All\" Gates\n\nWhen user requests \"all\":\n1. Detect current phase from artifacts\n2. Run all applicable gates for that phase\n3. Generate consolidated report\n\n### \"Pre-Deploy\" Gates\n\nWhen user requests \"pre-deploy\":\n1. Run security, reliability, test-coverage, and documentation gates in parallel\n2. All must pass for deployment approval\n3. Generate deployment readiness report\n\n## Quality Assurance\n\nBefore completing orchestration:\n- [ ] All requested gates validated\n- [ ] Results from all agents collected\n- [ ] Synthesis report generated\n- [ ] Clear pass\u002Ffail decision provided\n- [ ] Remediation actions specific and actionable\n\n## User Communication\n\n**At start**:\n```\nUnderstood. I'll orchestrate gate validation for {gate-name}.\n\nThis will involve:\n- Checking required artifacts\n- Running quality validations\n- Collecting specialist reviews\n- Generating comprehensive report\n\nExpected duration: 5-10 minutes.\n\nStarting validation...\n```\n\n**During execution**:\n```\n✓ = Complete\n⏳ = In progress\n❌ = Failed check\n⚠️ = Issue found\n```\n\n**At end**: Present synthesized results (see Step 5)\n\n## Error Handling\n\n**Unknown Gate**:\n```\n❌ Unknown gate: {input}\n\nSupported gates:\n- Phase gates: inception, elaboration, construction, transition\n- Workflow gates: security, reliability, test-coverage, documentation, traceability, 12-factor\n- Special: all, pre-deploy, orr\n\nPlease specify a valid gate.\n```\n\n**Missing Critical Artifacts**:\n```\n⚠️ Cannot validate - critical artifacts missing:\n- {artifact-1}: Expected at {path}\n- {artifact-2}: Expected at {path}\n\nThese artifacts are required for {gate} validation.\nCreate them using appropriate templates or commands.\n```\n\n**Conflicting Results**:\n```\n⚠️ Validation conflict detected:\n- {Agent-1}: PASS\n- {Agent-2}: FAIL\n\nReviewing details to determine overall status...\n[Then provide reasoned decision based on criticality]\n```\n\n## Success Criteria\n\nThis orchestration succeeds when:\n- [ ] Appropriate gate criteria identified\n- [ ] All validations completed by specialists\n- [ ] Results synthesized into clear report\n- [ ] Pass\u002Ffail decision justified with evidence\n- [ ] Remediation plan specific and actionable\n- [ ] User receives clear guidance on next steps\n\n## References\n\n**Templates** (via $AIWG_ROOT):\n- Gate criteria: `flows\u002Fgate-criteria-by-phase.md`\n- Handoff checklists: `flows\u002Fhandoff-checklist-template.md`\n\n**Multi-Agent Pattern**:\n- `docs\u002Fmulti-agent-documentation-pattern.md`\n\n**Orchestrator Architecture**:\n- `docs\u002Forchestrator-architecture.md`","> **Declarative Flow (#1539):** This flow's orchestration is now also expressed as a\n> declarative YAML Flow at `flows\u002Fflow-gate-check.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 Gate Check Orchestration\n\n**You are the Core Orchestrator** for SDLC phase gate validation.\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- \"Can we transition to {phase}?\"\n- \"Are we ready for {phase}?\"\n- \"Validate gate criteria\"\n- \"Check if we can proceed\"\n- \"Gate validation for {phase}\"\n- \"Check {phase} readiness\"\n- \"Is the {milestone} complete?\"\n- \"Run gate check for {phase}\"\n- \"Validate our readiness to move forward\"\n\nYou recognize these as requests for this orchestration flow.\n\n## Parameter Handling\n\n### Phase\u002FGate Identification\n\n**Supported Gates**:\n\n**Phase Milestones**:\n- `inception` \u002F `LOM` - Lifecycle Objective Milestone\n- `elaboration` \u002F `ABM` - Architecture Baseline Milestone\n- `construction` \u002F `IOC` - Initial Operational Capability\n- `transition` \u002F `PR` - Product Release\n\n**Workflow Gates**:\n- `discovery` - Discovery Track Definition of Ready\n- `delivery` - Delivery Track Definition of Done\n- `security` - Security validation\n- `reliability` - Performance and SLO compliance\n- `test-coverage` - Test coverage thresholds\n- `documentation` - Documentation completeness\n- `traceability` - Requirements → code → tests\n- `12-factor` - 12-factor app methodology compliance (opt-in, cloud-native targets)\n\n**Special Gates**:\n- `all` - Run all applicable gates\n- `pre-deploy` - Pre-deployment readiness\n- `orr` - Operational Readiness Review\n\n### --guidance Parameter\n\n**Purpose**: User provides upfront direction to tailor validation priorities\n\n**Examples**:\n```\n--guidance \"Focus on security compliance, HIPAA critical\"\n--guidance \"Time-constrained, prioritize minimum viable gates\"\n--guidance \"Enterprise deployment, need full compliance validation\"\n```\n\n**How to Apply**:\n- Parse guidance for keywords: security, compliance, timeline, quality\n- Adjust validation depth (comprehensive vs. essential)\n- Influence agent assignments (add specialized validators)\n- Modify reporting detail level\n\n### --interactive Parameter\n\n**Purpose**: You ask 3-5 strategic questions to understand context\n\n**Questions to Ask** (if --interactive):\n\n```\nI'll ask strategic questions to tailor the gate validation:\n\nQ1: What's your primary concern for this gate check?\n    (e.g., compliance readiness, technical quality, team preparedness)\n\nQ2: Are there any known issues or gaps you're concerned about?\n    (Help me focus validation on problem areas)\n\nQ3: What's your timeline for passing this gate?\n    (Influences whether to report quick-fixes vs. comprehensive remediation)\n\nQ4: Who needs to sign off on this gate?\n    (Helps identify which specialized reviewers to involve)\n\nQ5: What happens if the gate doesn't pass?\n    (Helps determine how strict validation should be)\n```\n\n## Multi-Agent Orchestration Workflow\n\n### Step 1: Determine Gate Context\n\n**Purpose**: Identify which gate to validate and current project state\n\n**Your Actions**:\n\n1. **Parse Gate Parameter**:\n   ```\n   Map user input to gate type:\n   - \"inception\" | \"LOM\" → Lifecycle Objective Milestone\n   - \"elaboration\" | \"ABM\" → Architecture Baseline Milestone\n   - \"construction\" | \"IOC\" → Initial Operational Capability\n   - \"transition\" | \"PR\" → Product Release\n   - Others → Workflow or special gates\n   ```\n\n2. **Scan Project State**:\n   ```\n   Use Glob to check for phase indicators:\n   - .aiwg\u002Fintake\u002F* → Likely in Inception\n   - .aiwg\u002Farchitecture\u002Fsoftware-architecture-doc.md → Likely post-Elaboration\n   - .aiwg\u002Ftesting\u002Ftest-results\u002F* → Likely in Construction\n   - .aiwg\u002Fdeployment\u002Fproduction-deploy.md → Likely in Transition\n   ```\n\n**Communicate Progress**:\n```\n✓ Gate identified: {gate-name}\n⏳ Scanning project state...\n✓ Current phase detected: {phase}\n```\n\n### Step 2: Phase Gate Validation (LOM\u002FABM\u002FIOC\u002FPR)\n\n#### 2.1: Inception Gate (LOM) Validation\n\n**When**: User requests \"inception\", \"LOM\", or system detects Inception phase\n\n**Launch Validation Agents**:\n\n```\n# Primary Validator\nTask(\n    subagent_type=\"project-manager\",\n    description=\"Validate Lifecycle Objective Milestone criteria\",\n    prompt=\"\"\"\n    Read gate criteria from: $AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fflows\u002Fgate-criteria-by-phase.md\n\n    Check for required Inception artifacts:\n    - .aiwg\u002Fintake\u002Fproject-intake.md (COMPLETE)\n    - .aiwg\u002Frequirements\u002Fvision-*.md (APPROVED)\n    - .aiwg\u002Fplanning\u002Fbusiness-case-*.md (APPROVED)\n    - .aiwg\u002Frisks\u002Frisk-list.md (BASELINED)\n    - .aiwg\u002Fsecurity\u002Fdata-classification.md (COMPLETE)\n\n    Validate LOM criteria:\n    - Vision document APPROVED (stakeholder signoff ≥75%)\n    - Business case APPROVED (funding secured)\n    - Risk list BASELINED (5-10 risks, top 3 have mitigation)\n    - Data classification COMPLETE\n    - Initial architecture documented\n    - Executive Sponsor approval obtained\n\n    Generate validation report:\n    - Status: PASS | FAIL | CONDITIONAL\n    - Missing artifacts list\n    - Failed criteria with reasons\n    - Signoff status\n    - Remediation actions\n\n    Save to: .aiwg\u002Fgates\u002Flom-validation-report.md\n    \"\"\"\n)\n\n# Parallel Specialized Reviewers\nTask(\n    subagent_type=\"business-analyst\",\n    description=\"Validate business readiness for LOM\",\n    prompt=\"\"\"\n    Review business artifacts:\n    - Business case viability\n    - Stakeholder alignment\n    - Funding adequacy\n    - Vision clarity\n\n    Report business readiness: READY | GAPS | BLOCKED\n    Save to: .aiwg\u002Fgates\u002Flom-business-review.md\n    \"\"\"\n)\n\nTask(\n    subagent_type=\"security-architect\",\n    description=\"Validate security readiness for LOM\",\n    prompt=\"\"\"\n    Review security artifacts:\n    - Data classification completeness\n    - Initial threat assessment\n    - Compliance requirements identified\n    - Security risks documented\n\n    Report security readiness: READY | GAPS | BLOCKED\n    Save to: .aiwg\u002Fgates\u002Flom-security-review.md\n    \"\"\"\n)\n```\n\n#### 2.2: Elaboration Gate (ABM) Validation\n\n**When**: User requests \"elaboration\", \"ABM\", or system detects Elaboration phase\n\n**Launch Validation Agents**:\n\n```\n# Primary Validator\nTask(\n    subagent_type=\"project-manager\",\n    description=\"Validate Architecture Baseline Milestone criteria\",\n    prompt=\"\"\"\n    Read gate criteria from: $AIWG_ROOT\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsdlc-complete\u002Fflows\u002Fgate-criteria-by-phase.md\n\n    Check for required Elaboration artifacts:\n    - .aiwg\u002Farchitecture\u002Fsoftware-architecture-doc.md (BASELINED)\n    - .aiwg\u002Farchitecture\u002Fadr\u002F*.md (3-5 ADRs)\n    - .aiwg\u002Frequirements\u002Fsupplemental-specification.md (COMPLETE)\n    - .aiwg\u002Ftesting\u002Fmaster-test-plan.md (APPROVED)\n    - .aiwg\u002Frisks\u002Frisk-retirement-report.md\n\n    Check for Layer 3 behavioral specifications:\n    - .aiwg\u002Frequirements\u002Frealizations\u002FDES-UCR-*.md (use case realizations)\n    - .aiwg\u002Farchitecture\u002Fstate-machines\u002FDES-SM-*.md (state machine specs)\n    - .aiwg\u002Farchitecture\u002Fdecision-tables\u002FDES-DT-*.md (decision tables)\n    - .aiwg\u002Farchitecture\u002Fmethod-contracts\u002FDES-MIC-*.md (method interface contracts)\n    - .aiwg\u002Farchitecture\u002Factivity-diagrams\u002FDES-ACT-*.md (activity diagrams)\n\n    Validate ABM criteria:\n    - Architecture BASELINED and peer-reviewed\n    - ADRs documented (3-5 major decisions)\n    - Risks ≥70% retired or mitigated\n    - Requirements baseline established\n    - Test strategy approved\n    - Development case tailored\n    - Behavioral spec coverage ≥80% of architecturally significant use cases\n    - Every behavioral spec has a completeness checklist satisfied\n    - Traceability: UC → behavioral spec IDs present in realizations\n\n    Generate validation report:\n    - List each use case and whether it has a behavioral spec (realization)\n    - Report behavioral spec coverage percentage\n    - Flag use cases without realizations as GAPS\n    - Overall status: PASS requires ≥80% coverage of architecturally significant UCs\n\n    Save to: .aiwg\u002Fgates\u002Fabm-validation-report.md\n    \"\"\"\n)\n\n# Architecture validation specialist\nTask(\n    subagent_type=\"architecture-designer\",\n    description=\"Deep validation of architecture readiness\",\n    prompt=\"\"\"\n    Validate architecture completeness:\n    - All views documented (logical, physical, deployment)\n    - Technology decisions justified\n    - Integration points defined\n    - Security architecture complete\n    - Performance architecture validated\n\n    Check architecture risks retired via POCs\n    Report: READY | GAPS | BLOCKED\n    Save to: .aiwg\u002Fgates\u002Fabm-architecture-review.md\n    \"\"\"\n)\n\n# Behavioral specification validation\nTask(\n    subagent_type=\"requirements-analyst\",\n    description=\"Validate behavioral specifications (Layer 3) completeness\",\n    prompt=\"\"\"\n    Validate Layer 3 behavioral specifications:\n\n    Check for use case realizations:\n    - .aiwg\u002Frequirements\u002Frealizations\u002FDES-UCR-*.md\n    - ≥80% coverage of architecturally significant use cases\n\n    Check for supporting specs:\n    - .aiwg\u002Farchitecture\u002Fstate-machines\u002FDES-SM-*.md (stateful entities)\n    - .aiwg\u002Farchitecture\u002Fdecision-tables\u002FDES-DT-*.md (branching logic)\n    - .aiwg\u002Farchitecture\u002Fmethod-contracts\u002FDES-MIC-*.md (method interfaces)\n    - .aiwg\u002Farchitecture\u002Factivity-diagrams\u002FDES-ACT-*.md (complex flows)\n\n    For each use case in .aiwg\u002Frequirements\u002F:\n    - List whether it has a corresponding realization\n    - Report coverage percentage\n    - Flag gaps\n\n    Report: READY | GAPS | BLOCKED\n    Include per-UC coverage table in report\n    Save to: .aiwg\u002Fgates\u002Fabm-behavioral-spec-review.md\n    \"\"\"\n)\n\n# Test readiness specialist\nTask(\n    subagent_type=\"test-architect\",\n    description=\"Validate test strategy readiness\",\n    prompt=\"\"\"\n    Review test planning:\n    - Master Test Plan completeness\n    - Test environment readiness\n    - Test data strategy defined\n    - Automation approach clear\n    - Coverage targets established\n\n    Report: READY | GAPS | BLOCKED\n    Save to: .aiwg\u002Fgates\u002Fabm-test-review.md\n    \"\"\"\n)\n```\n\n#### 2.3: Construction Gate (IOC) Validation\n\n**When**: User requests \"construction\", \"IOC\", or system detects Construction complete\n\n**Launch Validation Agents**:\n\n```\n# Primary Validator\nTask(\n    subagent_type=\"project-manager\",\n    description=\"Validate Initial Operational Capability\",\n    prompt=\"\"\"\n    Check for Construction completeness:\n    - All use cases implemented\n    - Test coverage targets met\n    - Performance within SLOs\n    - Security scans passing\n    - Documentation current\n\n    Check pseudo-code spec coverage (Layer 4):\n    - Every implemented method has a DES-PSC-*.md spec\n    - Spec coverage ≥80% of critical-path methods (configurable threshold)\n    - Error handling trees exist for critical paths\n    - Data structure specs match implementation\n\n    Validate IOC criteria:\n    - Unit test coverage ≥80%\n    - Integration tests 100% passing\n    - Acceptance tests validated\n    - No High\u002FCritical vulnerabilities\n    - Release notes complete\n    - Runbooks documented\n    - Traceability complete: UC → behavioral → pseudo-code → code → test\n\n    Generate comprehensive IOC report with:\n    - Behavioral spec → pseudo-code coverage matrix\n    - Spec-to-code traceability gaps\n    Save to: .aiwg\u002Fgates\u002Fioc-validation-report.md\n    \"\"\"\n)\n\n# Quality validation team (parallel)\nTask(\n    subagent_type=\"test-engineer\",\n    description=\"Validate test coverage and quality\",\n    prompt=\"\"\"\n    Analyze test metrics:\n    - Unit coverage percentage\n    - Integration test results\n    - Acceptance test status\n    - Performance test results\n    - Regression test status\n\n    Validate against Master Test Plan targets\n    Report: PASS | FAIL with specific gaps\n    Save to: .aiwg\u002Fgates\u002Fioc-test-validation.md\n    \"\"\"\n)\n\nTask(\n    subagent_type=\"security-gatekeeper\",\n    description=\"Security gate validation\",\n    prompt=\"\"\"\n    Review security posture:\n    - SAST\u002FDAST results\n    - Vulnerability scan status\n    - Dependency analysis\n    - Secret scanning results\n    - OWASP compliance\n\n    Validate: No High\u002FCritical without mitigation\n    Report: PASS | FAIL with remediation\n    Save to: .aiwg\u002Fgates\u002Fioc-security-validation.md\n    \"\"\"\n)\n\nTask(\n    subagent_type=\"reliability-engineer\",\n    description=\"Performance and reliability validation\",\n    prompt=\"\"\"\n    Validate SLOs:\n    - Response time (p50, p95, p99)\n    - Throughput capacity\n    - Error rates\n    - Resource utilization\n    - Scalability validation\n\n    Compare against targets in supplemental spec\n    Report: PASS | FAIL with metrics\n    Save to: .aiwg\u002Fgates\u002Fioc-reliability-validation.md\n    \"\"\"\n)\n```\n\n#### 2.4: Transition Gate (PR) Validation\n\n**When**: User requests \"transition\", \"PR\", \"orr\", or system detects Transition phase\n\n**Launch Validation Agents**:\n\n```\n# Primary Validator\nTask(\n    subagent_type=\"project-manager\",\n    description=\"Validate Product Release readiness\",\n    prompt=\"\"\"\n    Validate Transition\u002FRelease criteria:\n    - Operational Readiness Review complete\n    - Production deployment validated\n    - User training materials ready\n    - Support plan established\n    - Monitoring configured\n    - Rollback tested\n\n    Check for:\n    - User acceptance signoff\n    - Operations team readiness\n    - Support team training\n    - Business stakeholder approval\n\n    Generate Product Release validation report\n    Save to: .aiwg\u002Fgates\u002Fpr-validation-report.md\n    \"\"\"\n)\n\n# Operations readiness team\nTask(\n    subagent_type=\"devops-engineer\",\n    description=\"Validate operational readiness\",\n    prompt=\"\"\"\n    Review deployment readiness:\n    - Infrastructure provisioned\n    - Monitoring\u002Falerting configured\n    - Logging established\n    - Backup\u002Frecovery tested\n    - Rollback procedures validated\n    - Runbooks complete\n\n    Report: READY | GAPS | BLOCKED\n    Save to: .aiwg\u002Fgates\u002Fpr-operations-review.md\n    \"\"\"\n)\n\nTask(\n    subagent_type=\"support-engineer\",\n    description=\"Validate support readiness\",\n    prompt=\"\"\"\n    Review support preparedness:\n    - Support documentation complete\n    - Known issues documented\n    - Escalation paths defined\n    - Support team trained\n    - User guides available\n    - FAQ\u002Ftroubleshooting ready\n\n    Report: READY | GAPS | BLOCKED\n    Save to: .aiwg\u002Fgates\u002Fpr-support-review.md\n    \"\"\"\n)\n```\n\n### Step 3: Workflow Gate Validation\n\n**For non-phase gates** (security, reliability, test-coverage, etc.):\n\n```\n# Dispatch to appropriate specialist\nif gate == \"security\":\n    Task(\n        subagent_type=\"security-gatekeeper\",\n        description=\"Run security gate validation\",\n        prompt=\"\"\"\n        Comprehensive security validation:\n        - Run\u002Freview SAST results\n        - Run\u002Freview DAST results\n        - Check dependency vulnerabilities\n        - Scan for secrets\n        - Validate OWASP Top 10\n        - Review security architecture\n\n        Pass criteria: No High\u002FCritical without accepted risk\n        Generate detailed findings\n        Save to: .aiwg\u002Fgates\u002Fsecurity-gate-report.md\n        \"\"\"\n    )\n\nelif gate == \"reliability\":\n    Task(\n        subagent_type=\"reliability-engineer\",\n        description=\"Run reliability gate validation\",\n        prompt=\"\"\"\n        Validate performance and reliability:\n        - Load test results\n        - Stress test results\n        - SLI\u002FSLO compliance\n        - Resource utilization\n        - Scalability validation\n\n        Pass criteria: All SLOs met\n        Generate metrics report\n        Save to: .aiwg\u002Fgates\u002Freliability-gate-report.md\n        \"\"\"\n    )\n\nelif gate == \"test-coverage\":\n    Task(\n        subagent_type=\"test-engineer\",\n        description=\"Run test coverage validation\",\n        prompt=\"\"\"\n        Analyze test coverage:\n        - Unit test coverage\n        - Integration coverage\n        - Critical path coverage\n        - Error handling coverage\n        - Edge case coverage\n\n        Pass criteria: Meet Master Test Plan thresholds\n        Generate coverage report\n        Save to: .aiwg\u002Fgates\u002Ftest-coverage-report.md\n        \"\"\"\n    )\n\nelif gate == \"documentation\":\n    Task(\n        subagent_type=\"technical-writer\",\n        description=\"Run documentation gate validation\",\n        prompt=\"\"\"\n        Validate documentation completeness:\n        - User documentation\n        - API documentation\n        - Release notes\n        - Runbooks\n        - Architecture docs\n        - README files\n\n        Pass criteria: All user-facing docs complete\n        Generate completeness report\n        Save to: .aiwg\u002Fgates\u002Fdocumentation-gate-report.md\n        \"\"\"\n    )\n\nelif gate == \"traceability\":\n    Task(\n        subagent_type=\"requirements-analyst\",\n        description=\"Run traceability validation\",\n        prompt=\"\"\"\n        Validate bidirectional traceability:\n        - Requirements → Code\n        - Code → Tests\n        - Tests → Requirements\n        - Risks → Mitigations\n        - Decisions → Implementation\n\n        Pass criteria: 100% traceability\n        Generate traceability matrix\n        Save to: .aiwg\u002Fgates\u002Ftraceability-gate-report.md\n        \"\"\"\n    )\n\nelif gate == \"12-factor\":\n    # 12-Factor App methodology compliance gate (opt-in, cloud-native targets)\n    # Combines declarative lint (fast, deterministic) with architecture-designer\n    # review (semantic quality of SAD process architecture).\n    # Reference: .aiwg\u002Freports\u002F12-factor-gap-analysis.md, issue #821\n\n    # Layer 1: Declarative lint — structural checks (seconds)\n    Task(\n        subagent_type=\"project-manager\",\n        description=\"Run SDLC 12-factor lint ruleset\",\n        prompt=\"\"\"\n        Run the SDLC 12-factor lint ruleset against the project artifacts:\n\n        Command: aiwg lint .aiwg\u002F --ruleset sdlc --format json --ci --fail-on warn\n\n        The ruleset checks 10 structural conditions covering all 12 factors:\n        - dependency-manifest-present (II)\n        - sad-process-architecture (VI, VIII)\n        - sad-backing-services-locator (IV)\n        - sad-logging-architecture (XI)\n        - deployment-plan-deployments-table (I)\n        - deployment-plan-rolling-restart (IX)\n        - deployment-plan-admin-tasks (XII)\n        - env-parity-matrix (X)\n        - env-var-catalog (III)\n        - admin-processes-documented (XII)\n\n        Parse JSON output. Group diagnostics by factor.\n        Pass criteria: 0 errors; warnings documented with rationale if not addressed.\n        Save to: .aiwg\u002Fgates\u002F12-factor-lint-report.md\n        \"\"\"\n    )\n\n    # Layer 2: Architecture review — semantic quality of Process Architecture\n    Task(\n        subagent_type=\"architecture-designer\",\n        description=\"Validate Process Architecture section of SAD\",\n        prompt=\"\"\"\n        Deep review of the Software Architecture Document Section 9a (Process Architecture).\n        See .aiwg\u002Farchitecture\u002Fsoftware-architecture-doc.md.\n\n        Assess semantic quality (lint covers only presence, not correctness):\n\n        9a.1 Process Types — every process archetype listed with scaling axis, concurrency limits\n        9a.2 Process State Model — every state kind externalized to backing service, no in-process state\n        9a.3 Disposability — startup \u003C 10s target stated, SIGTERM handlers confirmed, crash recovery described\n        9a.4 Port Binding — self-contained services, no dependency on external web server (or ADR)\n        9a.5 Backing Services — every resource via env var, swap criteria realistic\n        9a.6 Logging Architecture — stdout\u002FJSON, no file handlers, correlation IDs propagated\n\n        For each: PASS | GAP | RISK | N\u002FA-with-ADR\n\n        Flag any section that lists state, disk writes, or log files that violate the corresponding rule:\n        - rules\u002Fstateless-processes.md\n        - rules\u002Fdisposable-processes.md\n        - rules\u002Flogs-as-event-streams.md\n        - rules\u002Fconfig-in-environment.md\n\n        Save to: .aiwg\u002Fgates\u002F12-factor-architecture-review.md\n        \"\"\"\n    )\n\n    # Layer 3: Deployment readiness — does the deployment plan reflect the process model?\n    Task(\n        subagent_type=\"deployment-manager\",\n        description=\"Validate deployment plan 12-factor compliance\",\n        prompt=\"\"\"\n        Review deployment artifacts for 12-factor deployment readiness.\n        See .aiwg\u002Fdeployment\u002Fdeployment-plan.md and deployment-environment.md.\n\n        Check:\n        - Deployments Table: every target environment enumerated? (Factor I)\n        - Rolling Restart Strategy: grace periods realistic? match SAD disposability SLA? (Factor IX)\n        - Admin Tasks: all migrations\u002Fbackfills reference admin-processes catalog? (Factor XII)\n        - Tech Stack Parity Matrix: dev\u002Fstaging\u002Fprod use same tech? parity violations ADR'd? (Factor X)\n        - Environment Variable Catalog: matches .env.example at project root? (Factor III)\n\n        Pass criteria: all 5 sections present and consistent with SAD Section 9a.\n        Save to: .aiwg\u002Fgates\u002F12-factor-deployment-review.md\n        \"\"\"\n    )\n```\n\n### Step 4: Synthesize Results\n\n**Purpose**: Combine all validation results into comprehensive gate report\n\n```\nTask(\n    subagent_type=\"project-manager\",\n    description=\"Synthesize gate validation results\",\n    prompt=\"\"\"\n    Read all validation reports from .aiwg\u002Fgates\u002F*.md\n\n    Create comprehensive Gate Validation Report:\n\n    # Gate Validation Report\n\n    **Gate**: {gate-name}\n    **Date**: {current-date}\n    **Overall Status**: PASS | FAIL | CONDITIONAL\n\n    ## Summary\n    - Pass Rate: X% (Y\u002FZ criteria)\n    - Decision: GO | NO-GO | CONDITIONAL GO\n\n    ## Validation Results\n\n    ### Required Artifacts\n    - List each with status (PRESENT\u002FMISSING\u002FINCOMPLETE)\n\n    ### Quality Gates\n    - List each gate with PASS\u002FFAIL status\n\n    ### Failed Criteria\n    - Detailed list with reasons\n\n    ### Signoff Status\n    - List required signoffs with status\n\n    ## Remediation Plan\n    - Prioritized list of actions to pass gate\n    - Owner assignments\n    - Timeline estimates\n\n    ## Recommendations\n    - Process improvements\n    - Risk mitigations\n    - Next steps\n\n    ## Decision\n    - Clear GO\u002FNO-GO\u002FCONDITIONAL recommendation\n    - Rationale based on findings\n    - Conditions if CONDITIONAL\n\n    Save to: .aiwg\u002Freports\u002Fgate-validation-{gate}-{date}.md\n    \"\"\"\n)\n```\n\n### Step 5: Present Results to User\n\n**Your Direct Communication**:\n\n```\n─────────────────────────────────────────────\n{Gate Name} Validation Complete\n─────────────────────────────────────────────\n\n**Overall Status**: {PASS | FAIL | CONDITIONAL}\n**Decision**: {GO | NO-GO | CONDITIONAL GO}\n\n**Validation Summary**:\n✓ Required Artifacts: {X\u002FY} complete\n✓ Quality Gates: {X\u002FY} passed\n✓ Signoffs: {X\u002FY} obtained\n\n{If FAIL or CONDITIONAL:}\n**Critical Issues**:\n- {Issue 1 with impact}\n- {Issue 2 with impact}\n\n**Remediation Required**:\n1. {Action} - Owner: {role} - Est: {time}\n2. {Action} - Owner: {role} - Est: {time}\n\n**Reports Generated**:\n- Full Report: .aiwg\u002Freports\u002Fgate-validation-{gate}-{date}.md\n- Specialist Reviews: .aiwg\u002Fgates\u002F*.md\n\n**Next Steps**:\n{If PASS}: Proceed to {next-phase}\n{If FAIL}: Complete remediation, then re-validate\n{If CONDITIONAL}: Address conditions within {timeframe}\n\n─────────────────────────────────────────────\n```\n\n## Special Gate Orchestration\n\n### \"All\" Gates\n\nWhen user requests \"all\":\n1. Detect current phase from artifacts\n2. Run all applicable gates for that phase\n3. Generate consolidated report\n\n### \"Pre-Deploy\" Gates\n\nWhen user requests \"pre-deploy\":\n1. Run security, reliability, test-coverage, and documentation gates in parallel\n2. All must pass for deployment approval\n3. Generate deployment readiness report\n\n## Quality Assurance\n\nBefore completing orchestration:\n- [ ] All requested gates validated\n- [ ] Results from all agents collected\n- [ ] Synthesis report generated\n- [ ] Clear pass\u002Ffail decision provided\n- [ ] Remediation actions specific and actionable\n\n## User Communication\n\n**At start**:\n```\nUnderstood. I'll orchestrate gate validation for {gate-name}.\n\nThis will involve:\n- Checking required artifacts\n- Running quality validations\n- Collecting specialist reviews\n- Generating comprehensive report\n\nExpected duration: 5-10 minutes.\n\nStarting validation...\n```\n\n**During execution**:\n```\n✓ = Complete\n⏳ = In progress\n❌ = Failed check\n⚠️ = Issue found\n```\n\n**At end**: Present synthesized results (see Step 5)\n\n## Error Handling\n\n**Unknown Gate**:\n```\n❌ Unknown gate: {input}\n\nSupported gates:\n- Phase gates: inception, elaboration, construction, transition\n- Workflow gates: security, reliability, test-coverage, documentation, traceability, 12-factor\n- Special: all, pre-deploy, orr\n\nPlease specify a valid gate.\n```\n\n**Missing Critical Artifacts**:\n```\n⚠️ Cannot validate - critical artifacts missing:\n- {artifact-1}: Expected at {path}\n- {artifact-2}: Expected at {path}\n\nThese artifacts are required for {gate} validation.\nCreate them using appropriate templates or commands.\n```\n\n**Conflicting Results**:\n```\n⚠️ Validation conflict detected:\n- {Agent-1}: PASS\n- {Agent-2}: FAIL\n\nReviewing details to determine overall status...\n[Then provide reasoned decision based on criticality]\n```\n\n## Success Criteria\n\nThis orchestration succeeds when:\n- [ ] Appropriate gate criteria identified\n- [ ] All validations completed by specialists\n- [ ] Results synthesized into clear report\n- [ ] Pass\u002Ffail decision justified with evidence\n- [ ] Remediation plan specific and actionable\n- [ ] User receives clear guidance on next steps\n\n## References\n\n**Templates** (via $AIWG_ROOT):\n- Gate criteria: `flows\u002Fgate-criteria-by-phase.md`\n- Handoff checklists: `flows\u002Fhandoff-checklist-template.md`\n\n**Multi-Agent Pattern**:\n- `docs\u002Fmulti-agent-documentation-pattern.md`\n\n**Orchestrator Architecture**:\n- `docs\u002Forchestrator-architecture.md`",{"name":5,"namespace":52,"platforms":53,"commandHint":55,"description":7},"aiwg",[54],"all",{"model":33,"category":56,"modelRole":39,"modelTier":57,"allowedTools":58,"argumentHint":59,"orchestration":60},"sdlc-orchestration","standard","Task, Read, Write, Glob, TodoWrite","\u003Cphase-or-gate-name> [project-directory] [--guidance \"text\"] [--interactive]",true,"main","6754967c344ccb087a8de06972f55a41067b291b","agentic\u002Fcode\u002Fplugins\u002Fcodex-sdlc\u002Fskills\u002Fflow-gate-check",36,"https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg","https:\u002F\u002Faiwg.io","https:\u002F\u002Fgithub.com\u002Fjmagly","https:\u002F\u002Fintegrolabs.io","ml\u002Fai, industrial automation, safety\u002Fsecurity, ssi\r\n\r\nmagly.net\r\nintegrolabs.io\r\naiwg.io\r\nfortemi.com\r\npagenary.com\r\nbytecask.com","2026-11-12 00:33:10",{"source":8,"skillName":5,"commands":72,"prompt":82,"zipAvailable":60},[73,76,79],{"tool":74,"command":75},"npx","npx skills add jmagly\u002Faiwg --skill flow-gate-check",{"tool":77,"command":78},"bunx","bunx skills add jmagly\u002Faiwg --skill flow-gate-check",{"tool":80,"command":81},"pnpm","pnpm dlx skills add jmagly\u002Faiwg --skill flow-gate-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fplugins\u002Fcodex-sdlc\u002Fskills\u002Fflow-gate-check\u002FSKILL.md",[],[85,112,135,141,148,161],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":92,"publishedAt":47},"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",[91],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[93,94,95,29,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111],"host","host hardening","hardening","re","recommendations","remediation","plan","port","verification","Bash","access","only","retention","audit","never","firewall","bind","secrets","request",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":122,"publishedAt":47},"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",[118,121],{"categoryNo":119,"categoryName":120,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[123,124,125,29,126,100,127,128,102,129,93,130,104,131,132,107,108,133,134,37],"exposure analysis","analysis","unknown","credentials","collection","ufw","ports","internet","local","scope","reconstruction","operator",{"skillNo":136,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":140,"publishedAt":47},"01M70P8QATMPKA78E4FT5D2TNA","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fsecurity-engineering\u002Fskills\u002Fhost-hardening\u002FSKILL.md",[139],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[95,93,94,103,29,111,98,97,106,99,100,101,102,110,104,105,96,107,108,109],{"skillNo":142,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":147,"publishedAt":47},"01M70NMPVJ5H0JH131P60FW4R8","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Fagentic\u002Fcode\u002Fframeworks\u002Fforensics-complete\u002Fskills\u002Fexposure-analysis\u002FSKILL.md",[145,146],{"categoryNo":119,"categoryName":120,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[124,123,107,126,100,127,102,125,93,130,104,131,132,29,108,129,128,133,134,37],{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":155,"publishedAt":47},"01M6CB4DDR0B4NNCFK7ZK7449H","fixture-skill","Exercise rule delivery.","https:\u002F\u002Fgithub.com\u002Fjmagly\u002Faiwg\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Frule-delivery\u002Fskills\u002Ffixture-skill\u002FSKILL.md",[154],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[156,157,158,159,32,160],"fixture skill","fixture","rule","delivery","exercise",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":168,"publishedAt":47},"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",[167],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[169,170,131,171,157],"pi","pi local","duplicate"]