build-agent

Generate code, firmware, and HDL artifacts from approved requirements with REQ-XXXX traceability.

50|9|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/Agile-V/agile_v_skills --skill build-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-agent
Source: https://github.com/Agile-V/agile_v_skills/tree/main/build-agent
Command: npx skills add https://github.com/Agile-V/agile_v_skills --skill build-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates artifacts (code, firmware, HDL, or other technical artifacts) strictly derived from approved requirements, ensuring traceability and deterministic outputs.

Core Features & Use Cases

  • Language-agnostic artifact synthesis from Logic Gatekeeper-approved requirements.
  • Enforces end-to-end traceability: every artifact is linked to a REQ-XXXX.
  • Supports multi-domain outputs (software, firmware, HDL, and documentation) for engineering teams.

Quick Start

Provide an approved REQUIREMENTS.md as the source of truth and run the synthesis to produce the first artifact.

Frequently Asked Questions about build-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate code and firmware from approved requirements?

To generate code and firmware from approved requirements, provide a REQUIREMENTS.md file as the source of truth and run the synthesis to produce artifacts strictly linked to their corresponding REQ-IDs.

What is requirements traceability for multi-domain engineering artifacts?

Requirements traceability for multi-domain artifacts ensures every piece of software, hardware, or firmware output is strictly derived from and linked to a specific REQ-XXXX identifier for deterministic builds.

Can I synthesize HDL and hardware artifacts from a requirements document?

Yes, you can synthesize HDL and hardware artifacts from a requirements document. The process supports multi-domain outputs across software, firmware, and hardware by enforcing gatekeeper checks.

Do I need an approved REQUIREMENTS.md to start artifact synthesis?

Yes, you need an approved REQUIREMENTS.md to start artifact synthesis. It acts as the sole source of truth, passing pre-execution validation and post-verification checks to ensure deterministic outputs.

Why does artifact generation fail without REQ-IDs in the output?

Artifact generation fails without REQ-IDs because the system applies strict gatekeeper checks. Every generated artifact must pass pre-execution validation and reference the corresponding approved requirement.