bmad-agent-audra

Detect drift between internal artifacts and code across repository sweeps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Audra detects drift and ensures lockstep fidelity between internal artifacts (docs, contracts, schemas, registries) and the code they describe.

Core Features & Use Cases

  • Deterministic L1 sweeps of artifact-related directories (docs, contracts, schemas, registries, lane matrices, and parameter directories) to verify they remain in sync with the code they describe.
  • Memory-sidecar-backed trace reports and drift pattern capture to support repeatable audits and historical analysis.
  • Structured routing to BMAD specialists (Paige, Murat, Winston, Cora) when non-code-proof gaps are discovered.

Quick Start

Run a full repository coherence sweep to validate lockstep fidelity against the current codebase.

Frequently Asked Questions about bmad-agent-audra

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

FAQPage Schema
How do I detect drift between internal artifacts and my codebase?

A memory sidecar captures trace reports and drift patterns during deterministic sweeps, supporting repeatable repo audits and historical drift analysis across artifact directories like docs, contracts, and schemas.

What is lockstep fidelity verification for repository artifacts?

Lockstep fidelity verification uses deterministic checks to ensure internal artifacts—docs, contracts, schemas, registries—remain perfectly synchronized with the code they describe, catching non-code-proof gaps before they cause integration failures.

How do I run a full repository coherence sweep?

Run a full repository coherence sweep to validate lockstep fidelity against the current codebase. The deterministic L1 sweep checks artifact-related directories, satisfies exit-code contracts, and exports structured trace reports to reports/dev-coherence.

How are drift findings routed for remediation?

Drift findings route to BMAD specialists—Paige, Murat, Winston, and Cora—when non-code-proof gaps are discovered, guiding operators to the appropriate agent for targeted remediation based on structured trace reports.

Can I audit specific directories instead of the full repository?

Directory-scoped sweeps support auditing specific artifact directories—docs, contracts, schemas, registries, lane matrices, and parameter directories—rather than the full repository, applying the same deterministic lockstep fidelity checks and trace report exports.

What is a memory-sidecar trace report for repo audits?

A memory sidecar captures trace reports and drift patterns during deterministic sweeps, supporting repeatable repo audits and historical drift analysis across artifact directories like docs, contracts, and schemas.