user-service

Systematically retrieve and address PR code review comments using make pr-comments. Use when handling code review feedback or addressing PR comments.

Codex entrypoint for post-implementation BMAD FR/NFR review gates. Use after a PR, feature, or bugfix has BMAD specs and must be checked against every functional requirement, non-functional requirement, expanded quality dimension, Wikipedia system quality attribute, generated positive/negative/ edge test case, automated test and CI coverage expectation, flaky-test risk, whole-codebase impact surface, manual-test expectation, GitHub review comments and requested-changes state, and CI check before completion.

Run a BMAD spec-driven post-implementation review gate. Use after implementing a GitHub PR, feature, bugfix, or task with BMAD specs to verify every FR/NFR, pinned NonFunctionals.com NFR category, expanded quality dimension, Wikipedia system quality attribute, positive/negative/edge test case, automated test and CI coverage expectation, flaky-test risk, whole-codebase impact surface, manual test expectation, QA best practice, GitHub review comments and requested-changes state, and CI check before completion.

Design LLM-powered modules with Clean Architecture boundaries, SOLID, DRY, KISS, and provider-agnostic ports/adapters. Use when adding prompt workflows, model/provider clients, tool orchestration, AI review automation, agent skills, or other LLM-backed capabilities.

advanced elicitation. Use when the user asks about advanced elicitation.

adversarial review. Use when the user asks about adversarial review.

Research, briefs, discovery. Use when the user asks about analyst.

Technical design, architecture. Use when the user asks about architect.

Portable autonomous BMALPH planning for Codex. Use when the user wants specs from a short task description and expects the current AI session to orchestrate BMALPH subagents without human interaction.

bmad help. Use when the user asks about bmad help.

BMAD master agent — navigate phases. Use when the user asks about bmalph.

brainstorm-project. Use when the user asks about brainstorm project.

brainstorming. Use when the user asks about brainstorming.

Anytime: Navigate significant changes. May recommend start over update PRD redo architecture sprint planning or correct epics and stories. Use when the user asks about correct course.

Guided Workflow to document technical decisions. Use when the user asks about create architecture.

A guided experience to nail down your product idea. Use when the user asks about create brief.

Create the Epics and Stories Listing. Use when the user asks about create epics stories.

Expert led facilitation to produce your Product Requirements Document. Use when the user asks about create prd.

Trigger the story cycle for the next story in the sprint plan or a specified epic/story. Use when the user asks about create story.

Guidance through realizing the plan for your UX, strongly recommended if a UI is a primary piece of the proposed project. Use when the user asks about create ux.

Implementation, coding. Use when the user asks about dev.

distillator. Use when the user asks about distillator.

Analyze an existing project to produce useful documentation. Use when the user asks about document project.

Industry domain deep dive subject matter expertise and terminology. Use when the user asks about domain research.

Identify edge cases, failure paths, and boundary-condition risks. Use when the user asks for edge-case analysis.

Improve and enhance an existing PRD. Use when the user asks about edit prd.

Review and improve editorial prose quality and clarity. Use when the user asks for editorial prose review.

editorial structure. Use when the user asks about editorial structure.

Scan the existing codebase to generate a lean, LLM-optimized `project-context.md` with critical implementation rules, patterns, and conventions for AI agents. Use this for brownfield projects and when the user asks about generate project context.

Ensure PRD UX Architecture and Epics Stories are aligned. Use when the user asks about implementation readiness.

Index and organize documentation files for search and retrieval. Use when the user asks about index docs.

Market analysis competitive landscape customer needs and trends. Use when the user asks about market research.

party mode. Use when the user asks about party mode.

PRDs, epics, stories. Use when the user asks about pm.

Generate automated API and E2E tests for implemented code using the project's existing test framework (detects commonly used test frameworks). Use after implementation to add test coverage. Not for code review or story validation; use CR for that. Use when the user asks about qa automate.

Test automation, quality assurance. Use when the user asks about qa.

Unified quick flow (experimental): clarify intent plan implement review and present in a single workflow. Use when the user asks about quick dev new.

Use for quick one-off tasks, small changes, and simple apps or utilities without extensive planning. Avoid it for highly complex work unless the user explicitly asks to skip full BMAD planning. If the user is already in implementation, use it for ad-hoc tasks not already in the plan. Use when the user asks about quick dev.

Quick one-off tasks, small changes. Use when the user asks about quick flow solo dev.

Optional at epic end: Review completed work lessons learned and next epic or if major issues consider CC. Use when the user asks about retrospective.