doc and text cleanup
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# BMAD Creator Tools
|
||||
# BMad Creator Tools
|
||||
|
||||
Tools for creating and extending BMAD framework components.
|
||||
Tools for creating and extending BMad framework components.
|
||||
|
||||
## Tasks
|
||||
|
||||
|
||||
@@ -11,27 +11,27 @@ activation-instructions:
|
||||
agent:
|
||||
name: The Creator
|
||||
id: bmad-the-creator
|
||||
title: BMAD Framework Extension Specialist
|
||||
title: BMad Framework Extension Specialist
|
||||
icon: 🏗️
|
||||
whenToUse: Use for creating new agents, expansion packs, and extending the BMAD framework
|
||||
whenToUse: Use for creating new agents, expansion packs, and extending the BMad framework
|
||||
customization: null
|
||||
persona:
|
||||
role: Expert BMAD Framework Architect & Creator
|
||||
role: Expert BMad Framework Architect & Creator
|
||||
style: Methodical, creative, framework-aware, systematic
|
||||
identity: Master builder who extends BMAD capabilities through thoughtful design and deep framework understanding
|
||||
focus: Creating well-structured agents, expansion packs, and framework extensions that follow BMAD patterns and conventions
|
||||
identity: Master builder who extends BMad capabilities through thoughtful design and deep framework understanding
|
||||
focus: Creating well-structured agents, expansion packs, and framework extensions that follow BMad patterns and conventions
|
||||
core_principles:
|
||||
- Framework Consistency - All creations follow established BMAD patterns
|
||||
- Framework Consistency - All creations follow established BMad patterns
|
||||
- Modular Design - Create reusable, composable components
|
||||
- Clear Documentation - Every creation includes proper documentation
|
||||
- Convention Over Configuration - Follow BMAD naming and structure patterns
|
||||
- Convention Over Configuration - Follow BMad naming and structure patterns
|
||||
- Extensibility First - Design for future expansion and customization
|
||||
- Numbered Options Protocol - Always use numbered lists for user selections
|
||||
startup:
|
||||
- Greet the user with your name and role, and inform of the *help command
|
||||
- CRITICAL: Do NOT automatically create documents or execute tasks during startup
|
||||
- CRITICAL: Do NOT create or modify any files during startup
|
||||
- Offer to help with BMAD framework extensions but wait for explicit user confirmation
|
||||
- Offer to help with BMad framework extensions but wait for explicit user confirmation
|
||||
- Only execute tasks when user explicitly requests them
|
||||
commands:
|
||||
- '*help" - Show numbered list of available commands for selection'
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
name: bmad-creator-tools
|
||||
version: 1.2.0
|
||||
short-title: Tools for creating BMAD framework components
|
||||
description: Tools for creating and extending BMAD framework components.
|
||||
short-title: Tools for creating BMad framework components
|
||||
description: Tools for creating and extending BMad framework components.
|
||||
author: Brian (BMad)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Create Agent Task
|
||||
|
||||
This task guides you through creating a new BMAD agent following the standard template.
|
||||
This task guides you through creating a new BMad agent following the standard template.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
# Create Expansion Pack Task
|
||||
|
||||
This task helps you create a sophisticated BMAD expansion pack with advanced agent orchestration, template systems, and quality assurance patterns based on proven best practices.
|
||||
This task helps you create a sophisticated BMad expansion pack with advanced agent orchestration, template systems, and quality assurance patterns based on proven best practices.
|
||||
|
||||
## Understanding Expansion Packs
|
||||
|
||||
Expansion packs extend BMAD with domain-specific capabilities using sophisticated AI agent orchestration patterns. They are self-contained packages that leverage:
|
||||
Expansion packs extend BMad with domain-specific capabilities using sophisticated AI agent orchestration patterns. They are self-contained packages that leverage:
|
||||
|
||||
- **Advanced Agent Architecture**: YAML-in-Markdown with embedded personas and character consistency
|
||||
- **Template Systems**: LLM instruction embedding with conditional content and dynamic variables
|
||||
@@ -12,7 +12,7 @@ Expansion packs extend BMAD with domain-specific capabilities using sophisticate
|
||||
- **Quality Assurance**: Multi-level validation with star ratings and comprehensive checklists
|
||||
- **Knowledge Integration**: Domain-specific data organization and best practices embedding
|
||||
|
||||
Every expansion pack MUST include a custom BMAD orchestrator agent with sophisticated command systems and numbered options protocols.
|
||||
Every expansion pack MUST include a custom BMad orchestrator agent with sophisticated command systems and numbered options protocols.
|
||||
|
||||
## CRITICAL REQUIREMENTS
|
||||
|
||||
@@ -83,7 +83,7 @@ Create `expansion-packs/{pack-name}/plan.md` with:
|
||||
|
||||
### Agents (with Character Personas)
|
||||
|
||||
- [ ] {pack-name}-orchestrator (REQUIRED: Custom BMAD orchestrator)
|
||||
- [ ] {pack-name}-orchestrator (REQUIRED: Custom BMad orchestrator)
|
||||
- Character Name: {human-name}
|
||||
- Communication Style: {style}
|
||||
- Key Commands: {command-list}
|
||||
@@ -157,7 +157,7 @@ Important: Wait for user approval before proceeding to Phase 2
|
||||
|
||||
#### 2.1 Create Orchestrator Agent with Domain-Themed Character
|
||||
|
||||
**FIRST PRIORITY**: Design the custom BMAD orchestrator with domain-appropriate theme:
|
||||
**FIRST PRIORITY**: Design the custom BMad orchestrator with domain-appropriate theme:
|
||||
|
||||
**Themed Character Design:**
|
||||
|
||||
@@ -183,7 +183,7 @@ Important: Wait for user approval before proceeding to Phase 2
|
||||
- **Activation Instructions**: Embedded YAML with behavior directives
|
||||
- **Startup Procedures**: Initialize without auto-execution
|
||||
- **Dependencies**: Clear references to tasks, templates, and data files
|
||||
- **Integration Points**: How it coordinates with core BMAD agents
|
||||
- **Integration Points**: How it coordinates with core BMad agents
|
||||
|
||||
#### 2.2 Design Specialist Agents with Character Personas
|
||||
|
||||
@@ -374,7 +374,7 @@ embedded_knowledge:
|
||||
- {domain}-terminology.md
|
||||
- {domain}-standards.md
|
||||
|
||||
# Dependencies on core BMAD components
|
||||
# Dependencies on core BMad components
|
||||
core_dependencies:
|
||||
agents:
|
||||
- architect # For system design
|
||||
@@ -863,7 +863,7 @@ Embedded knowledge (automatic):
|
||||
7. "Where in the workflow should users choose between different paths?"
|
||||
8. "How should the orchestrator hand off to specialist agents?"
|
||||
9. "What quality gates should be built into the workflow?"
|
||||
10. "How should it integrate with core BMAD agents?"
|
||||
10. "How should it integrate with core BMad agents?"
|
||||
|
||||
### Agent Planning
|
||||
|
||||
@@ -913,7 +913,7 @@ Embedded knowledge (automatic):
|
||||
**Quality and Validation:**
|
||||
|
||||
- **Plan First**: ALWAYS create and get approval for plan.md before implementing
|
||||
- **Orchestrator Required**: Every pack MUST have a custom BMAD orchestrator with sophisticated command system
|
||||
- **Orchestrator Required**: Every pack MUST have a custom BMad orchestrator with sophisticated command system
|
||||
- **Verify References**: ALL referenced tasks/templates MUST exist and be tested
|
||||
- **Multi-Level Validation**: Quality systems must provide basic, comprehensive, and expert-level assessment
|
||||
- **Domain Expertise**: Ensure accuracy in specialized fields with embedded best practices
|
||||
|
||||
@@ -70,7 +70,7 @@ Users must add these files to `bmad-core/data/`:
|
||||
|
||||
## Integration Points
|
||||
|
||||
- Depends on core agents: {list any core BMAD agents used}
|
||||
- Depends on core agents: {list any core BMad agents used}
|
||||
- Extends teams: {which teams to update}
|
||||
|
||||
## Success Criteria
|
||||
|
||||
Reference in New Issue
Block a user