bmad-agent-fidelity-assessor

Assess production artifacts against source-of-truth contracts and emit Fidelity Trace Reports.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/jlenrique/course-DEV-IDE-with-AGENTS --skill bmad-agent-fidelity-assessor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-agent-fidelity-assessor
Source: https://github.com/jlenrique/course-DEV-IDE-with-AGENTS/tree/main/skills/bmad-agent-fidelity-assessor
Command: npx skills add https://github.com/jlenrique/course-DEV-IDE-with-AGENTS --skill bmad-agent-fidelity-assessor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Vera provides forensic fidelity verification to ensure production artifacts faithfully reflect their source materials across the APP pipeline, enabling auditable, evidence-based gate decisions.

Core Features & Use Cases

  • Fidelity assessment across gates G0–G6 using deterministic contracts and agentic judgments, with Fidelity Trace Reports, O/I/A taxonomy, and remediation guidance.
  • Memory and governance-aware evaluation that preserves provenance, supports per-gate contracts, and routes findings to Marcus for decisioning.
  • Use cases include when Marcus delegates fidelity gate evaluation, when Vera is invoked to audit fidelity at a gate, or when a user requests verification of an artifact's faithfulness.

Quick Start

Activate Vera for a fidelity gate by providing a context envelope with gate, run ID, artifacts, and access to the fidelity contracts.

Frequently Asked Questions about bmad-agent-fidelity-assessor

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

FAQPage Schema
How do I verify artifact fidelity against source materials in a pipeline?

To verify artifact fidelity, the assessor compares production artifacts against their source of truth using deterministic L1 contracts and perception bridges, emitting a Fidelity Trace Report with remediation guidance for any detected omissions, inventions, or alterations.

How do I audit artifacts for omissions or inventions during gate evaluation?

Fidelity audits detect omissions, inventions, and alterations by applying perception bridges alongside deterministic L1 contracts, ensuring production artifacts faithfully reflect their source materials across the pipeline.

What is a Fidelity Trace Report and how does it support gate decisions?

A Fidelity Trace Report is an evidence-based output that categorizes findings using O/I/A taxonomy and provides remediation guidance, enabling auditable gate decisions when evaluating artifact faithfulness across gates G0 through G6.

Can I evaluate fidelity across multiple gates without losing provenance?

Yes, fidelity assessment supports gates G0 through G6 while preserving provenance through memory and governance-aware evaluation, routing findings to the delegate for decisioning and maintaining per-gate contract enforcement.

What inputs are needed to start a fidelity gate evaluation?

To start fidelity gate evaluation, you must provide a context envelope containing the gate identifier, run ID, target artifacts, and access to the relevant fidelity contracts for deterministic and agentic assessment.

When should I use deterministic contracts versus agentic judgments for verification?

Deterministic L1 contracts enforce strict baseline rules, while agentic judgments handle nuanced fidelity assessment, combining both to evaluate production artifacts comprehensively and route governance findings for decisioning.