austinpowers

Use this agent to review completed implementation work against requirements, correctness, and production readiness.

Use this agent to adversarially attack completed implementation work — find concrete ways to break the code through specific inputs, state sequences, race conditions, assumption violations, and production context mismatches that checklist-based review would miss.

MUST USE when the user wants new features, behavior changes, new projects, documents, decisions, plans, or any work where no approved design exists yet. Produces an approved design before any implementation or production begins. Triggers on: "build this", "create", "write", "plan", "decide", "design", "I want to", "help me", "we need to". Routed by using-austinpowers, or invoke directly via /brainstorming.

Creates minimal, high-signal context files for any project. For software: CLAUDE.md and AGENTS.md based on empirical best practices. For knowledge-work: PROJECT.md or CONTEXT.md that gives collaborators (human or AI) the minimum context needed to contribute correctly. Invoke on /init command, "create CLAUDE.md", "set up project context", "write an onboarding doc", or when a project lacks a context file for new contributors. tools: Read, Glob, Grep, Bash, Edit

Use in long or noisy sessions to persist durable state across session boundaries via state.md. Also generates project-map.md when asked to map the project. Triggers on: user explicitly asks to "save state", "compress context", "map this project", "generate project map", "create project map", cross-session handoff needed, or repeated failures indicate context is getting stale.

Use BEFORE brainstorming when facing a complex architectural, technology, or design decision where the options are not yet well-defined or the problem itself may need reframing. Assembles named stakeholder perspectives that each speak once without debate, then surfaces where they converge and where real tension remains — without forcing a premature choice. Triggers on: "should we use X or Y", "not sure which approach", "evaluate these options", "what are the trade-offs between", "help me think through this decision", "architecture decision", "technology choice". Routed by using-austinpowers before brainstorming when the decision space is unclear.

MUST USE when updating, migrating, or auditing project dependencies: upgrading packages, fixing security vulnerabilities (CVEs), resolving breaking changes, migrating to new major versions, or auditing outdated dependencies. Enforces incremental updates with verification at each step. Distinct from systematic-debugging (which fixes application bugs) and refactoring (which restructures application code). Triggers on: "update dependencies", "upgrade packages", "npm update", "pip upgrade", "outdated", "vulnerability", "CVE", "security advisory", "breaking change", "migration guide", "dependency conflict", "peer dependency", "update to latest", "audit dependencies", "npm audit", "dependabot". Routed by using-austinpowers, or invoke directly via /dependency-management.

10 hooks across 6 events