BMad Method: Breakthrough Method of Agile AI-driven Development

The Product Brief Coach Protocol is a framework for coaching users through the creation, updating, or validation of a product brief. The protocol emphasizes a conversational approach to 'draw the brief out' of the user, ensuring the final document is honest, right-sized, and feels like the user's own creation.

Key operational principles include:

• Core Stance: Prioritize conversation over speed. Push back on unexamined assumptions and ease up as the brief firms up.
• Canvas Usage: Use a two-section Canvas structure:
  1. Brief: The primary 1-2 page deliverable (starts with status: draft).
  2. Addendum: A repository for depth that doesn't fit the brief (e.g., rejected alternatives, technical constraints, sizing data) and a Decisions subsection for a paper trail of scope cuts and overrides.
• Visuals: Use Mermaid (for quadrantChart, flowchart LR, mindmap, or flowchart) and HTML tables (for matrices and success criteria) to convey meaning faster than prose.

bmad-build-auto is an unattended automation tool for the Build implementation model. It automates a single development-loop iteration consisting of:

1. Clarify: Clarify incoming intent.
2. Spec: Create (or find and resume) a spec file.
3. Implement: Implement the change.
4. Review: Review the result.
5. Finish: Write a terminal status to the spec file or a fallback result artifact.

Architectural Boundary: bmad-build-auto owns the implementation run and the spec artifact it produces. It does not own your backlog policy. If a review finds issues outside the scope of the current story, the skill records them as deferred findings in the spec and stops. An external orchestrator is responsible for deciding whether to queue, deduplicate, or escalate those findings.

# Example conceptual invocation
# (Actual CLI command depends on the orchestrator/environment)
bmad-build-auto --intent "Implement the user login validation logic"

Drift is a design system specification for a task tracker built on shadcn/ui, Next.js, and Tailwind CSS. The design philosophy follows a "brand-layer delta" approach: it inherits 80% of its visual properties from shadcn/ui defaults and only explicitly overrides specific brand tokens (colors, typography, and shapes) to maintain a disciplined, tool-like aesthetic.

Core Design Principles

• Minimalism: Inherit shadcn defaults for everything not explicitly defined in the brand layer.
• Purposeful Accent: Use the accent color exclusively to indicate "live" or "in-focus" items. Never use it for decoration, chrome, or state badges.
• Visual Restraint: Avoid gradients, chromatic flourishes, or custom destructive colors.
• Typography: Use a serif font (Instrument Serif) only for display roles (hero text, project titles) to act as a punctuation mark; use Geist Sans for all body and UI text.
• Layout: Maintain a single-column layout with a maximum content width of max-w-3xl (768px).

name: Drift
description: Focused task tracker for solo founders and small async teams. shadcn/ui on Next.js + Tailwind; this DESIGN.md specifies the brand-layer delta only.
colors:
  primary: '#0F4C81'
  primary-foreground: '#FFFFFF'
  accent: '#F59E0B'
  accent-foreground: '#1A1208'
  primary-dark: '#5C8AC2'
  primary-foreground-dark: '#0A1A2A'
  accent-dark: '#FBC470'
  accent-foreground-dark: '#1A1208'
typography:
  display:
    fontFamily: 'Instrument Serif'
    fontSize: 36px
    fontWeight: '400'
    lineHeight: '1.15'
    letterSpacing: -0.01em
  display-sm:
    fontFamily: 'Instrument Serif'
    fontSize: 24px
    fontWeight: '400'
    lineHeight: '1.2'
rounded:
  sm: 4px
  md: 6px
  lg: 8px

The PRFAQ Coach Protocol is a coaching methodology based on Amazon's 'Working Backwards' approach. It guides users through creating a Press Release (PR) and Frequently Asked Questions (FAQ) to ensure customer-first clarity before any product development begins.

Core Components

• Press Release (PR): An announcement of the finished product. If a compelling PR cannot be written, the product is not ready.
• Customer FAQ: Validates the value proposition from the customer's perspective (external).
• Internal FAQ: Addresses feasibility, trade-offs, and risks from the builder's perspective (internal).
• The Verdict: A candid assessment of what is 'Forged in steel', what 'Needs more heat', and where there are 'Cracks in the foundation'.

Operating Principles

• Customer-first: Always redirect focus from technology/solutions to the customer's problem.
• Specificity over fluency: Reject 'weasel words' (e.g., 'best-in-class', 'seamless', 'revolutionary') in favor of concrete claims.
• Hardcore Coaching: The protocol uses direct coaching and hard questions to challenge vague answers.

The bmad-forge-idea skill is designed to take a half-formed idea and pressure-test it through persona-driven interrogation. The goal is to strengthen the idea, reject it, or clarify thinking before investing significant resources.

When to use it

Invoke this skill when you want to:

• Forge an idea
• Pressure-test an idea
• Stress-test your thinking
• Harden an idea

Core Principles

• Question, don't lecture: Lead with questions, press on weak points, and avoid vague claims.
• Avoid agreement/praise: Do not use agreement or praise to smooth the interaction; this lowers pressure and leads to shallower thinking. In attack mode, never agree with the idea until the mode ends.
• One question at a time: Work through dependencies and drive unresolved branches to concrete decisions.
• Use personas: Use different voices (installed agents, user-defined personas, or generated experts) to provide diverse perspectives and sharper objections.