mma-audit

Audit prose artifacts for ambiguity and gaps across four subtypes.

5|4|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/zhixuan312/multi-model-agent --skill mma-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mma-audit
Source: https://github.com/zhixuan312/multi-model-agent/tree/main/packages/server/src/skills/mma-audit
Command: npx skills add https://github.com/zhixuan312/multi-model-agent --skill mma-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables structured, cross-agent auditing of prose artifacts, code-execution plans, and SKILL.md to surface ambiguity, gaps, and mismatches before they propagate.

Core Features & Use Cases

  • Four subtypes guide the audit: default for general prose, plan for plan-vs-codebase checks, spec for requirement-prose validation, and skill for SKILL.md readability.
  • Supports associating upstream specs via context blocks to enable SPEC COVERAGE alignment across rounds.
  • Integrates into MMA workflows for iterative improvements and delta tracking.

Quick Start

Post an audit request with subtype: default for a prose artifact to check coherence.

Frequently Asked Questions about mma-audit

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

FAQPage Schema
How do I audit design docs and specs for ambiguity before execution?

Auditing design docs involves performing a structured review to surface ambiguity and gaps in prose artifacts. It applies four subtypes: default, plan, spec, and skill, ensuring criteria-driven quality across documentation before mismatches propagate.

Can I check if my code-execution plans match the actual codebase?

Yes, you can check code-execution plans against the codebase using the plan audit subtype. It performs plan-vs-codebase checks to surface mismatches and gaps between proposed execution steps and the actual codebase implementation.

What is the best way to validate requirement specs against upstream coverage?

The best way to validate requirement specs is using the spec audit subtype with context blocks. It associates upstream specs via SPEC COVERAGE context blocks to align requirements across rounds and validate requirement-prose accuracy.

How do I improve SKILL.md readability for cross-agent workflows?

To improve SKILL.md readability, apply the skill audit subtype. It performs a structured audit on SKILL.md files to surface readability gaps and ensure criteria-driven quality across cross-agent documentation and playbooks.

Does the audit process support iterative improvements and delta tracking?

Yes, the audit process supports iterative improvements and delta tracking by integrating into MMA workflows via mma-context-blocks. This enables cross-agent rigor and tracks changes across multiple audit rounds.

When should I use the default audit subtype for general prose artifacts?

Use the default audit subtype when checking general prose artifacts for coherence. It performs a structured audit to surface ambiguity and gaps in general documentation that does not fit the plan, spec, or skill subtypes.