143 skills (repositories by bmad-code-org) · sorted by popularity
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.
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.
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.
This metadata record supports the BMad Core Tools module. Use the separate bmad skill to set up the module or report its current state; this record is not intended to be invoked directly.
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.
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.
Create and maintain repository instructions for AI agents in AGENTS.md. Check rules against project evidence, preserve existing requirements during revisions, and record observed mistakes so future agents receive concise, relevant guidance for working in the codebase.
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.
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.
Work with John, a product manager persona, to clarify requirements through user interviews and stakeholder alignment. Turn a product vision into a PRD, a product requirements document, and small, validated increments for development.
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.
Support decisions with market, technical, competitor, and other research. Draft prompts for external research tools, condense existing reports into source-cited summaries, or conduct web research directly, including comparisons between candidates.
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.
This metadata entry records the Toolsmith module. It is not run directly; use the separate bmad skill to set up the module on first use or report its current state afterward.
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.
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.
Explore a topic through a roundtable of BMAD agents or custom personas. Create participant groups, define distinct viewpoints, and build simulated customer panels to examine ideas through an ongoing conversation with contrasting perspectives.
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.
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.
Add end-to-end tests, which check complete usage flows, and API tests for features that already work. Follow the project's existing test setup to extend automated coverage without introducing a separate testing approach.
Turn product ideas into a focused brief through guided conversation, or update and review an existing one. It records decisions, flags assumptions and unknowns, and keeps supporting detail available for later planning.
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.
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.
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.