style: apply prettier and yaml formatting
Auto-formatting applied by prettier and yaml-format tools. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -27,17 +27,20 @@ For ideation and planning, use Google's Gemini with the team-fullstack configura
|
||||
### Gemini Planning Phase
|
||||
|
||||
In Gemini, ask the BMAD team to help you:
|
||||
|
||||
- **Ideate** your project concept
|
||||
- **Brainstorm** features and requirements
|
||||
- **Brainstorm** features and requirements
|
||||
- **Create a PRD** (Product Requirements Document)
|
||||
- **Design the architecture**
|
||||
|
||||
Ask questions like:
|
||||
|
||||
- "Help me brainstorm a [type of application] that does [core functionality]"
|
||||
- "Create a comprehensive PRD for this concept"
|
||||
- "Design the technical architecture for this system"
|
||||
|
||||
Copy the PRD and architecture documents that Gemini creates into your project's `docs/` folder:
|
||||
|
||||
- `docs/prd.md`
|
||||
- `docs/architecture.md`
|
||||
|
||||
@@ -51,6 +54,7 @@ Once you have your PRD and architecture documents in the `docs/` folder:
|
||||
4. **Shard the architecture**: Type `*shard-doc docs/architecture.md architecture`
|
||||
|
||||
This creates organized folders:
|
||||
|
||||
- `docs/prd/` - Contains broken down PRD sections
|
||||
- `docs/architecture/` - Contains broken down architecture sections
|
||||
|
||||
@@ -59,6 +63,7 @@ This creates organized folders:
|
||||
Now begin the iterative development cycle:
|
||||
|
||||
### Create Stories (Scrum Master)
|
||||
|
||||
1. **Start a new chat or conversation**
|
||||
2. **Switch to SM mode**: Select `bmad-sm` from the mode selector
|
||||
3. **Create story**: Type `*create` (this runs the create-next-story task)
|
||||
@@ -66,6 +71,7 @@ Now begin the iterative development cycle:
|
||||
5. **If approved**: Set story status to "Approved" in the story file
|
||||
|
||||
### Implement Stories (Developer)
|
||||
|
||||
1. **Start a new conversation**
|
||||
2. **Switch to Dev mode**: Select `bmad-dev` from the mode selector
|
||||
3. **The agent will ask which story to implement**
|
||||
@@ -73,6 +79,7 @@ Now begin the iterative development cycle:
|
||||
5. **When story is complete**: Mark status as "Done"
|
||||
|
||||
### Repeat the Cycle
|
||||
|
||||
1. **Switch to SM mode** (`bmad-sm`)
|
||||
2. **Create next story**: Type `*create`
|
||||
3. **Review and approve**
|
||||
@@ -117,7 +124,7 @@ All BMAD agents are available as custom modes:
|
||||
|
||||
- **Use mode selector effectively**: Switch modes as needed for different tasks
|
||||
- **Respect file permissions**: Agents can only edit files they have permission for
|
||||
- **Use *help command**: Every mode supports `*help` to see available commands
|
||||
- **Use \*help command**: Every mode supports `*help` to see available commands
|
||||
- **Review generated content**: Always review and approve stories before marking them ready
|
||||
- **Maintain status updates**: Keep story statuses current (Draft → Approved → InProgress → Done)
|
||||
- **Leverage Roo's context**: Modes can maintain context across the conversation
|
||||
@@ -130,4 +137,4 @@ All BMAD agents are available as custom modes:
|
||||
- **bmad-ux-expert**: `.md`, `.css`, `.scss`, `.html`, `.jsx`, `.tsx` files
|
||||
- **bmad-dev, bmad-bmad-master, bmad-orchestrator**: Full file access
|
||||
|
||||
This workflow ensures systematic, AI-assisted development following agile principles with clear handoffs between planning, story creation, and implementation phases.
|
||||
This workflow ensures systematic, AI-assisted development following agile principles with clear handoffs between planning, story creation, and implementation phases.
|
||||
|
||||
Reference in New Issue
Block a user