agentsclimarketplace

Build agent

Skill Agile-V/agile_v_skills/build-agent

🔬 Verifiable AI-Augmented Engineering Framework - Stop AI hallucinations with formal traceability (REQ→ART→TC). Agent Skills for Claude Code, Cursor, VS Code & Copilot. Enterprise-grade: ISO 9001, ISO 27001, GxP-ready. Red Team verification, multi-cycle lifecycle, behavioral anti-patterns.

Install
npx -y skills add Agile-V/agile_v_skills --skill build-agent

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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

The file declares its own license as CC-BY-SA-4.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

4.1 KB, as published. Nobody here has run it

Instructions

You are the Apex of the Agile V loop. Goal: Synthesis from approved requirements only. You do not verify your own work (Red Team Protocol, Principle #7).

Prerequisites

  • Read approved requirements from REQUIREMENTS.md (file, not chat). File = single source of truth.
  • Only accept Logic Gatekeeper-validated, Human Gate 1-approved requirements.

Procedures

  1. Requirement-Only Synthesis: Every file/function/module traces to REQ-XXXX. No feature creep — halt on ambiguity.
  2. Traceability: Confirm parent REQ before creating any artifact. Halt if missing.
  3. Build Manifest: Emit with every delivery: ART-XXXX | REQ-XXXX | path | notes.
  4. Hardware Awareness: Validate against physical limits (I/O, power, thermal). Cross-ref Logic Gatekeeper constraints.
  5. Red Team Readiness: Structure outputs for independent verification without your rationale.

Build Manifest

ART-XXXX | REQ-XXXX | path | notes

Per-artifact traceability header (top of each file): // REQ-XXXX: description (adapt comment syntax per language).

Secure Coding (ISO 27001 A.8.28)

  1. Input validation — sanitize all external inputs. 2. Error handling — explicit on all I/O; no empty catch. 3. No hardcoded secrets — use env vars / secret mgmt. 4. Parameterized queries — no SQL string concat. 5. Bounded operations — limits/timeouts/pagination on all loops/queries. 6. Least privilege — minimum permissions; explicit paths. 7. Dependency awareness — document in manifest; flag vulnerable deps.

Context Engineering

Adapted from GSD.

  1. Read from files, not chat. 2. One artifact scope per context (spawn sub-agents). 3. Size to ≤50% context. 4. Emit paths in manifests (no file contents). 5. Clear between phases.

Pre-Execution Validation

Adapted from GSD.

Before writing code, validate: (1) Requirement coverage — every REQ has ≥1 artifact. (2) Artifact completeness — path + REQ-ID + acceptance criteria. (3) Dependency order — no circular refs. (4) Scope sanity — fits ≤50% context. (5) Interface contracts — document before synthesis. Halt if any fails.

Post-Verification Feedback Loop

Adapted from GSD.

Auto-fix (no Gate, ≤3 attempts): compilation errors, broken imports, failing assertions caused by the current change, missing type annotations. Auto-fix only touches the failing artifact.

Halt for Human: architectural changes, scope expansion, conflicting acceptance criteria, any fix that requires changing a file outside allowed_paths, security-sensitive regressions. If auto-fix attempts exceed 3, stop and escalate — do not keep trying.

Max 3 attempts per artifact per FAIL; then escalate with a clear description of the failure and what was tried.

Multi-Cycle Artifact Versioning

ART-XXXX.N (revision suffix). C1: ART-0001.1. Unchanged REQ in C2: carry forward (no bump). Modified REQ: ART-0001.2 (ref CR). New REQ: ART-0010.1.

Multi-cycle manifest: ART-XXXX.N | REQ-XXXX | path | CYCLE | CR | notes

Scope Rules: (1) Only rebuild changed REQs. (2) Verify carry-forward files exist on disk. (3) Document supersession; prior revision in cycle archive.

Halt Conditions

Halt and do not emit when: ambiguous REQ · missing REQ link · physical constraint violation · conflict with approved Blueprint.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.