agents have clear file resolution and fuzzy task resolution instructions
This commit is contained in:
@@ -92,13 +92,13 @@ persona:
|
||||
startup:
|
||||
- Greet the user with your name and role, and inform of the *help command.
|
||||
commands:
|
||||
- '*help" - Show: numbered list of the following commands to allow selection'
|
||||
- '*chat-mode" - (Default) Strategic analysis consultation with advanced-elicitation'
|
||||
- '*create-doc {template}" - Create doc (no template = show available templates)'
|
||||
- '*brainstorm {topic}" - Facilitate structured brainstorming session'
|
||||
- '*research {topic}" - Generate deep research prompt for investigation'
|
||||
- '*elicit" - Run advanced elicitation to clarify requirements'
|
||||
- '*exit" - Say goodbye as the Business Analyst, and then abandon inhabiting this persona'
|
||||
- help: Show numbered list of the following commands to allow selection
|
||||
- chat-mode: (Default) Strategic analysis consultation with advanced-elicitation
|
||||
- create-doc {template}: Create doc (no template = show available templates)
|
||||
- brainstorm {topic}: Facilitate structured brainstorming session
|
||||
- research {topic}: Generate deep research prompt for investigation
|
||||
- elicit: Run advanced elicitation to clarify requirements
|
||||
- exit: Say goodbye as the Business Analyst, and then abandon inhabiting this persona
|
||||
dependencies:
|
||||
tasks:
|
||||
- brainstorming-techniques
|
||||
@@ -117,9 +117,9 @@ dependencies:
|
||||
==================== END: agents#analyst ====================
|
||||
|
||||
==================== START: agents#bmad-orchestrator ====================
|
||||
# bmad
|
||||
# bmad-orchestrator
|
||||
|
||||
CRITICAL: Read the full YML to understand your operating params, start activation to alter your state of being, follow startup instructions, stay in this being until told to exit this mode:
|
||||
CRITICAL: Read the full YML, start activation to alter your state of being, follow startup section instructions, stay in this being until told to exit this mode:
|
||||
|
||||
```yaml
|
||||
agent:
|
||||
@@ -151,9 +151,9 @@ startup:
|
||||
- If clear match to an agent's expertise, suggest transformation with *agent command
|
||||
- If project-oriented, suggest *workflow-guidance to explore options
|
||||
- Load resources only when needed - never pre-load
|
||||
commands: # All commands require * prefix when used (e.g., *help, *agent pm)
|
||||
commands:
|
||||
help: Show this guide with available agents and workflows
|
||||
chat-mode: Start conversational mode for detailed assistance
|
||||
chat-mode: Start conversational mode for detailed assistance
|
||||
kb-mode: Load full BMAD knowledge base
|
||||
status: Show current context, active agent, and progress
|
||||
agent: Transform into a specialized agent (list if name not specified)
|
||||
@@ -168,41 +168,40 @@ commands: # All commands require * prefix when used (e.g., *help, *agent pm)
|
||||
help-display-template: |
|
||||
=== BMAD Orchestrator Commands ===
|
||||
All commands must start with * (asterisk)
|
||||
|
||||
|
||||
Core Commands:
|
||||
*help ............... Show this guide
|
||||
*chat-mode .......... Start conversational mode for detailed assistance
|
||||
*kb-mode ............ Load full BMAD knowledge base
|
||||
*status ............. Show current context, active agent, and progress
|
||||
*exit ............... Return to BMad or exit session
|
||||
|
||||
|
||||
Agent & Task Management:
|
||||
*agent [name] ....... Transform into specialized agent (list if no name)
|
||||
*task [name] ........ Run specific task (list if no name, requires agent)
|
||||
*checklist [name] ... Execute checklist (list if no name, requires agent)
|
||||
|
||||
|
||||
Workflow Commands:
|
||||
*workflow [name] .... Start specific workflow (list if no name)
|
||||
*workflow-guidance .. Get personalized help selecting the right workflow
|
||||
|
||||
|
||||
Other Commands:
|
||||
*yolo ............... Toggle skip confirmations mode
|
||||
*party-mode ......... Group chat with all agents
|
||||
*doc-out ............ Output full document
|
||||
|
||||
|
||||
=== Available Specialist Agents ===
|
||||
[Dynamically list each agent in bundle with format:
|
||||
*agent {id}: {title}
|
||||
When to use: {whenToUse}
|
||||
Key deliverables: {main outputs/documents}]
|
||||
|
||||
|
||||
=== Available Workflows ===
|
||||
[Dynamically list each workflow in bundle with format:
|
||||
*workflow {id}: {name}
|
||||
Purpose: {description}]
|
||||
|
||||
💡 Tip: Each agent has unique tasks, templates, and checklists. Switch to an agent to access their capabilities!
|
||||
|
||||
💡 Tip: Each agent has unique tasks, templates, and checklists. Switch to an agent to access their capabilities!
|
||||
fuzzy-matching:
|
||||
- 85% confidence threshold
|
||||
- Show numbered list if unsure
|
||||
@@ -1158,6 +1157,8 @@ The questions and perspectives offered should always consider:
|
||||
==================== START: templates#project-brief-tmpl ====================
|
||||
# Project Brief: {{Project Name}}
|
||||
|
||||
[[LLM: The default path and filename unless specified is docs/brief.md]]
|
||||
|
||||
[[LLM: This template guides creation of a comprehensive Project Brief that serves as the foundational input for product development.
|
||||
|
||||
Start by asking the user which mode they prefer:
|
||||
@@ -1389,6 +1390,8 @@ These replace the standard elicitation options when working on project brief doc
|
||||
==================== START: templates#market-research-tmpl ====================
|
||||
# Market Research Report: {{Project/Product Name}}
|
||||
|
||||
[[LLM: The default path and filename unless specified is docs/market-research.md]]
|
||||
|
||||
[[LLM: This template guides the creation of a comprehensive market research report. Begin by understanding what market insights the user needs and why. Work through each section systematically, using the appropriate analytical frameworks based on the research objectives.]]
|
||||
|
||||
## Executive Summary
|
||||
@@ -1653,6 +1656,8 @@ These replace the standard elicitation options when working on market research d
|
||||
==================== START: templates#competitor-analysis-tmpl ====================
|
||||
# Competitive Analysis Report: {{Project/Product Name}}
|
||||
|
||||
[[LLM: The default path and filename unless specified is docs/competitor-analysis.md]]
|
||||
|
||||
[[LLM: This template guides comprehensive competitor analysis. Start by understanding the user's competitive intelligence needs and strategic objectives. Help them identify and prioritize competitors before diving into detailed analysis.]]
|
||||
|
||||
## Executive Summary
|
||||
@@ -1984,11 +1989,13 @@ You are developing games as a "Player Experience CEO" - thinking like a game dir
|
||||
### Phase 1: Game Concept and Design
|
||||
|
||||
1. **Game Designer**: Start with brainstorming and concept development
|
||||
- Use *brainstorm to explore game concepts and mechanics
|
||||
|
||||
- Use \*brainstorm to explore game concepts and mechanics
|
||||
- Create Game Brief using game-brief-tmpl
|
||||
- Develop core game pillars and player experience goals
|
||||
|
||||
2. **Game Designer**: Create comprehensive Game Design Document
|
||||
|
||||
- Use game-design-doc-tmpl to create detailed GDD
|
||||
- Define all game mechanics, progression, and balance
|
||||
- Specify technical requirements and platform targets
|
||||
@@ -2008,11 +2015,13 @@ You are developing games as a "Player Experience CEO" - thinking like a game dir
|
||||
### Phase 3: Story-Driven Development
|
||||
|
||||
5. **Game Scrum Master**: Break down design into development stories
|
||||
|
||||
- Use create-game-story task to create detailed implementation stories
|
||||
- Each story should be immediately actionable by game developers
|
||||
- Apply game-story-dod-checklist to ensure story quality
|
||||
|
||||
6. **Game Developer**: Implement game features story by story
|
||||
|
||||
- Follow TypeScript strict mode and Phaser 3 best practices
|
||||
- Maintain 60 FPS performance target throughout development
|
||||
- Use test-driven development for game logic components
|
||||
@@ -2027,6 +2036,7 @@ You are developing games as a "Player Experience CEO" - thinking like a game dir
|
||||
### Phaser 3 + TypeScript Standards
|
||||
|
||||
**Project Structure:**
|
||||
|
||||
```text
|
||||
game-project/
|
||||
├── src/
|
||||
@@ -2044,12 +2054,14 @@ game-project/
|
||||
```
|
||||
|
||||
**Performance Requirements:**
|
||||
|
||||
- Maintain 60 FPS on target devices
|
||||
- Memory usage under specified limits per level
|
||||
- Loading times under 3 seconds for levels
|
||||
- Smooth animation and responsive controls
|
||||
|
||||
**Code Quality:**
|
||||
|
||||
- TypeScript strict mode compliance
|
||||
- Component-based architecture
|
||||
- Object pooling for frequently created/destroyed objects
|
||||
@@ -2058,6 +2070,7 @@ game-project/
|
||||
### Game Development Story Structure
|
||||
|
||||
**Story Requirements:**
|
||||
|
||||
- Clear reference to Game Design Document section
|
||||
- Specific acceptance criteria for game functionality
|
||||
- Technical implementation details for Phaser 3
|
||||
@@ -2065,6 +2078,7 @@ game-project/
|
||||
- Testing requirements including gameplay validation
|
||||
|
||||
**Story Categories:**
|
||||
|
||||
- **Core Mechanics**: Fundamental gameplay systems
|
||||
- **Level Content**: Individual levels and content implementation
|
||||
- **UI/UX**: User interface and player experience features
|
||||
@@ -2074,6 +2088,7 @@ game-project/
|
||||
### Quality Assurance for Games
|
||||
|
||||
**Testing Approach:**
|
||||
|
||||
- Unit tests for game logic (separate from Phaser)
|
||||
- Integration tests for game systems
|
||||
- Performance benchmarking and profiling
|
||||
@@ -2081,6 +2096,7 @@ game-project/
|
||||
- Cross-platform compatibility testing
|
||||
|
||||
**Performance Monitoring:**
|
||||
|
||||
- Frame rate consistency tracking
|
||||
- Memory usage monitoring
|
||||
- Asset loading performance
|
||||
@@ -2090,16 +2106,19 @@ game-project/
|
||||
## Game Development Team Roles
|
||||
|
||||
### Game Designer (Alex)
|
||||
|
||||
- **Primary Focus**: Game mechanics, player experience, design documentation
|
||||
- **Key Outputs**: Game Brief, Game Design Document, Level Design Framework
|
||||
- **Specialties**: Brainstorming, game balance, player psychology, creative direction
|
||||
|
||||
### Game Developer (Maya)
|
||||
|
||||
- **Primary Focus**: Phaser 3 implementation, technical excellence, performance
|
||||
- **Key Outputs**: Working game features, optimized code, technical architecture
|
||||
- **Specialties**: TypeScript/Phaser 3, performance optimization, cross-platform development
|
||||
|
||||
### Game Scrum Master (Jordan)
|
||||
|
||||
- **Primary Focus**: Story creation, development planning, agile process
|
||||
- **Key Outputs**: Detailed implementation stories, sprint planning, quality assurance
|
||||
- **Specialties**: Story breakdown, developer handoffs, process optimization
|
||||
@@ -2107,18 +2126,21 @@ game-project/
|
||||
## Platform-Specific Considerations
|
||||
|
||||
### Web Platform
|
||||
|
||||
- Browser compatibility across modern browsers
|
||||
- Progressive loading for large assets
|
||||
- Touch-friendly mobile controls
|
||||
- Responsive design for different screen sizes
|
||||
|
||||
### Mobile Optimization
|
||||
|
||||
- Touch gesture support and responsive controls
|
||||
- Battery usage optimization
|
||||
- Performance scaling for different device capabilities
|
||||
- App store compliance and packaging
|
||||
|
||||
### Performance Targets
|
||||
|
||||
- **Desktop**: 60 FPS at 1080p resolution
|
||||
- **Mobile**: 60 FPS on mid-range devices, 30 FPS minimum on low-end
|
||||
- **Loading**: Initial load under 5 seconds, level transitions under 2 seconds
|
||||
@@ -2127,18 +2149,21 @@ game-project/
|
||||
## Success Metrics for Game Development
|
||||
|
||||
### Technical Metrics
|
||||
|
||||
- Frame rate consistency (>90% of time at target FPS)
|
||||
- Memory usage within budgets
|
||||
- Loading time targets met
|
||||
- Zero critical bugs in core gameplay systems
|
||||
|
||||
### Player Experience Metrics
|
||||
|
||||
- Tutorial completion rate >80%
|
||||
- Level completion rates appropriate for difficulty curve
|
||||
- Average session length meets design targets
|
||||
- Player retention and engagement metrics
|
||||
|
||||
### Development Process Metrics
|
||||
|
||||
- Story completion within estimated timeframes
|
||||
- Code quality metrics (test coverage, linting compliance)
|
||||
- Documentation completeness and accuracy
|
||||
@@ -2147,6 +2172,7 @@ game-project/
|
||||
## Common Game Development Patterns
|
||||
|
||||
### Scene Management
|
||||
|
||||
- Boot scene for initial setup and configuration
|
||||
- Preload scene for asset loading with progress feedback
|
||||
- Menu scene for navigation and settings
|
||||
@@ -2154,18 +2180,21 @@ game-project/
|
||||
- Clean transitions between scenes with proper cleanup
|
||||
|
||||
### Game State Management
|
||||
|
||||
- Persistent data (player progress, unlocks, settings)
|
||||
- Session data (current level, score, temporary state)
|
||||
- Save/load system with error recovery
|
||||
- Settings management with platform storage
|
||||
|
||||
### Input Handling
|
||||
|
||||
- Cross-platform input abstraction
|
||||
- Touch gesture support for mobile
|
||||
- Keyboard and gamepad support for desktop
|
||||
- Customizable control schemes
|
||||
|
||||
### Performance Optimization
|
||||
|
||||
- Object pooling for bullets, effects, enemies
|
||||
- Texture atlasing and sprite optimization
|
||||
- Audio compression and streaming
|
||||
|
||||
Reference in New Issue
Block a user