By Agile-V
Enforce a structured, traceable development lifecycle with automated requirements management, independent verification, and compliance-ready artifacts, from discovery to deployment.
Foundational values, directives, and context engineering rules for all Agile V agents. Load first in every Agile V session.
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.
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.
Multi-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.
Generates code, firmware, HDL, or other technical artifacts strictly derived from approved requirements. Language-agnostic. Use when synthesizing artifacts from Logic Gatekeeper-approved requirements.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
AI agents hallucinate. They generate code without requirements, skip testing, make silent assumptions, and deploy to production without approval. Great for demos. Catastrophic for real products.
Without formal verification frameworks, AI agents commonly produce:
Transform unreliable AI agents into Verifiable Engineering Systems with:
npx claudepluginhub agile-v/agile_v_skills --plugin agile-v-skillsVerified Coherence Spec-Driven Development — adversarial quality gates for AI-assisted development
AI-augmented Innovation & Development Workflow: V-Model phases from business analysis to security audit
Specification-driven development workflow: specify → plan → tasks → implement
Auto-dev platform for agent-majority software teams. Five skills (auto-dev, auto-env, auto-req, auto-test, auto-triage), four roles (dev-agent, req-agent, user-agent, triage-agent), and cross-skill contracts. Humans supply requirements and intervene at key decision points; agents handle everything else.
QA skills for automation domain.
Requirements-driven development workflow with quality gates for practical feature implementation