BMad Code Org

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turn ideas and notes into ticket requirements
• Break large initiatives into smaller work items
• Refine tickets and review readiness

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Researching a market before planning a project
• Examining competitors to inform a business idea
• Turning vague requests into concrete requirements

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Examining assumptions in a plan
• Reviewing a draft from several perspectives
• Exploring failure risks before a launch

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Delegating implementation of a new feature
• Fixing a bug described in an issue
• Choosing review depth for a substantial code change

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recording an agreed architecture decision
• Preserving reasons for rejecting alternatives
• Explaining past design choices to new team members

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Defining shared rules before development
• Extracting design rules from existing code
• Updating architecture for a new feature

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a pull request
• Checking uncommitted changes
• Reviewing specifications or documents

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Discuss interaction flows based on user needs
• Clarify UX specifications for implementation
• Consider unusual situations in interface design

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing an approved development story
• Making code changes with a test-first process
• Checking implementation against acceptance criteria

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a skill from a prompt or session logs
• Build an agent with a defined persona
• Fix or review an existing skill

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Test a new product concept before development
• Clarify the target customer and their problem
• Organize customer value, feasibility, and risks

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a completed epic
• Checking delivered work against ticket plans
• Recording evidence-backed improvement actions

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarify an early idea and its assumptions
• Challenge an idea from buyer, competitor, or critic perspectives
• Check a proposed change against existing project materials

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing where to start or what to do next
• Setting up or repairing a BMad installation
• Adding modules or migrating project artifacts

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 from multiple independent perspectives
• Choose a quick or thorough review
• Receive findings with fixes handed off

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a commit with guidance
• Walking through a pull request
• Reviewing a file or directory

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turning product requirements into a technical design
• Discussing trade-offs between technology choices
• Reviewing architecture with developer productivity in mind

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Exploring ideas for a new project
• Generating ideas through guided questions
• Delegating idea generation to the agent

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turn a product idea into a brief
• Update a brief when assumptions change
• Review weak assumptions before a pitch

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Identifying the module's metadata entry
• Finding how to initialize BMad Method
• Finding how to check the module's setup state

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Running one unattended development iteration
• Selecting the oneshot or full route
• Choosing none, quick, or thorough review

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 a product concept and source materials into a PRD
• Choose suitable detail for an internal tool or product launch
• Update a PRD while checking earlier decisions

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Define a product's appearance and interaction behavior
• Document screen structure and user journeys
• Update UX specifications after design changes

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adjust an agent's tone and communication style
• Apply shared team conventions
• Change a workflow's template or output path