Turn ideas, briefs, product requirements, or meeting notes into actionable tickets with Sofia, the Product Owner. Break large initiatives into smaller work items, refine requirements, review board status, validate ticket structure, and replan when requirements change.
Customize installed BMad skills by turning requested changes into TOML configuration files. Adjust exposed agent or workflow settings, separate team rules from personal preferences, and verify how the changes combine with existing settings.
Create, update, or review a product requirements document, or PRD. Organize product goals, features, and quality requirements through guided discussion or a faster draft, with detail matched to the project's needs and stakes.
Turn product requirements and user experience plans into technical architecture with Winston, a system architect persona. Discuss technology choices and their trade-offs, with an emphasis on established tools, developer productivity, and designs that can be implemented.
Run one iteration of a BMad unattended development loop, with optional route and review selections. The skill follows a generated workflow and reports a halt reason or command failure when execution cannot continue.
Work with Mary, a business analyst persona, to research markets, examine competitors, and clarify requirements. Use evidence-based discussion to turn vague needs into concrete specifications that can guide the next steps of a project.
Test a product idea by writing its launch press release before building it, then answering customer and internal questions. Research informs a complete PRFAQ, a press release with frequently asked questions, plus a product requirements summary.
Write an architecture decision record, a document explaining a team's design choice. Capture the context, rejected alternatives, and future costs so newcomers can understand the reasoning, then review the draft before saving it.
Turn a product's visual and interaction goals into DESIGN.md and EXPERIENCE.md. Through guided discussion, capture appearance, screen structure, behavior, accessibility, and user journeys as specifications that can guide later design and development work.
Run a brainstorming session with creative techniques suited to a topic and goal. Choose guided questioning, collaborative ideation, or autonomous idea generation, while keeping a session log that supports resuming work after an interruption.
Consult Sally, a UX and UI specialist, to translate user needs into interaction designs and UX specifications. The role considers unusual situations as well as everyday use, helping communicate clear design intent to architecture and implementation work.
Create, update, or validate a concise architecture document from a specification, an idea, or existing code. It records shared design rules so separately developed parts follow consistent boundaries, dependencies, state changes, and data ownership.
Get guidance on using installed BMad modules and choosing the next skill for a task. The skill also handles installation setup, updates, repairs, module additions, artifact migration, and selecting the active initiative being worked on.
Examine an early idea through focused questions from different perspectives. Test assumptions, expose weak points, and clarify decisions so you can strengthen the idea, reject it, or understand it better, with a report recording the outcome.
Review code changes with several independent reviewers working in parallel, then receive organized findings. Request a quick or thorough review, choose to hand off fixes, or run without interaction when another workflow or CI job initiates the review.
Review code changes or documents through configured review lenses, each representing a different perspective. Findings identify the location, triggering condition, suggested fix, and potential consequence, with reports available as JSON, Markdown, or both.
Implement approved development stories and code changes with Amelia, a senior software engineer persona. Follow a test-first process: write a failing test, make it pass, then improve the code while checking every acceptance criterion.
Guide a person through reviewing a commit, pull request, file, or directory. The skill generates and follows a BMad workflow to lead the review of the selected target.
Build and maintain BMad skills, agents, and modules through a guided conversation. Turn prompts or session logs into reusable skills, review existing tools, and prepare modules for distribution, with approval before files are written.
This entry stores the BMad Method module’s metadata rather than providing an executable workflow. Use the separate bmad skill with setup method to initialize the module or report its existing setup state.
Review a completed epic, a group of related development tasks, against its plans, code changes, and commits. Produce a retrospective with evidence-backed findings, follow-up actions, and a decision on whether to accept the work.
Revisit a recent answer, plan, draft, or decision using selected critique methods. The skill offers relevant approaches, explains what they reveal, and proposes improvements that are applied only after the user accepts them.
Delegate a feature, bug fix, or substantial code change and carry it through implementation, review, and verification. Start from a task description or issue link, with options for the workflow route and review depth.
Evaluate BMad skills using your agent's configured runner. Compare results with the model alone or another version, grade outputs against criteria, and test whether descriptions trigger correctly, preserving transcripts and evidence for each run.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)