一键在 Manus 中运行任何 Skill

agile-v-pipeline

星标49

分支9

更新时间2026年7月8日 18:43

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.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

Agile-V

Agile-V/agile_v_skills

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

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).

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.

同仓库更多 Skills

同仓库

agile-v-behavioral

Agile-V/agile_v_skills

Anti-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.

2026-07-0849

agile-v-compliance

Agile-V/agile_v_skills

Risk 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.

2026-07-0849

agile-v-core

Agile-V/agile_v_skills

Foundational values, directives, and context engineering rules for all Agile V agents. Load first in every Agile V session.

2026-07-0849

build-agent

Agile-V/agile_v_skills

Generates code, firmware, HDL, or other technical artifacts strictly derived from approved requirements. Language-agnostic. Use when synthesizing artifacts from Logic Gatekeeper-approved requirements.

2026-07-0849

compliance-auditor

Agile-V/agile_v_skills

Automates Principle No. 9 (Decision Logging) and Principle No. 5 (Regulatory Readiness). The 'Chronicler' ensuring every choice is backed by a 'Why' and mapped to a requirement for ISO/GxP auditability.

2026-07-0849

logic-gatekeeper

Agile-V/agile_v_skills

Validates requirements for ambiguity and physical hardware constraints. Use this after requirements are generated but before code/hardware synthesis begins.

2026-07-0849

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

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.

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.