agile-v/agile-v-pipeline
agile-v-pipeline/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add agile-v/agile_v_skills agile-v-pipelineInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 23, 2026, 4:18 AM24.0s1 file scanned
SKILL.md
- 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:
- MIT
- version:
- 1.4
- standard:
- Agile V
- author:
- agile-v.org
- sections_index:
- ["Pipeline", "Handoffs", "Wave Execution", "Checkpoint Types"]
- - name:
- Get Shit Done (GSD)
- url:
- https://github.com/gsd-build/get-shit-done
- 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
- Req Architect emits REQUIREMENTS.md -> Logic Gatekeeper reads.
- Gatekeeper -> Gate 1 (Evidence Summary, Human approves).
- Build Agent || Test Designer from REQUIREMENTS.md, no shared context.
- Build Manifest + Test Cases -> Red Team Verifier.
- 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).
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.
Related Skills
agile-v/red-team-verifier
development
VerifiedTrustedCommunity
The Verification Agent — challenges Build Agent artifacts via independent verification. Executes tests against artifacts. Use to audit code, schematics, or firmware against requirements.
43SKILL.mdUpdated Mar 27, 2026
agile-v/skills/system-understanding-agent
development
VerifiedTrustedCommunity
# Skill: system-understanding-agent ## Purpose Use this skill when Agile V is applied to an existing codebase, documentation set, or knowledge base. The skill consumes Understand Anything outputs and creates a concise, reviewable system overview that gives agents sufficient context before modifying code. This is **Gate 0** of the integrated Agile V lifecycle. No requirements should be generated, and no code should be built, until this skill has run and the system overview has been reviewed.
39SKILL.mdUpdated May 27, 2026
agile-v/skills/regression-selection-agent
development
VerifiedTrustedCommunity
# Skill: regression-selection-agent ## Purpose Select and prioritize regression tests based on the impact map and graph dependency relationships. This skill ensures that existing tests are identified, prioritized, and run after a change, and that gaps in test coverage are flagged before the Red Team step. --- ## Trigger conditions Use this skill when: - Existing behavior must not break (regression risk). - An impact map is available. - The change affects shared modules, services, or APIs.
39SKILL.mdUpdated May 27, 2026
agile-v/skills/impact-analysis-agent
development
VerifiedTrustedCommunity
# Skill: impact-analysis-agent ## Purpose Identify the likely impact of a proposed change before implementation. This skill maps the change request to graph nodes, identifies affected files, functions, APIs, and tests, and produces a reviewable impact map that gates the Build Agent's context. --- ## Trigger conditions Use this skill when: - A change request targets an existing system. - The change could affect multiple files or modules. - Regression risk exists (the change touches shared c
39SKILL.mdUpdated May 27, 2026