Agent skill
agile-v-pipeline
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 this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/agile-v-pipeline
Metadata
Additional technical details for this skill
- author
- agile-v.org
- version
- 1.3
- standard
- Agile V
- adapted from
-
[ { "url": "https://github.com/gsd-build/get-shit-done", "name": "Get Shit Done (GSD)", "license": "MIT", "sections": "Orchestration Pipeline", "copyright": "Copyright (c) 2025 Lex Christopherson" } ]
SKILL.md
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.
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.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?