feat: Claude Code slash commands for Tasks and Agents!
This commit is contained in:
Brian Madison
677
dist/teams/team-all.txt
vendored
677
dist/teams/team-all.txt
vendored
File diff suppressed because it is too large
Load Diff
666
dist/teams/team-fullstack.txt
vendored
666
dist/teams/team-fullstack.txt
vendored
File diff suppressed because it is too large
Load Diff
601
dist/teams/team-ide-minimal.txt
vendored
601
dist/teams/team-ide-minimal.txt
vendored
@@ -164,7 +164,6 @@ workflow-guidance:
|
||||
- Understand each workflow's purpose, options, and decision points
|
||||
- Ask clarifying questions based on the workflow's structure
|
||||
- Guide users through workflow selection when multiple options exist
|
||||
- For complex projects, offer to create a workflow plan using create-workflow-plan task
|
||||
- When appropriate, suggest: Would you like me to create a detailed workflow plan before starting?
|
||||
- For workflows with divergent paths, help users choose the right path
|
||||
- Adapt questions to the specific domain (e.g., game dev vs infrastructure vs web dev)
|
||||
@@ -174,9 +173,7 @@ dependencies:
|
||||
tasks:
|
||||
- advanced-elicitation.md
|
||||
- create-doc.md
|
||||
- create-workflow-plan.md
|
||||
- kb-mode-interaction.md
|
||||
- update-workflow-plan.md
|
||||
data:
|
||||
- bmad-kb.md
|
||||
- elicitation-methods.md
|
||||
@@ -596,302 +593,11 @@ User can type `#yolo` to toggle to YOLO mode (process all sections at once).
|
||||
- End with "Select 1-9 or just type your question/feedback:"
|
||||
==================== END: .bmad-core/tasks/create-doc.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/create-workflow-plan.md ====================
|
||||
# Create Workflow Plan Task
|
||||
|
||||
## Purpose
|
||||
|
||||
Guide users through workflow selection and create a detailed plan document that outlines the selected workflow steps, decision points, and expected outputs. This task helps users understand what will happen before starting a complex workflow and provides a checklist to track progress.
|
||||
|
||||
## Task Instructions
|
||||
|
||||
### 1. Understand User's Goal
|
||||
|
||||
[[LLM: Start with discovery questions to understand what the user wants to accomplish]]
|
||||
|
||||
Ask the user:
|
||||
|
||||
1. **Project Type**:
|
||||
- Are you starting a new project (greenfield) or enhancing an existing one (brownfield)?
|
||||
- What type of application? (web app, service/API, UI only, full-stack)
|
||||
|
||||
2. **For Greenfield**:
|
||||
- Do you need a quick prototype or production-ready application?
|
||||
- Will this have a UI component?
|
||||
- Single service or multiple services?
|
||||
|
||||
3. **For Brownfield**:
|
||||
- What's the scope of the enhancement?
|
||||
- Single bug fix or small feature (few hours)
|
||||
- Small enhancement (1-3 stories)
|
||||
- Major feature requiring coordination
|
||||
- Architectural changes or modernization
|
||||
- Do you have existing documentation?
|
||||
- Are you following existing patterns or introducing new ones?
|
||||
|
||||
### 2. Recommend Appropriate Workflow
|
||||
|
||||
Based on the answers, recommend:
|
||||
|
||||
**Greenfield Options:**
|
||||
|
||||
- `greenfield-fullstack` - Complete web application
|
||||
- `greenfield-service` - Backend API/service only
|
||||
- `greenfield-ui` - Frontend only
|
||||
|
||||
**Brownfield Options:**
|
||||
|
||||
- `brownfield-create-story` - Single small change
|
||||
- `brownfield-create-epic` - Small feature (1-3 stories)
|
||||
- `brownfield-fullstack` - Major enhancement
|
||||
|
||||
**Simplified Option:**
|
||||
|
||||
- For users unsure or wanting flexibility, suggest starting with individual agent tasks
|
||||
|
||||
### 3. Explain Selected Workflow
|
||||
|
||||
[[LLM: Once workflow is selected, provide clear explanation]]
|
||||
|
||||
For the selected workflow, explain:
|
||||
|
||||
1. **Overview**: What this workflow accomplishes
|
||||
2. **Duration**: Estimated time for planning phase
|
||||
3. **Outputs**: What documents will be created
|
||||
4. **Decision Points**: Where user input will be needed
|
||||
5. **Requirements**: What information should be ready
|
||||
|
||||
### 4. Create Workflow Plan Document
|
||||
|
||||
[[LLM: Generate a comprehensive plan document with the following structure]]
|
||||
|
||||
```markdown
|
||||
# Workflow Plan: {{Workflow Name}}
|
||||
|
||||
<!-- WORKFLOW-PLAN-META
|
||||
workflow-id: {{workflow-id}}
|
||||
status: active
|
||||
created: {{ISO-8601 timestamp}}
|
||||
updated: {{ISO-8601 timestamp}}
|
||||
version: 1.0
|
||||
-->
|
||||
|
||||
**Created Date**: {{current date}}
|
||||
**Project**: {{project name}}
|
||||
**Type**: {{greenfield/brownfield}}
|
||||
**Status**: Active
|
||||
**Estimated Planning Duration**: {{time estimate}}
|
||||
|
||||
## Objective
|
||||
|
||||
{{Clear description of what will be accomplished}}
|
||||
|
||||
## Selected Workflow
|
||||
|
||||
**Workflow**: `{{workflow-id}}`
|
||||
**Reason**: {{Why this workflow fits the user's needs}}
|
||||
|
||||
## Workflow Steps
|
||||
|
||||
### Planning Phase
|
||||
|
||||
- [ ] Step 1: {{step name}} <!-- step-id: 1.1, agent: {{agent}}, task: {{task}} -->
|
||||
- **Agent**: {{agent name}}
|
||||
- **Action**: {{what happens}}
|
||||
- **Output**: {{what's created}}
|
||||
- **User Input**: {{if any}}
|
||||
|
||||
- [ ] Step 2: {{step name}} <!-- step-id: 1.2, agent: {{agent}}, task: {{task}} -->
|
||||
- **Agent**: {{agent name}}
|
||||
- **Action**: {{what happens}}
|
||||
- **Output**: {{what's created}}
|
||||
- **Decision Point**: {{if any}} <!-- decision-id: D1 -->
|
||||
|
||||
{{Continue for all planning steps}}
|
||||
|
||||
### Development Phase (IDE)
|
||||
|
||||
- [ ] Document Sharding <!-- step-id: 2.1, agent: po, task: shard-doc -->
|
||||
- Prepare documents for story creation
|
||||
|
||||
- [ ] Story Development Cycle <!-- step-id: 2.2, repeats: true -->
|
||||
- [ ] Create story (SM agent) <!-- step-id: 2.2.1, agent: sm, task: create-next-story -->
|
||||
- [ ] Review story (optional) <!-- step-id: 2.2.2, agent: analyst, optional: true -->
|
||||
- [ ] Implement story (Dev agent) <!-- step-id: 2.2.3, agent: dev -->
|
||||
- [ ] QA review (optional) <!-- step-id: 2.2.4, agent: qa, optional: true -->
|
||||
- [ ] Repeat for all stories
|
||||
|
||||
- [ ] Epic Retrospective (optional) <!-- step-id: 2.3, agent: po, optional: true -->
|
||||
|
||||
## Key Decision Points
|
||||
|
||||
1. **{{Decision Name}}** (Step {{n}}): <!-- decision-id: D1, status: pending -->
|
||||
- Trigger: {{what causes this decision}}
|
||||
- Options: {{available choices}}
|
||||
- Impact: {{how it affects the workflow}}
|
||||
- Decision Made: _Pending_
|
||||
|
||||
{{List all decision points}}
|
||||
|
||||
## Expected Outputs
|
||||
|
||||
### Planning Documents
|
||||
- [ ] {{document 1}} - {{description}}
|
||||
- [ ] {{document 2}} - {{description}}
|
||||
{{etc...}}
|
||||
|
||||
### Development Artifacts
|
||||
- [ ] Stories in `docs/stories/`
|
||||
- [ ] Implementation code
|
||||
- [ ] Tests
|
||||
- [ ] Updated documentation
|
||||
|
||||
## Prerequisites Checklist
|
||||
|
||||
Before starting this workflow, ensure you have:
|
||||
|
||||
- [ ] {{prerequisite 1}}
|
||||
- [ ] {{prerequisite 2}}
|
||||
- [ ] {{prerequisite 3}}
|
||||
{{etc...}}
|
||||
|
||||
## Customization Options
|
||||
|
||||
Based on your project needs, you may:
|
||||
- Skip {{optional step}} if {{condition}}
|
||||
- Add {{additional step}} if {{condition}}
|
||||
- Choose {{alternative}} instead of {{default}}
|
||||
|
||||
## Risk Considerations
|
||||
|
||||
{{For brownfield only}}
|
||||
- Integration complexity: {{assessment}}
|
||||
- Rollback strategy: {{approach}}
|
||||
- Testing requirements: {{special needs}}
|
||||
|
||||
## Next Steps
|
||||
|
||||
1. Review this plan and confirm it matches your expectations
|
||||
2. Gather any missing prerequisites
|
||||
3. Start workflow with: `*task workflow {{workflow-id}}`
|
||||
4. Or begin with first agent: `@{{first-agent}}`
|
||||
|
||||
## Notes
|
||||
|
||||
{{Any additional context or warnings}}
|
||||
|
||||
---
|
||||
*This plan can be updated as you progress through the workflow. Check off completed items to track progress.*
|
||||
```
|
||||
|
||||
### 5. Save and Present Plan
|
||||
|
||||
1. Save the plan as `docs/workflow-plan.md`
|
||||
2. Inform user: "Workflow plan created at docs/workflow-plan.md"
|
||||
3. Offer options:
|
||||
- Review the plan together
|
||||
- Start the workflow now
|
||||
- Gather prerequisites first
|
||||
- Modify the plan
|
||||
|
||||
### 6. Plan Variations
|
||||
|
||||
[[LLM: Adjust plan detail based on workflow complexity]]
|
||||
|
||||
**For Simple Workflows** (create-story, create-epic):
|
||||
|
||||
- Simpler checklist format
|
||||
- Focus on immediate next steps
|
||||
- Less detailed explanations
|
||||
|
||||
**For Complex Workflows** (full greenfield/brownfield):
|
||||
|
||||
- Detailed step breakdowns
|
||||
- All decision points documented
|
||||
- Comprehensive output descriptions
|
||||
- Risk mitigation sections
|
||||
|
||||
**For Brownfield Workflows**:
|
||||
|
||||
- Include existing system impact analysis
|
||||
- Document integration checkpoints
|
||||
- Add rollback considerations
|
||||
- Note documentation dependencies
|
||||
|
||||
### 7. Interactive Planning Mode
|
||||
|
||||
[[LLM: If user wants to customize the workflow]]
|
||||
|
||||
If user wants to modify the standard workflow:
|
||||
|
||||
1. Present workflow steps as options
|
||||
2. Allow skipping optional steps
|
||||
3. Let user reorder certain steps
|
||||
4. Document customizations in plan
|
||||
5. Warn about dependencies if steps are skipped
|
||||
|
||||
### 8. Execution Guidance
|
||||
|
||||
After plan is created, provide clear guidance:
|
||||
|
||||
```text
|
||||
Your workflow plan is ready! Here's how to proceed:
|
||||
|
||||
1. **Review the plan**: Check that all steps align with your goals
|
||||
2. **Gather prerequisites**: Use the checklist to ensure you're ready
|
||||
3. **Start execution**:
|
||||
- Full workflow: `*task workflow {{workflow-id}}`
|
||||
- Step by step: Start with `@{{first-agent}}`
|
||||
4. **Track progress**: Check off steps in the plan as completed
|
||||
|
||||
Would you like to:
|
||||
a) Review the plan together
|
||||
b) Start the workflow now
|
||||
c) Gather prerequisites first
|
||||
d) Modify the plan
|
||||
```
|
||||
|
||||
## Success Criteria
|
||||
|
||||
The workflow plan is successful when:
|
||||
|
||||
1. User clearly understands what will happen
|
||||
2. All decision points are documented
|
||||
3. Prerequisites are identified
|
||||
4. Expected outputs are clear
|
||||
5. User feels confident to proceed
|
||||
6. Plan serves as useful progress tracker
|
||||
|
||||
## Integration with BMad Master and Orchestrator
|
||||
|
||||
When used by BMad Master or BMad Orchestrator, this task should:
|
||||
|
||||
1. Be offered when user asks about workflows
|
||||
2. Be suggested before starting complex workflows
|
||||
3. Create a plan that the agent can reference during execution
|
||||
4. Allow the agent to track progress against the plan
|
||||
|
||||
## Example Usage
|
||||
|
||||
```text
|
||||
User: "I need to add a payment system to my existing app"
|
||||
|
||||
BMad Orchestrator: "Let me help you create a workflow plan for that enhancement. I'll ask a few questions to recommend the best approach..."
|
||||
|
||||
[Runs through discovery questions]
|
||||
|
||||
BMad Orchestrator: "Based on your answers, I recommend the brownfield-fullstack workflow. Let me create a detailed plan for you..."
|
||||
|
||||
[Creates and saves plan]
|
||||
|
||||
BMad Orchestrator: "I've created a workflow plan at docs/workflow-plan.md. This shows all the steps we'll go through, what documents will be created, and where you'll need to make decisions. Would you like to review it together?"
|
||||
```
|
||||
==================== END: .bmad-core/tasks/create-workflow-plan.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/kb-mode-interaction.md ====================
|
||||
# KB Mode Interaction Task
|
||||
|
||||
## Purpose
|
||||
|
||||
Provide a user-friendly interface to the BMad knowledge base without overwhelming users with information upfront.
|
||||
|
||||
## Instructions
|
||||
@@ -899,11 +605,11 @@ Provide a user-friendly interface to the BMad knowledge base without overwhelmin
|
||||
When entering KB mode (*kb-mode), follow these steps:
|
||||
|
||||
### 1. Welcome and Guide
|
||||
Announce entering KB mode with a brief, friendly introduction:
|
||||
|
||||
"I've entered KB mode and have access to the full BMad knowledge base. I can help you with detailed information about any aspect of BMad-Method."
|
||||
Announce entering KB mode with a brief, friendly introduction.
|
||||
|
||||
### 2. Present Topic Areas
|
||||
|
||||
Offer a concise list of main topic areas the user might want to explore:
|
||||
|
||||
**What would you like to know more about?**
|
||||
@@ -920,19 +626,23 @@ Offer a concise list of main topic areas the user might want to explore:
|
||||
Or ask me about anything else related to BMad-Method!
|
||||
|
||||
### 3. Respond Contextually
|
||||
|
||||
- Wait for user's specific question or topic selection
|
||||
- Provide focused, relevant information from the knowledge base
|
||||
- Offer to dive deeper or explore related topics
|
||||
- Keep responses concise unless user asks for detailed explanations
|
||||
|
||||
### 4. Interactive Exploration
|
||||
|
||||
- After answering, suggest related topics they might find helpful
|
||||
- Maintain conversational flow rather than data dumping
|
||||
- Use examples when appropriate
|
||||
- Reference specific documentation sections when relevant
|
||||
|
||||
### 5. Exit Gracefully
|
||||
|
||||
When user is done or wants to exit KB mode:
|
||||
|
||||
- Summarize key points discussed if helpful
|
||||
- Remind them they can return to KB mode anytime with *kb-mode
|
||||
- Suggest next steps based on what was discussed
|
||||
@@ -961,257 +671,6 @@ Or ask me about anything else related to BMad-Method!
|
||||
**Assistant**: [Provides focused information about workflows from the KB, then offers to explore specific workflow types or related topics]
|
||||
==================== END: .bmad-core/tasks/kb-mode-interaction.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/update-workflow-plan.md ====================
|
||||
# Update Workflow Plan Task
|
||||
|
||||
## Purpose
|
||||
|
||||
Update the status of steps in an active workflow plan, mark completions, add notes about deviations, and maintain an accurate record of workflow progress. This task can be called directly by users or automatically by other tasks upon completion.
|
||||
|
||||
## Task Instructions
|
||||
|
||||
### 0. Load Plan Configuration
|
||||
|
||||
[[LLM: First load core-config.yaml to get plan settings]]
|
||||
|
||||
Check workflow configuration:
|
||||
|
||||
- `workflow.planFile` - Location of the plan (default: docs/workflow-plan.md)
|
||||
- `workflow.trackProgress` - Whether tracking is enabled
|
||||
- `workflow.updateOnCompletion` - Whether to auto-update on task completion
|
||||
|
||||
If tracking is disabled, inform user and exit.
|
||||
|
||||
### 1. Verify Plan Exists
|
||||
|
||||
[[LLM: Check if workflow plan exists at configured location]]
|
||||
|
||||
If no plan exists:
|
||||
|
||||
```
|
||||
No active workflow plan found at {location}.
|
||||
Would you like to create one? Use *plan command.
|
||||
```
|
||||
|
||||
### 2. Determine Update Type
|
||||
|
||||
[[LLM: Ask user what type of update they want to make]]
|
||||
|
||||
Present options:
|
||||
|
||||
```
|
||||
What would you like to update in the workflow plan?
|
||||
|
||||
1. Mark step as complete
|
||||
2. Update current step
|
||||
3. Add deviation note
|
||||
4. Mark decision point resolution
|
||||
5. Update overall status
|
||||
6. View current plan status only
|
||||
|
||||
Please select an option (1-6):
|
||||
```
|
||||
|
||||
### 3. Parse Current Plan
|
||||
|
||||
[[LLM: Read and parse the plan to understand current state]]
|
||||
|
||||
Extract:
|
||||
|
||||
- All steps with their checkbox status
|
||||
- Step IDs from comments (if present)
|
||||
- Current completion percentage
|
||||
- Any existing deviation notes
|
||||
- Decision points and their status
|
||||
|
||||
### 4. Execute Updates
|
||||
|
||||
#### 4.1 Mark Step Complete
|
||||
|
||||
If user selected option 1:
|
||||
|
||||
1. Show numbered list of incomplete steps
|
||||
2. Ask which step to mark complete
|
||||
3. Update the checkbox from `[ ]` to `[x]`
|
||||
4. Add completion timestamp: `<!-- completed: YYYY-MM-DD HH:MM -->`
|
||||
5. If this was the current step, identify next step
|
||||
|
||||
#### 4.2 Update Current Step
|
||||
|
||||
If user selected option 2:
|
||||
|
||||
1. Show all steps with current status
|
||||
2. Ask which step is now current
|
||||
3. Add/move `<!-- current-step -->` marker
|
||||
4. Optionally add note about why sequence changed
|
||||
|
||||
#### 4.3 Add Deviation Note
|
||||
|
||||
If user selected option 3:
|
||||
|
||||
1. Ask for deviation description
|
||||
2. Ask which step this relates to (or general)
|
||||
3. Insert note in appropriate location:
|
||||
|
||||
```markdown
|
||||
> **Deviation Note** (YYYY-MM-DD): {user_note}
|
||||
> Related to: Step X.Y or General workflow
|
||||
```
|
||||
|
||||
#### 4.4 Mark Decision Resolution
|
||||
|
||||
If user selected option 4:
|
||||
|
||||
1. Show pending decision points
|
||||
2. Ask which decision was made
|
||||
3. Record the decision and chosen path
|
||||
4. Update related steps based on decision
|
||||
|
||||
#### 4.5 Update Overall Status
|
||||
|
||||
If user selected option 5:
|
||||
|
||||
1. Show current overall status
|
||||
2. Provide options:
|
||||
- Active (continuing with plan)
|
||||
- Paused (temporarily stopped)
|
||||
- Abandoned (no longer following)
|
||||
- Complete (all steps done)
|
||||
3. Update plan header with new status
|
||||
|
||||
### 5. Automatic Updates (When Called by Tasks)
|
||||
|
||||
[[LLM: When called automatically by another task]]
|
||||
|
||||
If called with parameters:
|
||||
|
||||
```
|
||||
task: {task_name}
|
||||
step_id: {step_identifier}
|
||||
status: complete|skipped|failed
|
||||
note: {optional_note}
|
||||
```
|
||||
|
||||
Automatically:
|
||||
|
||||
1. Find the corresponding step
|
||||
2. Update its status
|
||||
3. Add completion metadata
|
||||
4. Add note if provided
|
||||
5. Calculate new progress percentage
|
||||
|
||||
### 6. Generate Update Summary
|
||||
|
||||
After updates, show summary:
|
||||
|
||||
```
|
||||
✅ Workflow Plan Updated
|
||||
|
||||
Changes made:
|
||||
- {change_1}
|
||||
- {change_2}
|
||||
|
||||
New Status:
|
||||
- Progress: {X}% complete ({completed}/{total} steps)
|
||||
- Current Step: {current_step}
|
||||
- Next Recommended: {next_step}
|
||||
|
||||
Plan location: {file_path}
|
||||
```
|
||||
|
||||
### 7. Integration with Other Tasks
|
||||
|
||||
[[LLM: How other tasks should call this]]
|
||||
|
||||
Other tasks can integrate by:
|
||||
|
||||
1. **After Task Completion**:
|
||||
|
||||
```
|
||||
At end of task execution:
|
||||
- Check if task corresponds to a plan step
|
||||
- If yes, call update-workflow-plan with:
|
||||
- task: {current_task_name}
|
||||
- step_id: {matching_step}
|
||||
- status: complete
|
||||
```
|
||||
|
||||
2. **On Task Failure**:
|
||||
|
||||
```
|
||||
If task fails:
|
||||
- Call update-workflow-plan with:
|
||||
- task: {current_task_name}
|
||||
- status: failed
|
||||
- note: {failure_reason}
|
||||
```
|
||||
|
||||
### 8. Plan Status Display
|
||||
|
||||
[[LLM: When user selects view status only]]
|
||||
|
||||
Display comprehensive status:
|
||||
|
||||
```markdown
|
||||
📋 Workflow Plan Status
|
||||
━━━━━━━━━━━━━━━━━━━━
|
||||
Workflow: {workflow_name}
|
||||
Status: {Active|Paused|Complete}
|
||||
Progress: {X}% complete ({completed}/{total} steps)
|
||||
Last Updated: {timestamp}
|
||||
|
||||
✅ Completed Steps:
|
||||
- [x] Step 1.1: {description} (completed: {date})
|
||||
- [x] Step 1.2: {description} (completed: {date})
|
||||
|
||||
🔄 Current Step:
|
||||
- [ ] Step 2.1: {description} <!-- current-step -->
|
||||
Agent: {agent_name}
|
||||
Task: {task_name}
|
||||
|
||||
📌 Upcoming Steps:
|
||||
- [ ] Step 2.2: {description}
|
||||
- [ ] Step 3.1: {description}
|
||||
|
||||
⚠️ Deviations/Notes:
|
||||
{any_deviation_notes}
|
||||
|
||||
📊 Decision Points:
|
||||
- Decision 1: {status} - {choice_made}
|
||||
- Decision 2: Pending
|
||||
|
||||
💡 Next Action:
|
||||
Based on the plan, you should {recommended_action}
|
||||
```
|
||||
|
||||
## Success Criteria
|
||||
|
||||
The update is successful when:
|
||||
|
||||
1. Plan accurately reflects current workflow state
|
||||
2. All updates are clearly timestamped
|
||||
3. Deviations are documented with reasons
|
||||
4. Progress calculation is correct
|
||||
5. Next steps are clear to user
|
||||
6. Plan remains readable and well-formatted
|
||||
|
||||
## Error Handling
|
||||
|
||||
- **Plan file not found**: Offer to create new plan
|
||||
- **Malformed plan**: Attempt basic updates, warn user
|
||||
- **Write permission error**: Show changes that would be made
|
||||
- **Step not found**: Show available steps, ask for clarification
|
||||
- **Concurrent updates**: Implement simple locking or warn about conflicts
|
||||
|
||||
## Notes
|
||||
|
||||
- Always preserve plan history (don't delete old information)
|
||||
- Keep updates atomic to prevent corruption
|
||||
- Consider creating backup before major updates
|
||||
- Updates should enhance, not complicate, the workflow experience
|
||||
- If plan becomes too cluttered, suggest creating fresh plan for next phase
|
||||
==================== END: .bmad-core/tasks/update-workflow-plan.md ====================
|
||||
|
||||
==================== START: .bmad-core/data/bmad-kb.md ====================
|
||||
# BMad Knowledge Base
|
||||
|
||||
@@ -2334,20 +1793,20 @@ The LLM will:
|
||||
|
||||
## Primary Method: Automatic with markdown-tree
|
||||
|
||||
[[LLM: First, check if markdownExploder is set to true in bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
|
||||
[[LLM: First, check if markdownExploder is set to true in .bmad-core/core-config.yaml. If it is, attempt to run the command: `md-tree explode {input file} {output path}`.
|
||||
|
||||
If the command succeeds, inform the user that the document has been sharded successfully and STOP - do not proceed further.
|
||||
|
||||
If the command fails (especially with an error indicating the command is not found or not available), inform the user: "The markdownExploder setting is enabled but the md-tree command is not available. Please either:
|
||||
|
||||
1. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
|
||||
2. Or set markdownExploder to false in bmad-core/core-config.yaml
|
||||
2. Or set markdownExploder to false in .bmad-core/core-config.yaml
|
||||
|
||||
**IMPORTANT: STOP HERE - do not proceed with manual sharding until one of the above actions is taken.**"
|
||||
|
||||
If markdownExploder is set to false, inform the user: "The markdownExploder setting is currently false. For better performance and reliability, you should:
|
||||
|
||||
1. Set markdownExploder to true in bmad-core/core-config.yaml
|
||||
1. Set markdownExploder to true in .bmad-core/core-config.yaml
|
||||
2. Install @kayvan/markdown-tree-parser globally with: `npm install -g @kayvan/markdown-tree-parser`
|
||||
|
||||
I will now proceed with the manual sharding process."
|
||||
@@ -2387,8 +1846,6 @@ If the user has @kayvan/markdown-tree-parser installed, use it and skip the manu
|
||||
|
||||
## Manual Method (if @kayvan/markdown-tree-parser is not available or user indicated manual method)
|
||||
|
||||
[[LLM: Only proceed with the manual instructions below if the user cannot or does not want to use @kayvan/markdown-tree-parser.]]
|
||||
|
||||
### Task Instructions
|
||||
|
||||
1. Identify Document and Target Location
|
||||
@@ -2399,7 +1856,7 @@ If the user has @kayvan/markdown-tree-parser installed, use it and skip the manu
|
||||
|
||||
2. Parse and Extract Sections
|
||||
|
||||
[[LLM: When sharding the document:
|
||||
CRITICAL AEGNT SHARDING RULES:
|
||||
|
||||
1. Read the entire document content
|
||||
2. Identify all level 2 sections (## headings)
|
||||
@@ -2460,8 +1917,6 @@ Create an `index.md` file in the sharded folder that:
|
||||
|
||||
### 5. Preserve Special Content
|
||||
|
||||
[[LLM: Pay special attention to preserving:
|
||||
|
||||
1. **Code blocks**: Must capture complete blocks including:
|
||||
|
||||
```language
|
||||
@@ -2483,7 +1938,7 @@ Create an `index.md` file in the sharded folder that:
|
||||
|
||||
6. **Links and references**: Keep all markdown links intact
|
||||
|
||||
7. **Template markup**: If documents contain {{placeholders}} or [[LLM instructions]], preserve exactly]]
|
||||
7. **Template markup**: If documents contain {{placeholders}} ,preserve exactly
|
||||
|
||||
### 6. Validation
|
||||
|
||||
@@ -2522,9 +1977,9 @@ Document sharded successfully:
|
||||
|
||||
## Purpose
|
||||
|
||||
- Guide a structured response to a change trigger using the `change-checklist`.
|
||||
- Guide a structured response to a change trigger using the `.bmad-core/checklists/change-checklist`.
|
||||
- Analyze the impacts of the change on epics, project artifacts, and the MVP, guided by the checklist's structure.
|
||||
- Explore potential solutions (e.g., adjust scope, rollback elements, rescope features) as prompted by the checklist.
|
||||
- Explore potential solutions (e.g., adjust scope, rollback elements, re-scope features) as prompted by the checklist.
|
||||
- Draft specific, actionable proposed updates to any affected project artifacts (e.g., epics, user stories, PRD sections, architecture document sections) based on the analysis.
|
||||
- Produce a consolidated "Sprint Change Proposal" document that contains the impact analysis and the clearly drafted proposed edits for user review and approval.
|
||||
- Ensure a clear handoff path if the nature of the changes necessitates fundamental replanning by other core agents (like PM or Architect).
|
||||
@@ -2536,19 +1991,16 @@ Document sharded successfully:
|
||||
- **Acknowledge Task & Inputs:**
|
||||
- Confirm with the user that the "Correct Course Task" (Change Navigation & Integration) is being initiated.
|
||||
- Verify the change trigger and ensure you have the user's initial explanation of the issue and its perceived impact.
|
||||
- Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `change-checklist` (e.g., `change-checklist`).
|
||||
- Confirm access to all relevant project artifacts (e.g., PRD, Epics/Stories, Architecture Documents, UI/UX Specifications) and, critically, the `.bmad-core/checklists/change-checklist`.
|
||||
- **Establish Interaction Mode:**
|
||||
- Ask the user their preferred interaction mode for this task:
|
||||
- **"Incrementally (Default & Recommended):** Shall we work through the `change-checklist` section by section, discussing findings and collaboratively drafting proposed changes for each relevant part before moving to the next? This allows for detailed, step-by-step refinement."
|
||||
- **"Incrementally (Default & Recommended):** Shall we work through the change-checklist section by section, discussing findings and collaboratively drafting proposed changes for each relevant part before moving to the next? This allows for detailed, step-by-step refinement."
|
||||
- **"YOLO Mode (Batch Processing):** Or, would you prefer I conduct a more batched analysis based on the checklist and then present a consolidated set of findings and proposed changes for a broader review? This can be quicker for initial assessment but might require more extensive review of the combined proposals."
|
||||
- Request the user to select their preferred mode.
|
||||
- Once the user chooses, confirm the selected mode (e.g., "Okay, we will proceed in Incremental mode."). This chosen mode will govern how subsequent steps in this task are executed.
|
||||
- **Explain Process:** Briefly inform the user: "We will now use the `change-checklist` to analyze the change and draft proposed updates. I will guide you through the checklist items based on our chosen interaction mode."
|
||||
<rule>When asking multiple questions or presenting multiple points for user input at once, number them clearly (e.g., 1., 2a., 2b.) to make it easier for the user to provide specific responses.</rule>
|
||||
- Once the user chooses, confirm the selected mode and then inform the user: "We will now use the change-checklist to analyze the change and draft proposed updates. I will guide you through the checklist items based on our chosen interaction mode."
|
||||
|
||||
### 2. Execute Checklist Analysis (Iteratively or Batched, per Interaction Mode)
|
||||
|
||||
- Systematically work through Sections 1-4 of the `change-checklist` (typically covering Change Context, Epic/Story Impact Analysis, Artifact Conflict Resolution, and Path Evaluation/Recommendation).
|
||||
- Systematically work through Sections 1-4 of the change-checklist (typically covering Change Context, Epic/Story Impact Analysis, Artifact Conflict Resolution, and Path Evaluation/Recommendation).
|
||||
- For each checklist item or logical group of items (depending on interaction mode):
|
||||
- Present the relevant prompt(s) or considerations from the checklist to the user.
|
||||
- Request necessary information and actively analyze the relevant project artifacts (PRD, epics, architecture documents, story history, etc.) to assess the impact.
|
||||
@@ -2571,7 +2023,7 @@ Document sharded successfully:
|
||||
|
||||
### 4. Generate "Sprint Change Proposal" with Edits
|
||||
|
||||
- Synthesize the complete `change-checklist` analysis (covering findings from Sections 1-4) and all the agreed-upon proposed edits (from Instruction 3) into a single document titled "Sprint Change Proposal." This proposal should align with the structure suggested by Section 5 of the `change-checklist` (Proposal Components).
|
||||
- Synthesize the complete change-checklist analysis (covering findings from Sections 1-4) and all the agreed-upon proposed edits (from Instruction 3) into a single document titled "Sprint Change Proposal." This proposal should align with the structure suggested by Section 5 of the change-checklist.
|
||||
- The proposal must clearly present:
|
||||
- **Analysis Summary:** A concise overview of the original issue, its analyzed impact (on epics, artifacts, MVP scope), and the rationale for the chosen path forward.
|
||||
- **Specific Proposed Edits:** For each affected artifact, clearly show or describe the exact changes (e.g., "Change Story X.Y from: [old text] To: [new text]", "Add new Acceptance Criterion to Story A.B: [new AC]", "Update Section 3.2 of Architecture Document as follows: [new/modified text or diagram description]").
|
||||
@@ -2588,9 +2040,9 @@ Document sharded successfully:
|
||||
## Output Deliverables
|
||||
|
||||
- **Primary:** A "Sprint Change Proposal" document (in markdown format). This document will contain:
|
||||
- A summary of the `change-checklist` analysis (issue, impact, rationale for the chosen path).
|
||||
- A summary of the change-checklist analysis (issue, impact, rationale for the chosen path).
|
||||
- Specific, clearly drafted proposed edits for all affected project artifacts.
|
||||
- **Implicit:** An annotated `change-checklist` (or the record of its completion) reflecting the discussions, findings, and decisions made during the process.
|
||||
- **Implicit:** An annotated change-checklist (or the record of its completion) reflecting the discussions, findings, and decisions made during the process.
|
||||
==================== END: .bmad-core/tasks/correct-course.md ====================
|
||||
|
||||
==================== START: .bmad-core/tasks/brownfield-create-epic.md ====================
|
||||
@@ -3917,15 +3369,14 @@ ALWAYS cite source documents: `[Source: architecture/{filename}.md#{section}]`
|
||||
- Verify all source references are included for technical details
|
||||
- Ensure tasks align with both epic requirements and architecture constraints
|
||||
- Update status to "Draft" and save the story file
|
||||
- If `workflow.trackProgress: true` and `workflow.updateOnCompletion: true`, call update-workflow-plan task to mark story creation step complete
|
||||
- Execute `tasks/execute-checklist` `checklists/story-draft-checklist`
|
||||
- Execute `.bmad-core/tasks/execute-checklist` `.bmad-core/checklists/story-draft-checklist`
|
||||
- Provide summary to user including:
|
||||
- Story created: `{devStoryLocation}/{epicNum}.{storyNum}.story.md`
|
||||
- Status: Draft
|
||||
- Key technical components included from architecture docs
|
||||
- Any deviations or conflicts noted between epic and architecture
|
||||
- Checklist Results
|
||||
- Next steps: For Complex stories, suggest the user carefully review the story draft and also optionally have the PO run the task `validate-next-story`
|
||||
- Next steps: For Complex stories, suggest the user carefully review the story draft and also optionally have the PO run the task `.bmad-core/tasks/validate-next-story`
|
||||
==================== END: .bmad-core/tasks/create-next-story.md ====================
|
||||
|
||||
==================== START: .bmad-core/checklists/story-draft-checklist.md ====================
|
||||
@@ -4194,9 +3645,7 @@ Be honest - it's better to flag issues now than have them discovered later.]]
|
||||
==================== START: .bmad-core/tasks/review-story.md ====================
|
||||
# review-story
|
||||
|
||||
When a developer marks a story as "Ready for Review", perform a comprehensive senior developer code review with the ability to refactor and improve code directly.
|
||||
|
||||
[[LLM: QA Agent executing review-story task as Senior Developer]]
|
||||
When a developer agent marks a story as "Ready for Review", perform a comprehensive senior developer code review with the ability to refactor and improve code directly.
|
||||
|
||||
## Prerequisites
|
||||
|
||||
@@ -4325,6 +3774,7 @@ After review and any refactoring, append your results to the story file in the Q
|
||||
## Blocking Conditions
|
||||
|
||||
Stop the review and request clarification if:
|
||||
|
||||
- Story file is incomplete or missing critical sections
|
||||
- File List is empty or clearly incomplete
|
||||
- No tests exist when they were required
|
||||
@@ -4334,6 +3784,7 @@ Stop the review and request clarification if:
|
||||
## Completion
|
||||
|
||||
After review:
|
||||
|
||||
1. If all items are checked and approved: Update story status to "Done"
|
||||
2. If unchecked items remain: Keep status as "Review" for dev to address
|
||||
3. Always provide constructive feedback and explanations for learning
|
||||
|
||||
664
dist/teams/team-no-ui.txt
vendored
664
dist/teams/team-no-ui.txt
vendored
File diff suppressed because it is too large
Load Diff
Reference in New Issue
Block a user