القائمة
Mechanical FR/AC compliance. Walk every functional requirement and acceptance criterion and render a binary Pass/Fail with evidence. No judgment about quality, direction, or architecture.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
The drift check. Compare what was built against the design doc and master spec. Sets the Double Gate — A3 cannot start until A1 is at zero findings.
Code/content quality. Dead code, hardcoded values, leftover TODOs, weak error handling, security holes, performance traps, standards violations. Enforces the Double Gate — blocks until A1 is at zero findings.
Vision-gap analysis. Compared to the perfect-world North Star, what is missing, drifting, or underbuilt — and what to add or change now to close the gap. Not a passive alignment scorecard.
Research the world. Real web research to find what the best teams do for every technology and pattern in the build, then implement superior approaches now (not later). The only lens that brings outside knowledge.
The boundary ritual — review what just landed, record an approval, journal it, and advance the phase. The ONLY step that writes approvals, and it does NO git.
Formally amend the constitution, with mandatory impact analysis before any change lands. The constitution is supreme law; amendments are versioned and their downstream effects scanned first.
| name | A2 — Spec Review |
| description | Mechanical FR/AC compliance. Walk every functional requirement and acceptance criterion and render a binary Pass/Fail with evidence. No judgment about quality, direction, or architecture. |
| argument-hint | <group-number> [feature-name] |
The mechanical compliance check. A2 walks every Functional Requirement (FR) and every Acceptance Criterion (AC) in the master spec and renders a binary verdict — Pass or Fail — against the implementation, with evidence. It makes no judgment about code quality (that is A3), direction (A4), or architecture (A1). Exhaustive and non-judgmental: each requirement either is satisfied by the code or it is not.
spec.md (required — the source of all FRs/ACs) · all micro specs in scope · the actual code files they referenceaudits/{scope}-a2.md: a coverage table listing every FR/AC with Pass/Fail and its evidence, a finding per failure with reasoning trace, and an overall verdict.A2 is binary and evidence-bound. A well-formed finding cites (1) the exact FR/AC ID with its wording, (2) the implementation evidence that fails it, and (3) a Pass/Fail verdict with no ambiguity. If a requirement is itself ambiguous, A2 flags the ambiguity rather than guessing intent — it never invents a passing or failing interpretation to resolve unclear spec language.
Finding format, the zero-tolerance loop (loops to zero findings), and conviction scoring are shared across all lenses — see docs/the-audit-system.md. A2 may run alongside A1, but A3 still waits on A1 being clean.
- "a2 audit group 1"
- "spec review"
- "check FR/AC compliance"