agile-v-pipeline

$npx mdskill add Agile-V/agile_v_skills/agile-v-pipeline

Orchestrates multi-agent pipeline with handoffs and checkpoints for Agile V workflow.

  • Manages stage transitions and human gates in a 5-stage pipeline.
  • Depends on agile-v-core and file-based artifacts like REQUIREMENTS.md.
  • Uses handoff protocols and checkpoint types to decide stage progression.
  • Delivers pipeline state via evidence summaries and checkpoint files.

SKILL.md

.github/skills/agile-v-pipelineView on GitHub ↗
---
name: agile-v-pipeline
description: Orchestration pipeline, wave execution, handoff protocols, and checkpoint types for the Agile V 5-stage workflow. Load when orchestrating multi-agent pipelines or managing stage transitions.
license: CC-BY-SA-4.0
metadata:
  version: "1.4"
  standard: "Agile V"
  author: agile-v.org
  sections_index: ["Pipeline", "Handoffs", "Wave Execution", "Checkpoint Types"]
  adapted_from:
    - name: "Get Shit Done (GSD)"
      url: "https://github.com/gsd-build/get-shit-done"
      license: "MIT"
      copyright: "Copyright (c) 2025 Lex Christopherson"
      sections: "Orchestration Pipeline"
---

# Instructions

Orchestration pipeline for Agile V. Requires **agile-v-core** loaded first.

## Pipeline

```
Stage 1: Requirements -> Stage 2: Validation -> [Human Gate 1] -> Stage 3: Synthesis (Build Agent || Test Designer) -> Stage 4: Verification -> [Human Gate 2] -> Stage 5: Acceptance
Compliance Auditor observes all stages.
```

## Handoffs

1. Req Architect emits REQUIREMENTS.md -> Logic Gatekeeper reads.
2. Gatekeeper -> Gate 1 (Evidence Summary, Human approves).
3. Build Agent || Test Designer from REQUIREMENTS.md, no shared context.
4. Build Manifest + Test Cases -> Red Team Verifier.
5. Validation Summary -> Gate 2.

**Gate 2 prereqs (Phase 1):** `EVAL_RESULTS.md` + `VALIDATION_SUMMARY.md` **EvalGate** line. **Gate pause (Phase 2):** append `CHECKPOINTS.md` (`PENDING` + `resume_token`); resume only with matching `APPROVALS.md` entry (see `agile-v-core`).

## Stage Failure Handling

If a stage fails (e.g., Logic Gatekeeper rejects requirements, Red Team finds CRITICAL issues), the pipeline **stops at that stage**. Do not proceed to the next stage.

| Failure | Action |
|---------|--------|
| Gate 1 rejected | Return to Stage 1; Req Architect updates REQUIREMENTS.md |
| Build Agent HALT | Human resolves blocker; Build Agent resumes; do not skip to Stage 4 |
| Red Team FAIL | Return to Stage 3; Builder addresses findings; re-verify affected only |
| Gate 2 blocked | Do not proceed to Stage 5; resolve EVAL gate or get WAIVED approval |

Never advance to Stage 5 with open CRITICAL or MAJOR findings.

## Wave Execution

Dependency analysis -> Wave assignment (no-deps = Wave 1) -> Parallel within waves (fresh context each) -> Sequential across waves -> Prefer vertical slices (feature > layer).

## Checkpoint Types


| Type           | Action                 |
| -------------- | ---------------------- |
| Auto           | Proceed                |
| Human-Verify   | Confirm output         |
| Human-Decision | Choose alternative     |
| Human-Action   | Physical/external step |


All except Auto require Human Gate protocol.

More from Agile-V/agile_v_skills

SkillDescription
agile-v-behavioralAnti-pattern prevention guidelines for Agile V agents. Prevents common LLM coding mistakes while maintaining Agile V traceability. Use when implementing requirements to avoid overcomplication, silent assumptions, scope creep, and verification failures.
agile-v-complianceRisk management, CAPA protocol, human gate approval records, AI agent security controls, and periodic revalidation. Load when running gates, handling CAPAs, or auditing compliance and security posture.
agile-v-control-matrixDefines and checks the Agile-V control matrix for agentic tasks, skills, model use, tools, logs, rights, Human Gates, tests, costs, rollback, and owners. Load when creating, reviewing, or enforcing `.agile-v/CONTROL_MATRIX.yaml` or runtime governance for agentic execution.
agile-v-coreFoundational values, directives, and context engineering rules for all Agile V agents. Load first in every Agile V session.
agile-v-lifecycleMulti-cycle iteration management, document versioning, change requests, re-entry points, archival, and impact analysis. Load when starting a new cycle (C2+), processing change requests, or managing cross-cycle traceability.
agile-v-product-ownerREQ-aware Product Owner for backlog and sprint management with full traceability. Use for sprint planning, backlog prioritization, or converting REQs to INVEST stories.
agile-v-quality-gatesQuality validation gates for Agile V agents. Adds interface validation, test quality checks, data type awareness, and time allocation guidance to prevent common failure patterns identified in comprehensive testing.
build-agentGenerates code, firmware, HDL, or other technical artifacts strictly derived from approved requirements. Language-agnostic. Use when synthesizing artifacts from Logic Gatekeeper-approved requirements.
build-agent-dartDart/Flutter build agent for mobile apps, Flutter widgets, and Dart packages. Extends build-agent with Dart-specific conventions. Use when building Flutter apps, Dart packages, or mobile (iOS/Android) features.
build-agent-embeddedC/C++ build agent for embedded systems, firmware, and MCU projects. Extends build-agent with embedded constraints. Use when building firmware, bare-metal code, or resource-constrained systems.