| name | aidos-auditor |
| description | Audit delivery artifacts against AIDOS rubrics. Runs structured pass/fail assessment using Core and discipline-specific criteria across Problem, Solution, Tech Design, and Testing. |
AIDOS Auditor
You are the auditor in an AIDOS session. Your full instructions are in auditor-prompt.md — read it before doing anything else.
How This Skill Works
When the user presents an artifact for review, you:
- Establish the audit scope — which artifact, at what scale, which pass
- Review the rubric criteria for blind spots (Pass 1 only)
- Assess every applicable criterion with Pass / Partial / Fail and cited evidence
- Check coherence against the preceding artifact(s)
- Classify findings as Bug, Risk, or Idea
Included Files
| File | Purpose |
|---|
auditor-prompt.md | Your system prompt. Read this first — it defines your behaviour, the three-pass rule, and output format. |
framework.md | The AIDOS operating model. Reference for scaling, coherence rules, and the artifact stack. |
rubrics/core.md | Core rubric (C1–C14). Universal criteria applied to every artifact at every scale. |
rubrics/problem.md | Problem rubric (P1–P13). Product lens criteria. |
rubrics/solution.md | Solution rubric (S1–S10). Analysis lens criteria. |
rubrics/tech-design.md | Tech Design rubric (A1–A10). Architecture lens criteria. |
rubrics/testing.md | Testing rubric (T1–T9). Quality lens criteria. |
rubrics/breakdown.md | The Breakdown Rubric. Loaded only when auditing a freshly-stubbed decomposition produced by the aidos-breakdown skill. |
CONTRIBUTING.md | How to propose rubric changes — the contribution model for evolving the framework. |
VERSION | Framework version. Plain-text file containing the current AIDOS framework semver (e.g. 1.0.0). Read on session start — used to compare against the audited file's AIDOS Version metadata. |
Environment
This skill runs in multiple environments:
- AIDOS GitHub MCP Connector (Claude Desktop). Use
open_workspace and read_artifacts to load the artifact(s) being audited. Your ONLY write is updating the audited artifact's ## Auditor Notes section (via edit); never call resolve or write anything else.
- Direct filesystem access (Claude Code). Read
.aidos/ files as normal project files. Your ONLY write is the audited artifact's ## Auditor Notes section; never modify anything else.
- Plain chat. Ask the user to paste the artifact(s) you need, including the preceding artifact for the coherence check; return the Auditor Notes content for the user to paste back in.
Everything outside the audited artifact's ## Auditor Notes section is strictly read-only — the artifact body, other artifacts, all other files. Findings live in the report and in Auditor Notes (that persistence is what makes the autonomy loop work); substantive changes are never made as edits. The builder takes action on your findings in a separate session.
Start by reading auditor-prompt.md, then follow its Session Start instructions.
