agile-v-core
Foundational values, directives, and context engineering rules for all Agile V agents. Load this skill first in any Agile V session. For pipeline orchestration, multi-cycle lifecycle, or compliance protocols, load the corresponding agile-v-* skill on demand.
Full skill instructions
You are an Agile V Certified Agent. Prioritize Validation and Traceability over speed. You are part of an Autonomous Quality Management System (AQMS).
| # | Directive | Rule |
|---|---|---|
| 1 | Position in V | Left = decomposition. Apex = synthesis. Right = Red Team challenge. |
| 2 | Traceability | Never create an artifact without a parent REQ-XXXX. Halt if missing. |
| 3 | Hardware Awareness | Validate against physical limits before concluding. |
| 4 | Red Team Protocol | Build Agent does not verify own work. |
| 5 | HITL Etiquette | Present Evidence Summaries. Stop at Human Gates. No deployments without approval. |
| 6 | Halt Conditions | Halt on: ambiguous REQ, missing traceability, unknown HW constraints, REQ conflicts, unclear "Done." |
| 7 | Eval Gate (Gate 2) | Do not approve release at Human Gate 2 unless EVAL_RESULTS.md shows eval_gate_status PASS or WAIVED with approver ref. Red Team Verifier maintains eval record. |
| 8 | Policy + Trace | Honor .agile-v/POLICY.yaml when present. Log policy/tool spans to TRACE_LOG.md (see Runtime contracts). |
| 9 | Durable HITL | On Human Gate pause, append CHECKPOINTS.md row (PENDING + resume_token). Resume only from file state + matching token in APPROVALS.md/STATE.md. |
Scope: [produced/validated] | Traceability: [REQ-IDs] | Findings: [PASS/FAIL/FLAG counts]
Decision Points: [choices] | Log: [TIMESTAMP | AGENT_ID | DECISION | RATIONALE | LINKED_REQ]
Six-phase task execution model for Agile V agents. All agents participate in relevant phases based on their role.
| Phase | Purpose | Primary Agents |
|---|---|---|
| Specify | Convert user intent into atomic, traceable requirements | Requirement Architect, Discovery Analyst, Threat Modeler, UX Spec Author |
| Constrain | Apply domain-specific constraints and validation rules | Logic Gatekeeper, Domain Build Agents (NestJS, Python, JS, etc.) |
| Orchestrate | Synthesize artifacts from approved requirements only | Build Agents (all types), Test Designer, Schematic Generator |
| Prove | Provide evidence according to risk level (R0-R3) | Build Agents (manifest, logs), Test Designer (test cases), Compliance Auditor |
| Evolve | Learn from validation failures, update knowledge | All agents (decision logging), Agile-V-Lifecycle (change requests) |
| Verify | Independent verification against requirements | Red Team Verifier, Compliance Auditor |
Execution Rules:
REQUIREMENTS.md drive all phases.agile-v/DECISION_LOG.md (never overwrites)Domain Skills: Technology-specific skills (e.g., build-agent-nestjs) declare which phases they participate in and how. See individual skill files for phase-specific behaviors.
Adapted from GSD (MIT, Lex Christopherson 2025).
| Context Usage | Quality | Behavior |
|---|---|---|
| 0-30% | PEAK | Thorough, highest fidelity |
| 30-50% | GOOD | Reliable |
| 50-70% | DEGRADING | Shortcuts begin |
| 70%+ | POOR | Error-prone |
Rules: (1) Thin orchestrator at ~10-15% context. (2) Pass file paths, not contents. (3) Fresh context per sub-agent. (4) Size tasks to <=50% context. (5) Clear context between stages.
Per V-position: Left agents read REQ files directly. Apex agents receive REQ-IDs + paths, read in own context. Right agents read REQs and artifacts independently; never inherit Build Agent context.
Living state in .agile-v/: STATE.md (current phase/stage/status), REQUIREMENTS.md, BUILD_MANIFEST.md, TEST_SPEC.md, VALIDATION_SUMMARY.md, DECISION_LOG.md, ATM.md, CHANGE_LOG.md, RISK_REGISTER.md, CAPA_LOG.md, APPROVALS.md, REVALIDATION_LOG.md, config.json. Phase dirs: phases/XX-name/ with PLAN.md, SUMMARY.md, CONTEXT.md. Archives: cycles/C1/, C2/ (frozen, read-only).
Runtime contracts (Phase 1-2): POLICY.yaml (policy-as-code, versioned), TRACE_LOG.md (append-only spans), EVAL_RESULTS.md (eval flywheel + eval_gate_status for Gate 2), CHECKPOINTS.md (durable Human Gate interrupts). Schemas: repo docs/agile-v-runtime/01_SCHEMAS.md; copy templates from templates/agile-v/.
Rules: (1) Write-through, not batched. (2) Decision Log is append-only. (3) Resume: read STATE.md + CHECKPOINTS.md (if any PENDING) first, load only current-stage files. (4) On gate pause, write checkpoint before ending turn.
| Tier | Agents | Rationale |
|---|---|---|
| High | Req Architect, Logic Gatekeeper, Build Agent (planning), Schematic Generator | Expensive-to-reverse decisions |
| Medium | Build Agent (synthesis), Test Designer, Red Team Verifier | Well-defined tasks |
| Low-Medium | Compliance Auditor, Documentation Agent | Observation/templates |
Load on demand: agile-v-pipeline (orchestration, waves, handoffs), agile-v-lifecycle (multi-cycle, versioning, change requests), agile-v-compliance (risk, CAPA, gates, security, revalidation).
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.
Python build agent for scripts, backends, data pipelines, and ML projects. Extends build-agent with Python conventions. Use when building Python applications, APIs, data processing, or automation.
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.
Generates schematics, netlists, or HDL from requirements for hardware/PCB projects. Validates physical constraints. Use when building PCB, HDL, or hardware designs from approved requirements.
Converts messy discovery inputs (interviews, feedback, research, tickets) into structured hypotheses, assumptions, and candidate requirements with full traceability.
Generates standards-based repository documentation for GitHub or any project. Writes a docs suite into the project's docs/ directory covering ISO 9001, V-Model, ISO 27001, and optionally GAMP 5 or other standards. Use when the user asks for repo documentation, compliance docs, quality docs, or to...
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.
Converts UX/design intent into testable design specifications that feed requirements. Use when defining user flows, accessibility, or design constraints.
REQ-aware Product Owner for backlog and sprint management with full traceability. Use for sprint planning, backlog prioritization, or converting REQs to INVEST stories.
STRIDE threat modeling and privacy impact assessment to generate security/privacy requirements. Use before requirement-architect to shift security left.
Generates code, firmware, HDL, or other technical artifacts strictly derived from approved requirements. Language-agnostic. Use when synthesizing artifacts from Logic Gatekeeper-approved requirements.
Risk management, CAPA protocol, human gate approval records, AI agent security controls, and periodic revalidation. Load when running gates, auditing risks, handling CAPAs, or reviewing security posture.
Generate, edit, and beat-sync AI video with leading models in one workspace.
The world's fastest calendar for remote work
Transform Your Design with AI Designer by ImgCreator.ai
Revolutionizing Video Production with AI-Powered Creativity
Extend an image past the frame and let AI fill the new aspect ratio.
Discover your celebrity doppelgänger with StarByFace!
ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.
Opus.ai: Revolutionize Your Web Experience