Execute systematic test coverage analysis and bug discovery for a code module

Quick commit and push using the commit skill

Quick commit using the commit skill

Create a PR for the current branch

Fetch unresolved comments on Github PR and fix them

Capture an observation for later retrospective review

Process pending observations with root cause analysis, find optimal solutions via the claude-code-optimizer, and implement improvements

Review existing code against design principles (CQS, hexagonal, DDD, naming, OOP)

Review a design document or plan against design principles (CQS, hexagonal, DDD, naming, OOP)

Analyze the current conversation for errors, inefficiencies, and friction, then perform 5 whys root cause analysis

Creates git commits with conventional commit messages. Use after completing code changes (features, fixes, refactors) or when user says 'commit'. Analyzes staged changes and generates appropriate commit messages.

Reviews existing code against design principles (CQS, hexagonal, DDD, naming, OOP). Strict gatekeeper — reports every violation with file and line references. Use when reviewing code for design quality.

Reviews design documents and implementation plans against design principles (CQS, hexagonal, DDD, naming, OOP). Strict gatekeeper — reports every violation. Use when reviewing a plan or design doc.

Manage Architecture Decision Records (ADRs) for documenting technical decisions. Use when discussing architecture, design decisions, trade-offs, or when the user mentions ADRs, architectural decisions, or wants to document a technical choice.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Continuous improvement feedback loop that captures observations during work (/note), analyzes root causes with 5 whys (/review), and implements durable improvements via the claude-code-optimizer (/retro). Triggers on retrospective, retro, improvement, feedback loop, root cause, 5 whys, observation, friction.

Transform technical PRD features into usable user stories. Use when analyzing PRDs, splitting features into stories, or when user mentions story splitting, user stories, or INVEST criteria.

Strict test-driven development state machine with red-green-refactor cycles. Enforces test-first development, meaningful failures, minimum implementations, and full verification. Activates when user requests: 'use a TDD approach', 'start TDD', 'test-drive this'.

Creates prioritized test lists for TDD using ZOMBIES ordering and Transformation Priority Premise. Analyzes feature requirements and produces a checklist of tests ordered from simplest to most complex.

Validates that tests are well-written following best practices. Checks structure, setup patterns, dependencies, naming, and detects anti-patterns. Can run as an agent to review and improve test code.

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Paranoid devil's advocate that tears apart plans, designs, and decisions. Finds everything that can go wrong using multiple critical perspectives. Use when reviewing architecture, migration plans, budgets, travel plans, career decisions, or any artifact that could fail.

Helps users unlock Claude Code's full potential. Research what's possible, validate solutions, and deliver working recommendations—not theoretical ideas. Use when discussing Claude Code workflows, skills, personas, MCP servers, hooks, or optimization.

Create git commits with meaningful messages. Use when the user says "commit", wants to commit changes, or has finished implementing a feature.

Creates complete brand identity systems including visual language, voice, and guidelines. Use after strategy is complete, or when a project needs brand definition. Reads strategy-brief.md if available.

Coordinates the full design process: strategy, brand, then UI/UX. Use when starting a complete design engagement from scratch. Manages handoffs and checkpoints between phases.

Knowledge base of design principles covering CQS, Hexagonal Architecture, DDD patterns, identity management, naming conventions, and OOP discipline. Used as reference by design review agents.

Conducts user research, competitive analysis, and market positioning to establish design foundations. Use when starting a new project, rebranding, or when design decisions need strategic grounding.

Translates brand identity into interface design systems, user flows, and platform-specific guidance. Use after brand identity is defined, or when building apps/websites. Reads strategy and brand docs if available.