mighty-powers

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Use when you need to research a domain, market, or technical area before planning

Use when starting any conversation — establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Audit frontend and backend implementation against every PRD file, one by one, using parallel subagents. Produces a full status table (done / partial / not-started), identifies critical-path blockers, and recommends next sprints. Use when you need to know where you stand against your PRDs.

First-time project setup for Mighty Powers. Creates config file, artifact directories, offers to generate CLAUDE.md, and explains available workflows.

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

Produce the architecture: a lean spine of invariants that keeps everything built from it consistent, projected into whatever format the work needs. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design".

Facilitate a brainstorming session using diverse creative techniques. Use when the user says 'help me brainstorm' or 'help me ideate'.

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.

Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".

LLM-assisted human-in-the-loop review. Make sense of a change, focus attention where it matters, test. Use when the user says "checkpoint", "human review", or "walk me through this change".

Manage significant changes during sprint execution. Use when the user says "correct course" or "propose sprint change"

DEPRECATED — use mp:architecture. Kept for backward compatibility.

Break requirements into epics and user stories. Use when the user says "create the epics and stories list"

DEPRECATED — use mp:prd (create intent). Kept for backward compatibility.

Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]"

Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"

Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Document brownfield projects for AI context. Use when the user says "document this project" or "generate project docs"

Use when you have a written implementation plan to execute, with wave-by-wave parallel dispatch and persistent status tracking for session resilience

Create project-context.md with AI rules. Use when the user says "generate project context" or "create project context"

Analyzes current state and user query to answer Mighty Powers / lifecycle questions or recommend the next skill(s) to use. Use when user asks for help, bmad help, what to do next, or what to start with in BMad.

Manage project learnings across sessions. Save, search, prune, and export learnings that compound over time. Use when user wants to record, recall, or share project knowledge.

Orchestrates lively group discussions between installed BMAD agents or other personas. Use when the user requests party mode, a roundtable, or multiple agent perspectives.

Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD.

Working Backwards PRFAQ challenge to forge product concepts. Use when the user requests to 'create a PRFAQ', 'work backwards', or 'run the PRFAQ challenge'.

Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.

Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]"

Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project's existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.

Resume an interrupted implementation plan from where it stopped. Use when a session crashed, or when restarting work on an in-progress plan. Can auto-detect or be pointed to a specific plan folder.

Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"

Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"

Sprint workflow pipeline — chains plan → build → test → review → ship → verify skills into a structured sprint. Use when starting a new feature or project iteration to follow the full lifecycle.

Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"

Use whenever answering anything version-sensitive — library/framework/SDK APIs, package versions, model IDs, pricing, CLI flags, config, or "latest/newest" anything. Verify against current sources instead of training data.

Use when executing implementation plans with independent tasks in the current session

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

DEPRECATED — use mp:prd (validate intent). Kept for backward compatibility.

Use when you have a spec or requirements for a multi-step task, before touching code