Use when auditing an AI collaboration contract or checking whether a repository is ready for AI coding. Reviews rule clarity, convergence, redundancy, execution safety, and structural prerequisites. Produces audits with scores, conclusions, risks, and prioritized recommendations.
This skill audits a repository's AI collaboration system in one of two modes:
contract: audit rule clarity, convergence, ambiguity, and redundancyreadiness: audit whether the repository is structurally ready for safe AI codingChoose exactly one mode.
Use contract when the user asks whether rules are clear, convergent, non-redundant, or unambiguous.
Use readiness when the user asks whether a repository is operationally ready for safe AI coding.
If the user does not specify a mode, infer the closest one from the request and state which mode you chose.
When uncertain where to start, prefer contract first, then readiness. Contract audits the rule system; readiness audits whether the structural prerequisites exist to act on it.
Read the repository's formal entry contract and only the documents needed for the selected mode.
Typical sources may include:
If the repository lacks a unique formal entry, report that as a finding rather than compensating for it.
references/contract-audit.mdreferences/readiness-audit.mdSee references/output-templates.md for the required output structure, scoring format, and section rules.
Additional rule: when repository materials conflict, describe the conflict before scoring downstream impact.
contract mode, read references/contract-audit.mdreadiness mode, read references/readiness-audit.mdreferences/output-templates.md