my-claude

Audit Ansible playbooks, roles, collections, and inventories for production readiness. Use when reviewing an Ansible repo, before merging IaC PRs, before promoting a role to a collection, or when the user mentions ansible-lint, idempotency, vault, or molecule.

Enter planning mode — interview the user, design a phased approach, and produce an implementation plan before writing code.

Execute an approved /plan unattended — phases, agents, commits — stopping only on hard safety failures (hook exit 2, sandbox/network deny, repeated test failures). Use after /plan when the user wants hands-off execution.

Run a full read-only audit of the current project — code review, security analysis, and documentation freshness check. Use to assess project health without making changes.

Start implementing a feature with user story validation, phased execution, and quality gates. Use after planning is complete.

Take a project from "it works" to "it's shippable." Runs audit, fixes findings, walks the Definition of Done checklist, and generates a release readiness score. Use before releasing, after feature-complete, or when quality feels prototype-y.

Run the Goldfish Protocol — test a design doc's completeness by verifying a fresh session can reconstruct the plan from it alone. Use after /plan, before /implement, on any complex feature.

Document what went well, what went wrong, and what to do differently after completing a feature or fixing a hard bug. Compounds knowledge across sessions.

Create a pull request with proper title, description, test plan, and linked issues. Use when ready to submit changes for review.

Save learnings, patterns, and preferences to persistent memory. Use when the user says "remember this", encounters a hard-won fix, or wants to preserve context across sessions.

Audit code and dependencies for security vulnerabilities. Use when reviewing PRs, checking dependencies, preparing for deployment, or when user mentions security, vulnerabilities, or audit.

Scaffold a new Architecture Decision Record (ADR). Use when documenting architectural choices, technology selections, or significant design trade-offs.

Scaffold a new Critical User Journey document. Use when documenting user flows, onboarding journeys, or end-to-end scenarios.

Generate clear commit messages following project conventions. Use when writing commit messages, reviewing staged changes, or preparing releases.