45 skills published by Agile-V across 1 repository. Together they weigh 142 876 tokens — that is what loading all of them at once would cost you in context.
45 skills 142 876 tokens total
Captures, validates, compares, and summarizes the AI system context that influenced an Agile-V task. Produces AI_RUN_MANIFEST, AI_BOM_EVIDENCE_FRAGMENT, AI_INFLUENCE_SUMMARY, and optional CycloneDX ML-BOM export. Load for any L1+ AI-assisted task requiring provenance, compliance, or release evidence.
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.
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.
Defines and checks the Agile-V control matrix for agentic tasks, skills, model use, tools, logs, rights, Human Gates, tests, costs, rollback, and owners. Load when creating, reviewing, or enforcing `.agile-v/CONTROL_MATRIX.yaml` or runtime governance for agentic execution.
Foundational values, directives, and context engineering rules for all Agile V agents. Load first in every Agile V session.
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.
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.
REQ-aware Product Owner for backlog and sprint management with full traceability. Use for sprint planning, backlog prioritization, or converting REQs to INVEST stories.
Quality validation gates for Agile V agents. Adds interface validation, test quality checks, data type awareness, and time allocation guidance to prevent common failure patterns identified in comprehensive testing.
Generates code, firmware, HDL, or other technical artifacts strictly derived from approved, baselined requirements. Language-agnostic. Use when synthesizing artifacts from Logic Gatekeeper-reviewed requirements with Gate 1 approval and baseline capture.
Dart/Flutter build agent for mobile apps, Flutter widgets, and Dart packages. Extends build-agent with Dart-specific conventions. Use when building Flutter apps, Dart packages, or mobile (iOS/Android) features.
C/C++ build agent for embedded systems, firmware, and MCU projects. Extends build-agent with embedded constraints. Use when building firmware, bare-metal code, or resource-constrained systems.
JavaScript/TypeScript/Web build agent for web apps, Node backends, and frontend components. Extends build-agent with JS/Web conventions. Use when building web apps, APIs, or frontend/backend features.
NestJS backend build agent for REST/GraphQL APIs, microservices, and enterprise backends. Extends build-agent with NestJS architectural patterns, dependency injection, testing strategies, and security best practices. Use when building NestJS applications.
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.
Manages financial planning, OKRs, team resources, vendor relationships, and operational compliance with full traceability. Use for budgeting, OKR tracking, resource planning, vendor management, or operational risk assessment.
Chief Executive Officer (CEO) orchestrator for strategic alignment, cross-C-suite coordination, board relations, crisis management, and executive decision governance. Orchestrates all C-suite agents and venture-strategist.
Chief Financial Officer (CFO) orchestrator for financial modeling, fundraising strategy, cash management, financial controls, board reporting, and unit economics governance. Orchestrates business-operations (finance) and venture-strategist (investor relations).
Chief Operating Officer (COO) orchestrator for cross-functional execution, process design, delivery cadence governance, vendor escalation, resource arbitration, and operational playbooks. Orchestrates business-operations (ops), release-manager, agile-v-product-owner, gtm-executor.
Chief People Officer (CHRO) orchestrator for organizational design, hiring, compensation, culture, performance management, DE&I, and talent development. Use when defining org structure, hiring plans, compensation bands, culture principles, or people operations.
Chief Technology Officer (CTO) orchestrator for architecture governance, build-vs-buy decisions, tech debt management, engineering standards, platform strategy, and security posture. Orchestrates rd-innovator, build-agent, observability-planner, threat-modeler.
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.
Core abstractions, protocols, and patterns shared across all C-Suite orchestrator skills. Load this before any C-Suite skill to provide governance primitives, executive gate protocols, and multi-cycle patterns.
Generates periodic executive briefings (weekly/monthly/quarterly) by aggregating health status, critical alerts, key decisions, and upcoming milestones from all C-Suite domain dashboards into a single narrative update.
Create evidence explaining the actual implementation diff and its relationship to the predicted impact, closing the loop between pre-change prediction and post-change reality.
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 create/refresh the docs/ suite.
Create traceability from Agile V requirements to Understand Anything graph nodes, changed files, and tests, ensuring full evidence chain coverage.
Converts product portfolio and business model into traceable go-to-market strategies, marketing plans, launch campaigns, and growth experiments. Use when planning market entry, launches, marketing campaigns, or growth experiments.
Identify the likely impact of a proposed change before implementation by mapping it to graph nodes, affected files, functions, APIs, and tests.
Validates requirements for ambiguity and physical hardware constraints. Use this after requirements are generated but before code/hardware synthesis begins.
Defines metrics, events, dashboards, alerts, and SLOs to monitor production systems. Use after Gate 2 or with release-manager to ensure production observability.
Manages R&D pipeline, technology scouting, prototyping, and IP tracking with traceable innovation-to-product handoff. Use when evaluating technologies, managing prototypes, or transferring validated innovations to the engineering pipeline.
The Verification Agent — challenges Build Agent artifacts via independent verification. Executes tests against artifacts. Use to audit code, schematics, or firmware against requirements.
Select and prioritize regression tests based on the impact map and graph dependency relationships, flagging coverage gaps before the Red Team step.
Manages post-Gate-2 release activities with Agile V rigor. Rollout plans, rollback procedures, sign-off checklists. Use after Human Gate 2 for production deployment.
Converts high-level product intent into traceable PRDs and User Stories. Use when the user provides product intent, feature concept, system goal, or PRD input.
Establishes a tailored safety lifecycle from hazards through operational feedback and assurance evidence. Use when a system can create unacceptable harm.
Generates schematics, netlists, or HDL from approved, baselined requirements for hardware/PCB projects. Validates physical constraints. Use when building PCB, HDL, or hardware designs after Gate 1 approval and baseline capture.
Consume Understand Anything outputs and create a concise, reviewable system overview that gives agents sufficient context before modifying code (Gate 0).
Designs the verification suite from approved, baselined requirements only — never from code. Prevents success bias. Use when building test cases in parallel with the Build Agent after Gate 1 approval and baseline capture.
STRIDE threat modeling and privacy impact assessment to generate security/privacy requirements. Use before requirement-architect to shift security left.
Converts UX/design intent into testable design specifications that feed requirements. Use when defining user flows, accessibility, or design constraints.
Plans and assesses intended-use validation with representative users and operational environments. Use after verification to decide whether the right system was built for its defined intended use.
Converts vision and market opportunity into traceable business models, product portfolios, and strategic plans. Use when defining business strategy, product direction, competitive positioning, or fundraising materials.