External/BMAD-METHOD
1
0
Fork 0
mirror of https://github.com/bmadcode/BMAD-METHOD.git synced 2025-12-29 16:14:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix quick udpate status bug in installer

Browse Source
This commit is contained in:
Brian Madison
2025-11-04 21:16:52 -06:00
parent c283344a54
commit 7552ee2e3b
74 changed files with 861 additions and 4448 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
.claude/commands/bmad/bmm/workflows/README.md
View File

@@ -35,9 +35,9 @@
**prd**
- Path: `bmad/bmm/workflows/2-plan-workflows/prd/workflow.yaml`
- Unified PRD workflow for project levels 2-4. Produces strategic PRD and tactical epic breakdown. Hands off to architecture workflow for technical design. Note: Level 0-1 use tech-spec workflow.
- Unified PRD workflow for BMad Method and Enterprise Method tracks. Produces strategic PRD and tactical epic breakdown. Hands off to architecture workflow for technical design. Note: Quick Flow track uses tech-spec workflow.
**tech-spec-sm**
**tech-spec**
- Path: `bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml`
- Technical specification workflow for Level 0 projects (single atomic changes). Creates focused tech spec for bug fixes, single endpoint additions, or small isolated changes. Tech-spec only - no PRD needed.

2
.claude/commands/bmad/bmm/workflows/prd.md
View File

@@ -1,5 +1,5 @@
---
description: 'Unified PRD workflow for project levels 2-4. Produces strategic PRD and tactical epic breakdown. Hands off to architecture workflow for technical design. Note: Level 0-1 use tech-spec workflow.'
description: 'Unified PRD workflow for BMad Method and Enterprise Method tracks. Produces strategic PRD and tactical epic breakdown. Hands off to architecture workflow for technical design. Note: Quick Flow track uses tech-spec workflow.'
---
# prd

15
.claude/commands/bmad/bmm/workflows/tech-spec-sm.md
View File

@@ -1,15 +0,0 @@
---
description: 'Technical specification workflow for Level 0 projects (single atomic changes). Creates focused tech spec for bug fixes, single endpoint additions, or small isolated changes. Tech-spec only - no PRD needed.'
---
# tech-spec-sm
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
<steps CRITICAL="TRUE">
1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml
3. Pass the yaml path bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written
5. Save outputs after EACH section when generating any documents from templates
</steps>

6
.claude/commands/bmad/bmm/workflows/tech-spec.md
View File

@@ -1,5 +1,5 @@
---
description: 'Generate a comprehensive Technical Specification from PRD and Architecture with acceptance criteria and traceability mapping'
description: 'Technical specification workflow for Level 0 projects (single atomic changes). Creates focused tech spec for bug fixes, single endpoint additions, or small isolated changes. Tech-spec only - no PRD needed.'
---
# tech-spec
@@ -8,8 +8,8 @@ IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the c
<steps CRITICAL="TRUE">
1. Always LOAD the FULL {project-root}/bmad/core/tasks/workflow.xml
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml
3. Pass the yaml path bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml
3. Pass the yaml path bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
4. Follow workflow.xml instructions EXACTLY as written
5. Save outputs after EACH section when generating any documents from templates
</steps>