superpowers-prepared

Use this agent as the rigorous, uncompromising code-review gate for one chunk of changed files. It enforces the project's established standards and the active technology rules as hard requirements, judges the change against the host workspace's real architecture (not generic ideals), and adversarially tries to break the code before approving. Dispatched one per chunk by the carrasco-review skill.

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, refactoring with new capabilities, or architecture decisions and no approved design exists yet. Produces an approved design document before any code is written. Triggers on: "build this", "add a feature", "I want to change", "how should we", "design", "architect", "new project", "refactor", "we need to add/build/create", "implement a new". Routed by using-superpowers, or invoke directly via /brainstorming.

Rigorous, uncompromising code review driven by the harness. Plans the review (chunking changed files by topic when there are many), dispatches one aggressive "carrasco" subagent per chunk in parallel to enforce the project's established standards and the active technology rules, then aggregates the verdicts into a blocking report under .harness/reviews/. Triggers on: "carrasco review", "rigorous review", "strict code review", "review hard", "review my changes against our standards". Also used by the stop gate (verify-on-stop) and routed from requesting-code-review when a hard standards-enforcing pass is wanted.

Creates minimal, high-signal CLAUDE.md and AGENTS.md context files based on empirical best practices. Invoke on /init command, "create CLAUDE.md", "update CLAUDE.md", "write AGENTS.md", or "set up Claude Code for this project". Also invoked by brainstorming when repo lacks a context file. 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-superpowers before brainstorming when the decision space is unclear.

12 hooks across 6 events