Eu Ai Act Check

EU AI Act Compliance Check (9 Obligations)

Regulation: Regulation (EU) 2024/1689, Articles 9-15 Enforcement: 2 August 2026 (subject to Digital Omnibus harmonized standards conditionality) Anti-pattern: Discovering compliance gaps after EU deployment instead of during development

> ⚠️ NOT LEGAL ADVICE. This skill produces a developer-facing compliance checklist. Consult a qualified EU AI lawyer before relying on it for production EU deployment.

> Companion plugin: For the full 7-step development workflow that produces Annex IV-shaped evidence as a side effect (research → requirements → design → breakdown → build-brief → review → deploy → monitor), install pitimon/8-habit-ai-dev alongside this plugin. The two plugins are complementary by design.

When to Use

• Before major release of an AI system targeting the EU market
• During architecture design of a new high-risk AI feature
• During audit preparation for EU customers/regulators
• After significant changes to data, model, or human-oversight design

When to Skip

• System is not high-risk under Annex III (most internal tools, dev tools, non-safety AI fall outside)
• System is not deployed in the EU (no EU users, no EU market)
• Already covered by a recent (.md **in the user's project repository** (not in this plugin). Create the folder once via mkdir -p docs/compliance/eu-ai-act/reports` if it doesn't exist.

Step 3 — Conscience Check

> "Have I prevented a regulatory crisis, or am I waiting to react to one?" > "Do I understand WHY this regulation exists (protect fundamental rights), not just WHAT to comply with?"

Handoff

• Expects from predecessor: A finalized release candidate or design ready for compliance review
• Produces for successor: Compliance report + gap list. Failures route back to:
• /governance-check for risk and security gaps (Articles 9, 15 ¶4-5)
• /spec-driven-dev for oversight design gaps (Article 14)
• /create-adr for documentation gaps (Article 11)
• governance-reviewer agent for deep multi-file audit
• External (use pitimon/8-habit-ai-dev's /monitor-setup and /review-ai) for runtime concerns Articles 12 (record-keeping) and 15 ¶1-3 (accuracy)

Definition of Done

• [ ] Scope pre-flight completed; OUT OF SCOPE decisions documented
• [ ] All 9 obligations checked with Pass/Fail/N-A + 1-line evidence
• [ ] Critical gaps identified with recommended remediation route (governance skill or external)
• [ ] Report saved under docs/compliance/eu-ai-act/reports/ in the user's project repo
• [ ] Conscience Check questions answered honestly
• [ ] (For production EU deployment) Lawyer review scheduled

References

• Primary research: ${CLAUDE_PLUGIN_ROOT}/docs/research/eu-ai-act-obligations.md (verified quotes per article)
• User-facing mapping: ${CLAUDE_PLUGIN_ROOT}/docs/compliance/EU-AI-ACT-MAPPING.md (workflow + examples)
• DSGAI cross-reference: ${CLAUDE_PLUGIN_ROOT}/docs/compliance/DSGAI-MAPPING.md (Article 15 ¶5 ↔ DSGAI04/11)
• Migration provenance: ${CLAUDE_PLUGIN_ROOT}/docs/adr/ADR-003-eu-ai-act-compliance-toolkit.md

> ⚠️ NOT LEGAL ADVICE. This skill is a developer reference. The 9-obligation checklist is derived from the regulation text but interpretation is subject to Commission guidance, harmonized standards (pending), and case law. Always consult a qualified EU AI lawyer for production compliance decisions.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: pitimon
• Source: pitimon/claude-governance
• License: MIT

Install and usage instructions live in the source repository linked above.