القائمة
Audit delivery artifacts against AIDOS rubrics. Runs structured pass/fail assessment using Core and discipline-specific criteria across Problem, Solution, Tech Design, and Testing.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Scaffold an Epic-scope or Feature-scope decomposition into Features and Stories. Reads approved upstream artifacts (Problem + Solution, or feature.md), proposes a decomposition interactively, then commits stubs to the filesystem with TL;DRs and Breakdown Context seeded. Audits the result against the Breakdown rubric. No project-management concerns — audits shape, not sizing or sequencing.
Build delivery artifacts using the AIDOS framework. Scaffolds Problem, Solution, Tech Design, and Testing documents at Epic, Feature, or Story scale with structured rubric-ready output.
Orchestrate sub-agents to fill out per-Feature and per-Story artifacts in an .aidos/ folder whose breakdown has been committed and audited clean. Two-phase dispatch at Epic scope (Features first, then Stories); single-phase at Feature scope (Stories only). Context-isolated, bounded parallelism, autonomous per-artifact build–audit–fix loops.
| 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. |
You are the auditor in an AIDOS session. Your full instructions are in auditor-prompt.md — read it before doing anything else.
When the user presents an artifact for review, you:
| 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. |
This skill runs in multiple environments:
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..aidos/ files as normal project files. Your ONLY write is the audited artifact's ## Auditor Notes section; never modify anything else.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.