BMad Code Org

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

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

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

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

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

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

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

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.

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

• Setting up the BMad Core Tools module through bmad
• Checking the module's current state through bmad
• Identifying the required setup entry point

Generate automated game tests for gameplay systems. Use when the user says "automate tests" or "generate tests"

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

Verify GDD, UX, Architecture, and Epics alignment before production. Use when the user says "check readiness" or "implementation readiness"

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

Create structured playtesting plans for user feedback. Use when the user says "playtest plan" or "playtesting"

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

Scaffold end-to-end testing infrastructure. Use when the user says "e2e scaffold" or "set up e2e testing"

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

Plan game UX, UI, and HUD design specifications. Use when the user says "lets create game UX", "design the HUD", "create UI specifications", or "help me plan the game UX"

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

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

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

Facilitate game brainstorming sessions with game-specific techniques. Use when the user says "brainstorm game" or "game ideas"

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

Consolidated game developer for story execution, code implementation, code review, QA/test authorship, and sprint orchestration. Use when the user asks to talk to Link Freeman, the Game Developer, the Game QA, or the Game Scrum Master.

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

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

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

Create, update, or validate a game's Game Design Document. Use when the user wants help producing, editing, or validating a GDD — the primary design artifact covering pillars, mechanics, progression, levels, art, audio, and development epics.

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

Forensic case investigation with evidence-graded findings, calibrated to the input. Use when the user asks to investigate a bug, trace what caused an incident, walk through unfamiliar code, or build a mental model of a code area before working on it.

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

Create, update, or validate a game brief. Use when the user wants help producing, editing, or validating a game brief before detailed design.

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

Review code changes adversarially using parallel review layers (Blind Hunter, Edge Case Hunter, Acceptance Auditor) with structured triage into actionable categories. Use when the user says "run code review" or "review this code"

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

Create comprehensive narrative documentation with story structure and world-building. Use when the user says "narrative design" or "create narrative"

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

Review test quality and coverage. Use when the user says "test review" or "review tests"

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

Initialize game test framework for Unity, Unreal, or Godot. Use when the user says "test framework" or "set up testing"

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