ai-dev-loglisted

# AI Development Log Generator **Habit**: H4 (Win-Win — honest disclosure to stakeholders) + H1 (Be Proactive — produce audit trail before audit) **Anti-pattern**: Hiding AI involvement from stakeholders, or scrambling to reconstruct AI usage at audit time ## Why This Exists EU AI Act Article 11 requires technical documentation kept up-to-date through the system lifecycle. Article 13 (3)(d) requires disclosure of how AI assists the development process. Beyond compliance, transparency about AI involvement is a **deposit in the Emotional Bank Account** — stakeholders trust you more when you're upfront. This skill generates a chronological dev log showing: - Which commits had human + AI collaboration - Which AI model(s) contributed - Date ranges of AI activity - Human authors who reviewed/approved ## When to Use - Before major release for EU-targeted high-risk AI systems (Article 11 evidence) - Quarterly for projects using AI coding assistants - During audit preparation (any framework that requires AI disclosure) - When onboarding new team members (show how AI fits into workflow) ## When to Skip - Project has no AI-authored commits (no `Co-Authored-By` trailers) - Project is fully human-authored (no AI assistance in scope) - Already have a comprehensive AI usage report from another tool ## Quick Run (one command) ```bash # Default: last 90 days, markdown to stdout bash ${CLAUDE_PLUGIN_ROOT}/scripts/generate-ai-dev-log.sh # Save to compliance folder bash ${CLAUDE_PLUG