mirror of
https://github.com/bmadcode/BMAD-METHOD.git
synced 2025-12-17 09:45:25 +00:00
Merge pull request #1109 from alexeyv/fix/normalize-dev-story-trigger
fix(bmm): normalize dev-story trigger naming
This commit is contained in:
commit
572074d2a6
@ -16,7 +16,7 @@ agent:
|
||||
- 60fps is non-negotiable. Write code designers can iterate without fear. Ship early, ship often, iterate on player feedback.
|
||||
|
||||
menu:
|
||||
- trigger: develop-story
|
||||
- trigger: dev-story
|
||||
workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
|
||||
workflow-install: "{project-root}/.bmad/bmgd/workflows/4-production/dev-story/workflow.yaml"
|
||||
description: "Execute Dev Story workflow, implementing tasks and tests, or performing updates to the story"
|
||||
|
||||
@ -35,7 +35,7 @@ agent:
|
||||
- "NEVER lie about tests being written or passing - tests must actually exist and pass 100%"
|
||||
|
||||
menu:
|
||||
- trigger: develop-story
|
||||
- trigger: dev-story
|
||||
workflow: "{project-root}/.bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
|
||||
description: "Execute Dev Story workflow (full BMM path with sprint-status)"
|
||||
|
||||
|
||||
@ -214,7 +214,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
|
||||
**Workflows:**
|
||||
|
||||
- `workflow-status` - Check what to do next
|
||||
- `develop-story` - Implement story with:
|
||||
- `dev-story` - Implement story with:
|
||||
- Task-by-task iteration
|
||||
- Test-driven development
|
||||
- Multi-run capability (initial + fixes)
|
||||
@ -451,7 +451,7 @@ The BMad Method Module (BMM) provides a comprehensive team of specialized AI age
|
||||
**Workflows:**
|
||||
|
||||
- `workflow-status` - Check what to do next
|
||||
- `develop-story` - Execute Dev Story workflow, implementing tasks and tests
|
||||
- `dev-story` - Execute Dev Story workflow, implementing tasks and tests
|
||||
- `code-review` - Perform thorough clean context QA code review on a story
|
||||
|
||||
**Communication Style:** Direct and energetic. Execution-focused. Breaks down complex game challenges into actionable steps. Celebrates performance wins.
|
||||
@ -902,7 +902,7 @@ Load the customized agent and verify the changes are reflected in its behavior a
|
||||
|
||||
```
|
||||
1. SM: *create-story
|
||||
2. DEV: *develop-story
|
||||
2. DEV: *dev-story
|
||||
3. DEV: *code-review
|
||||
4. Repeat steps 1-3 for next story
|
||||
```
|
||||
@ -912,7 +912,7 @@ Load the customized agent and verify the changes are reflected in its behavior a
|
||||
```
|
||||
1. TEA: *framework (once per project, early)
|
||||
2. TEA: *atdd (before implementing features)
|
||||
3. DEV: *develop-story (includes tests)
|
||||
3. DEV: *dev-story (includes tests)
|
||||
4. TEA: *automate (comprehensive test suite)
|
||||
5. TEA: *trace (quality gate)
|
||||
6. TEA: *ci (pipeline setup)
|
||||
@ -977,12 +977,12 @@ Quick reference for agent selection:
|
||||
| **UX Designer** | 🎨 | 2 (Planning) | create-ux-design, validate-design | UX-heavy projects, design |
|
||||
| **Architect** | 🏗️ | 3 (Solutioning) | architecture, implementation-readiness | Technical design, architecture |
|
||||
| **SM** | 🏃 | 4 (Implementation) | sprint-planning, create-story | Story management, sprint coordination |
|
||||
| **DEV** | 💻 | 4 (Implementation) | develop-story, code-review | Implementation, coding |
|
||||
| **DEV** | 💻 | 4 (Implementation) | dev-story, code-review | Implementation, coding |
|
||||
| **TEA** | 🧪 | All Phases | framework, atdd, automate, trace, ci | Testing, quality assurance |
|
||||
| **Paige (Tech Writer)** | 📚 | All Phases | document-project, diagrams, validation | Documentation, diagrams |
|
||||
| **Principal Engineer** | ⚡ | Quick Flow (All phases) | create-tech-spec, quick-dev, code-review | Rapid development, technical leadership |
|
||||
| **Game Designer** | 🎲 | 1-2 (Games) | brainstorm-game, gdd, narrative | Game design, creative vision |
|
||||
| **Game Developer** | 🕹️ | 4 (Games) | develop-story, code-review | Game implementation |
|
||||
| **Game Developer** | 🕹️ | 4 (Games) | dev-story, code-review | Game implementation |
|
||||
| **Game Architect** | 🏛️ | 3 (Games) | architecture, implementation-readiness | Game systems architecture |
|
||||
| **BMad Master** | 🧙 | Meta | party-mode, list tasks/workflows | Orchestration, multi-agent |
|
||||
|
||||
@ -1072,7 +1072,7 @@ Quick reference for agent selection:
|
||||
|
||||
- [ ] SM: `*sprint-planning` (once)
|
||||
- [ ] SM: `*create-story`
|
||||
- [ ] DEV: `*develop-story`
|
||||
- [ ] DEV: `*dev-story`
|
||||
- [ ] DEV: `*code-review`
|
||||
|
||||
**Testing Strategy:**
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user