One-click install
npx skills add https://github.com/devalexanderdaza/bmad-any --skill bmad-agent-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-agent-patterns
Source: https://github.com/devalexanderdaza/bmad-any/tree/main/.cursor/skills/bmad-agent-patterns
Command: npx skills add https://github.com/devalexanderdaza/bmad-any --skill bmad-agent-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates guesswork and compliance gaps when building BMAD agents, ensuring all agents follow standardized structural rules for reliable operation across supported IDEs like Claude Code, GitHub Copilot, OpenCode, and Cursor.

Core Features & Use Cases

  • Standardized 8-Step Activation: Provides the fixed activation sequence for pure-role BMAD agents, eliminating inconsistent onboarding flows.
  • Customization Schema & Merge Rules: Defines the full customize.toml structure, including layered override logic for base, team, and personal configurations.
  • Archetype Guidance: Clarifies the required file structure and configuration for the three BMAD agent archetypes (stateless, memory, autonomous) to match different use cases.
  • Use Case: When creating a new BMAD agent for your team, use this Skill to verify your agent's SKILL.md frontmatter, activation sequence, and customization files meet all compliance requirements before deployment.

Quick Start

Use the bmad-agent-patterns skill to review your new BMAD agent's SKILL.md and customize.toml files for compliance with all structural patterns and activation rules.

Frequently Asked Questions about bmad-agent-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build BMAD agents that comply with SKILL.md frontmatter and activation sequence rules?

BMAD agent compliance requires standardizing SKILL.md frontmatter formatting and implementing an 8-step activation sequence. Using established structural patterns eliminates non-compliant agent authoring and ensures reliable operation.

What is the customize.toml schema and how do layered override merge rules work for BMAD agents?

The customize.toml schema defines configuration for BMAD agents using layered override merge rules. These rules apply hierarchical logic across base, team, and personal configurations to manage agent customization without conflicts.

Does the BMAD agent activation sequence work across different IDEs like Claude Code and Cursor?

The standardized 8-step activation sequence works across supported IDEs including Claude Code, GitHub Copilot, OpenCode, and Cursor. It provides a fixed onboarding flow to ensure consistent agent behavior regardless of the environment.

How do I split responsibilities when creating a BMAD agent roster for different archetypes?

Splitting responsibilities across a BMAD agent roster requires matching agents to the three archetypes: stateless, memory, and autonomous. Archetype guidance clarifies the required file structure and configuration needed for each specific use case.

What are the limitations of using structural patterns for BMAD agent authoring?

These structural patterns apply strictly to BMAD agent creation, compliance review, and responsibility splitting. They focus on file structure, activation rules, and customize.toml schema adherence rather than handling dynamic runtime agent execution logic.