plan-project gone, and all level 1-3 workflows are dynamic from the workflow in suggesting what is next

This commit is contained in:
Brian Madison
2025-10-24 23:16:08 -05:00
parent f37c960a4d
commit 92bff333b1
25 changed files with 210 additions and 160 deletions

View File

@@ -226,47 +226,40 @@ Run cohesion validation? (y/n)</ask>
- **Ready for sprint planning with epic/story breakdown**
</check>
## Next Steps Checklist
## Next Steps
<action>Determine appropriate next steps for Level 0 atomic change</action>
<invoke-workflow path="{project-root}/bmad/bmm/workflows/workflow-status">
<param>mode: update</param>
<param>action: complete_workflow</param>
<param>workflow_name: tech-spec</param>
</invoke-workflow>
**Optional Next Steps:**
<check if="change involves UI components">
- [ ] **Create simple UX documentation** (if UI change is user-facing)
- Note: Full instructions-ux workflow may be overkill for Level 0
- Consider documenting just the specific UI change
<check if="success == true">
<output>Status updated!</output>
</check>
- [ ] **Generate implementation task**
- Command: `workflow task-generation`
- Uses: tech-spec.md
<output>**✅ Tech-Spec Complete, {user_name}!**
<check if="change is backend/API only">
**Deliverables Created:**
<check if="project_level == 0">
**Recommended Next Steps:**
- [ ] **Create test plan** for the change
- Unit tests for the specific change
- Integration test if affects other components
- [ ] **Generate implementation task**
- Command: `workflow task-generation`
- Uses: tech-spec.md
<ask>**✅ Tech-Spec Complete, {user_name}!**
Next action:
1. Proceed to implementation
2. Generate development task
3. Create test plan
4. Exit workflow
Select option (1-4):</ask>
- ✅ tech-spec.md - Technical specification
- ✅ user-story.md - Single user story
</check>
<check if="project_level == 1">
- ✅ tech-spec.md - Technical specification
- ✅ epics.md - Epic and story breakdown
</check>
**Next Steps:**
- **Next required:** {{next_workflow}} ({{next_agent}} agent)
- **Optional:** Create test plan or document UI changes if applicable
Check status anytime with: `workflow-status`
</output>
</step>
</workflow>