敏捷AI技能

Requirements artifact (source of truth)

The Requirement Architect exports the approved Blueprint (after Human Gate 1) to a requirements file (default: REQUIREMENTS.md in the project root). The Logic Gatekeeper then reads that file, validates it (ambiguity, constraints, conflicts), and writes back any user-approved adjustments to the same file. All downstream agents (Build Agent, Test Designer, Red Team Verifier, Schematic Generator, Compliance Auditor) read requirements from this file, not from in-chat handoff. Using a single persisted file as the requirements source reduces context-window pressure, avoids carrying the full Blueprint in conversation, and lets parallel or sequential agent runs (e.g. build per feature) reference the same canonical artifact.

Installation (Choose Your Platform)

Claude Code:

/plugin install agile-v-skills

Cursor: ```bash

Your First Verified Build

You: "Add user authentication"

Agent: ⚠️ HALT CONDITION: No requirement specification found

Before implementing, I'll invoke the Requirement Architect to:
1. Decompose "user authentication" into formal requirements
2. Define acceptance criteria
3. Identify security and compliance constraints

[Requirement Architect creates REQ-0001, REQ-0002...]

Build Agent: ✓ Implementation complete (ART-0001 → REQ-0001)
Red Team Verifier: Testing independently...
  - Found 2 security issues Build Agent missed
  - SECURITY-001: No max password length (DoS risk)
  
[Build Agent fixes issues based on Red Team feedback]

Red Team Verifier: ✓ All tests pass
Agent: Ready for Human Gate approval

Result: Production-ready code with full traceability and independent verification.

---

🚀 **Quick Start**

How to Use

Below are practical ways to use these skills in common editors and agents.

🏢 Enterprise & Team Integration: Standardizing Excellence

Agile V™ is built to function as the quality layer between your team’s expertise and any AI agent they use. Whether teams rely on proprietary LLMs, local models, or different IDEs, the engineering standard remains consistent across the organization. Thanks to Agent Skills every agent behaves according to the same engineering principles, no matter where or how it runs.

Understand Anything Integration

Agile V can consume an Understand Anything knowledge graph to add codebase-understanding, impact analysis, graph traceability, and regression-test selection to the Agile V lifecycle.

This enables:

• Requirement → component → test traceability
• Change-impact analysis before writing code
• Regression-test selection from the dependency graph
• Audit-ready evidence bundles with system context
• Reviewer-friendly architecture maps

Integration docs

See integrations/understand-anything/ for:

• Adapter contract (graph format → Agile V schema)
• Evidence mapping (which artifacts go where in the bundle)
• Graph assumptions and tolerant loading strategy
• Security and privacy guidance for evidence exports
• End-to-end examples