bmad-method 6.0.0-Beta.3 → 6.0.0-Beta.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude/skills/draft-changelog/SKILL.md +7 -0
- package/.claude/skills/draft-changelog/prompts/instructions.md +58 -0
- package/.claude/skills/gh-triage/README.md +14 -0
- package/.claude/skills/gh-triage/SKILL.md +12 -0
- package/.claude/skills/gh-triage/prompts/agent-prompt.md +60 -0
- package/.claude/skills/gh-triage/prompts/instructions.md +74 -0
- package/.claude/skills/release-module/README.md +24 -0
- package/.claude/skills/release-module/SKILL.md +7 -0
- package/.claude/skills/release-module/prompts/instructions.md +57 -0
- package/.github/ISSUE_TEMPLATE/bug-report.yaml +124 -0
- package/.github/ISSUE_TEMPLATE/documentation.yaml +55 -0
- package/CHANGELOG.md +41 -0
- package/README.md +8 -7
- package/docs/bmgd/bmgd-logo.png +0 -0
- package/docs/bmgd/game-types.md +374 -0
- package/docs/bmgd/index.md +113 -0
- package/docs/bmgd/quick-flow-workflows.md +160 -0
- package/docs/bmgd/workflow.jpg +0 -0
- package/docs/tutorials/getting-started.md +40 -36
- package/package.json +4 -4
- package/src/bmm/agents/quick-flow-solo-dev.agent.yaml +2 -3
- package/src/bmm/agents/quinn.agent.yaml +1 -1
- package/src/bmm/agents/tech-writer/tech-writer.agent.yaml +3 -3
- package/src/bmm/module-help.csv +21 -15
- package/src/bmm/workflows/1-analysis/research/market-steps/step-01-init.md +1 -1
- package/src/bmm/workflows/2-plan-workflows/create-prd/steps-c/step-11-polish.md +1 -1
- package/src/bmm/workflows/2-plan-workflows/create-prd/steps-e/step-e-04-complete.md +1 -1
- package/src/bmm/workflows/2-plan-workflows/create-prd/validation-report-prd-workflow.md +3 -3
- package/src/bmm/workflows/generate-project-context/project-context-template.md +21 -0
- package/src/bmm/workflows/generate-project-context/steps/step-01-discover.md +184 -0
- package/src/bmm/workflows/generate-project-context/steps/step-02-generate.md +318 -0
- package/src/bmm/workflows/generate-project-context/steps/step-03-complete.md +278 -0
- package/src/bmm/workflows/generate-project-context/workflow.md +49 -0
- package/src/core/module-help.csv +8 -8
- package/src/core/tasks/workflow.xml +1 -1
- package/src/utility/agent-components/activation-steps.txt +1 -1
- package/tools/cli/installers/lib/core/manifest.js +1 -0
- package/tools/cli/installers/lib/ide/_config-driven.js +2 -0
- package/tools/cli/installers/lib/ide/codex.js +1 -0
- package/tools/cli/installers/lib/ide/shared/task-tool-command-generator.js +1 -0
- package/tools/cli/installers/lib/ide/templates/agent-command-template.md +1 -0
- package/tools/cli/installers/lib/ide/templates/combined/default-agent.md +1 -0
- package/tools/cli/installers/lib/ide/templates/combined/default-workflow-yaml.md +1 -0
- package/tools/cli/installers/lib/ide/templates/combined/default-workflow.md +1 -0
- package/tools/cli/installers/lib/ide/templates/workflow-command-template.md +1 -0
- package/tools/cli/installers/lib/ide/templates/workflow-commander.md +1 -0
- package/tools/cli/installers/lib/modules/manager.js +2 -2
- package/tools/cli/lib/activation-builder.js +5 -3
- package/tools/validate-agent-schema.js +1 -1
- package/src/bmm/workflows/1-analysis/research/market-steps/step-02-customer-insights.md +0 -200
- /package/.github/ISSUE_TEMPLATE/{feature_request.md → feature-request.md} +0 -0
|
@@ -0,0 +1,58 @@
|
|
|
1
|
+
# Draft Changelog Execution
|
|
2
|
+
|
|
3
|
+
## Input
|
|
4
|
+
Project path (or run from project root)
|
|
5
|
+
|
|
6
|
+
## Step 1: Identify Current State
|
|
7
|
+
- Get the latest released tag
|
|
8
|
+
- Get current version
|
|
9
|
+
- Verify there are commits since the last release
|
|
10
|
+
|
|
11
|
+
## Step 2: Launch Explore Agent
|
|
12
|
+
|
|
13
|
+
Use `thoroughness: "very thorough"` to analyze all changes since the last release tag.
|
|
14
|
+
|
|
15
|
+
**Key: For each merge commit, look up the merged PR/issue that was closed.**
|
|
16
|
+
- Use `gh pr view` or git commit body to find the PR number
|
|
17
|
+
- Read the PR description and comments to understand full context
|
|
18
|
+
- Don't rely solely on commit merge messages - they lack context
|
|
19
|
+
|
|
20
|
+
**Analyze:**
|
|
21
|
+
|
|
22
|
+
1. **All merges/commits** since the last tag
|
|
23
|
+
2. **For each merge, read the original PR/issue** that was closed
|
|
24
|
+
3. **Files changed** with statistics
|
|
25
|
+
4. **Categorize changes:**
|
|
26
|
+
- 🎁 **Features** - New functionality, new agents, new workflows
|
|
27
|
+
- 🐛 **Bug Fixes** - Fixed bugs, corrected issues
|
|
28
|
+
- ♻️ **Refactoring** - Code improvements, reorganization
|
|
29
|
+
- 📚 **Documentation** - Docs updates, README changes
|
|
30
|
+
- 🔧 **Maintenance** - Dependency updates, tooling, infrastructure
|
|
31
|
+
- 💥 **Breaking Changes** - Changes that may affect users
|
|
32
|
+
|
|
33
|
+
**Provide:**
|
|
34
|
+
- Comprehensive summary of ALL changes with PR context
|
|
35
|
+
- Categorization of each change
|
|
36
|
+
- Identification of breaking changes
|
|
37
|
+
- Significance assessment (major/minor/trivial)
|
|
38
|
+
|
|
39
|
+
## Step 3: Generate Draft Changelog
|
|
40
|
+
|
|
41
|
+
Format:
|
|
42
|
+
```markdown
|
|
43
|
+
## v0.X.X - [Date]
|
|
44
|
+
|
|
45
|
+
* [Change 1 - categorized by type]
|
|
46
|
+
* [Change 2]
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
Guidelines:
|
|
50
|
+
- Present tense ("Fix bug" not "Fixed bug")
|
|
51
|
+
- Most significant changes first
|
|
52
|
+
- Group related changes
|
|
53
|
+
- Clear, concise language
|
|
54
|
+
- For breaking changes, clearly indicate impact
|
|
55
|
+
|
|
56
|
+
## Step 4: Present Draft
|
|
57
|
+
|
|
58
|
+
Show the draft with current version, last tag, commit count, and options to edit/retry.
|
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
# gh-triage
|
|
2
|
+
|
|
3
|
+
Fetches all GitHub issues via gh CLI and uses AI agents to deeply analyze, cluster, and prioritize issues.
|
|
4
|
+
|
|
5
|
+
## Usage
|
|
6
|
+
|
|
7
|
+
Run from within any BMad Method repository to triage issues.
|
|
8
|
+
|
|
9
|
+
## What It Does
|
|
10
|
+
|
|
11
|
+
1. Fetches all open issues via `gh issue list`
|
|
12
|
+
2. Splits issues into batches
|
|
13
|
+
3. Launches parallel agents to analyze each batch
|
|
14
|
+
4. Generates comprehensive triage report to `_bmad-output/triage-reports/`
|
|
@@ -0,0 +1,12 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: gh-triage
|
|
3
|
+
description: Fetch all GitHub issues via gh CLI and use AI agents to deeply analyze, cluster, and prioritize issues
|
|
4
|
+
license: MIT
|
|
5
|
+
disable-model-invocation: true
|
|
6
|
+
metadata:
|
|
7
|
+
author: bmad-code-org
|
|
8
|
+
version: "3.0.0"
|
|
9
|
+
compatibility: Requires gh CLI, git repository, and BMad Method with Task tool support
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
Read `prompts/instructions.md` and execute.
|
|
@@ -0,0 +1,60 @@
|
|
|
1
|
+
You are analyzing a batch of GitHub issues for deep understanding and triage.
|
|
2
|
+
|
|
3
|
+
**YOUR TASK:**
|
|
4
|
+
Read the issues in your batch and provide DEEP analysis:
|
|
5
|
+
|
|
6
|
+
1. **For EACH issue, analyze:**
|
|
7
|
+
- What is this ACTUALLY about? (beyond keywords)
|
|
8
|
+
- What component/system does it affect?
|
|
9
|
+
- What's the impact and severity?
|
|
10
|
+
- Is it a bug, feature request, or something else?
|
|
11
|
+
- What specific theme does it belong to?
|
|
12
|
+
|
|
13
|
+
2. **PRIORITY ASSESSMENT:**
|
|
14
|
+
- CRITICAL: Blocks users, security issues, data loss, broken installers
|
|
15
|
+
- HIGH: Major functionality broken, important features missing
|
|
16
|
+
- MEDIUM: Workarounds available, minor bugs, nice-to-have features
|
|
17
|
+
- LOW: Edge cases, cosmetic issues, questions
|
|
18
|
+
|
|
19
|
+
3. **RELATIONSHIPS:**
|
|
20
|
+
- Duplicates: Near-identical issues about the same problem
|
|
21
|
+
- Related: Issues connected by theme or root cause
|
|
22
|
+
- Dependencies: One issue blocks or requires another
|
|
23
|
+
|
|
24
|
+
**YOUR BATCH:**
|
|
25
|
+
[Paste the batch of issues here - each with number, title, body, labels]
|
|
26
|
+
|
|
27
|
+
**OUTPUT FORMAT (JSON only, no markdown):**
|
|
28
|
+
{
|
|
29
|
+
"issues": [
|
|
30
|
+
{
|
|
31
|
+
"number": 123,
|
|
32
|
+
"title": "issue title",
|
|
33
|
+
"deep_understanding": "2-3 sentences explaining what this is really about",
|
|
34
|
+
"affected_components": ["installer", "workflows", "docs"],
|
|
35
|
+
"issue_type": "bug/feature/question/tech-debt",
|
|
36
|
+
"priority": "CRITICAL/HIGH/MEDIUM/LOW",
|
|
37
|
+
"priority_rationale": "Why this priority level",
|
|
38
|
+
"theme": "installation/workflow/integration/docs/ide-support/etc",
|
|
39
|
+
"relationships": {
|
|
40
|
+
"duplicates_of": [456],
|
|
41
|
+
"related_to": [789, 101],
|
|
42
|
+
"blocks": [111]
|
|
43
|
+
}
|
|
44
|
+
}
|
|
45
|
+
],
|
|
46
|
+
"cross_repo_issues": [
|
|
47
|
+
{"number": 123, "target_repo": "bmad-builder", "reason": "about agent builder"}
|
|
48
|
+
],
|
|
49
|
+
"cleanup_candidates": [
|
|
50
|
+
{"number": 456, "reason": "v4-related/outdated/duplicate"}
|
|
51
|
+
],
|
|
52
|
+
"themes_found": {
|
|
53
|
+
"Installation Blockers": {
|
|
54
|
+
"count": 5,
|
|
55
|
+
"root_cause": "Common pattern if identifiable"
|
|
56
|
+
}
|
|
57
|
+
}
|
|
58
|
+
}
|
|
59
|
+
|
|
60
|
+
Return ONLY valid JSON. No explanations outside the JSON structure.
|
|
@@ -0,0 +1,74 @@
|
|
|
1
|
+
# GitHub Issue Triage with AI Analysis
|
|
2
|
+
|
|
3
|
+
**CRITICAL RULES:**
|
|
4
|
+
- NEVER include time or effort estimates in output or recommendations
|
|
5
|
+
- Focus on WHAT needs to be done, not HOW LONG it takes
|
|
6
|
+
- Use Bash tool with gh CLI for all GitHub operations
|
|
7
|
+
|
|
8
|
+
## Execution
|
|
9
|
+
|
|
10
|
+
### Step 1: Fetch Issues
|
|
11
|
+
Use `gh issue list --json number,title,body,labels` to fetch all open issues.
|
|
12
|
+
|
|
13
|
+
### Step 2: Batch Creation
|
|
14
|
+
Split issues into batches of ~10 issues each for parallel analysis.
|
|
15
|
+
|
|
16
|
+
### Step 3: Parallel Agent Analysis
|
|
17
|
+
For EACH batch, use the Task tool with `subagent_type=general-purpose` to launch an agent with prompt from `prompts/agent-prompt.md`
|
|
18
|
+
|
|
19
|
+
### Step 4: Consolidate & Generate Report
|
|
20
|
+
After all agents complete, create a comprehensive markdown report saved to `_bmad-output/triage-reports/triage-YYYY-MM-DD.md`
|
|
21
|
+
|
|
22
|
+
## Report Format
|
|
23
|
+
|
|
24
|
+
### Executive Summary
|
|
25
|
+
- Total issues analyzed
|
|
26
|
+
- Issue count by priority (CRITICAL, HIGH, MEDIUM, LOW)
|
|
27
|
+
- Major themes discovered
|
|
28
|
+
- Top 5 critical issues requiring immediate attention
|
|
29
|
+
|
|
30
|
+
### Critical Issues (CRITICAL Priority)
|
|
31
|
+
For each CRITICAL issue:
|
|
32
|
+
- **#123 - [Issue Title](url)**
|
|
33
|
+
- **What it's about:** [Deep understanding]
|
|
34
|
+
- **Affected:** [Components]
|
|
35
|
+
- **Why Critical:** [Rationale]
|
|
36
|
+
- **Suggested Action:** [Specific action]
|
|
37
|
+
|
|
38
|
+
### High Priority Issues (HIGH Priority)
|
|
39
|
+
Same format as Critical, grouped by theme.
|
|
40
|
+
|
|
41
|
+
### Theme Clusters
|
|
42
|
+
For each major theme:
|
|
43
|
+
- **Theme Name** (N issues)
|
|
44
|
+
- **What connects these:** [Pattern]
|
|
45
|
+
- **Root cause:** [If identifiable]
|
|
46
|
+
- **Consolidated actions:** [Bulk actions if applicable]
|
|
47
|
+
- **Issues:** #123, #456, #789
|
|
48
|
+
|
|
49
|
+
### Relationships & Dependencies
|
|
50
|
+
- **Duplicates:** List pairs with `gh issue close` commands
|
|
51
|
+
- **Related Issues:** Groups of related issues
|
|
52
|
+
- **Dependencies:** Blocking relationships
|
|
53
|
+
|
|
54
|
+
### Cross-Repo Issues
|
|
55
|
+
Issues that should be migrated to other repositories.
|
|
56
|
+
|
|
57
|
+
For each, provide:
|
|
58
|
+
```
|
|
59
|
+
gh issue close XXX --repo CURRENT_REPO --comment "This issue belongs in REPO. Please report at https://github.com/TARGET_REPO/issues/new"
|
|
60
|
+
```
|
|
61
|
+
|
|
62
|
+
### Cleanup Candidates
|
|
63
|
+
- **v4-related:** Deprecated version issues with close commands
|
|
64
|
+
- **Stale:** No activity >30 days
|
|
65
|
+
- **Low priority + old:** Low priority issues >60 days old
|
|
66
|
+
|
|
67
|
+
### Actionable Next Steps
|
|
68
|
+
Specific, prioritized actions:
|
|
69
|
+
1. [CRITICAL] Fix broken installer - affects all new users
|
|
70
|
+
2. [HIGH] Resolve Windows path escaping issues
|
|
71
|
+
3. [HIGH] Address workflow integration bugs
|
|
72
|
+
etc.
|
|
73
|
+
|
|
74
|
+
Include `gh` commands where applicable for bulk actions.
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
# release-module
|
|
2
|
+
|
|
3
|
+
Automates the complete release process for npm modules.
|
|
4
|
+
|
|
5
|
+
## Usage
|
|
6
|
+
|
|
7
|
+
Run from project root or pass project path:
|
|
8
|
+
```
|
|
9
|
+
bmad-utility-skills:release-module
|
|
10
|
+
```
|
|
11
|
+
|
|
12
|
+
## Prerequisite
|
|
13
|
+
|
|
14
|
+
First run `draft-changelog` to analyze changes and create a draft changelog.
|
|
15
|
+
|
|
16
|
+
## What It Does
|
|
17
|
+
|
|
18
|
+
1. Gets and confirms changelog entry
|
|
19
|
+
2. Confirms version bump type (patch/minor/major)
|
|
20
|
+
3. Updates CHANGELOG.md
|
|
21
|
+
4. Bumps version with `npm version`
|
|
22
|
+
5. Pushes git tag
|
|
23
|
+
6. Publishes to npm
|
|
24
|
+
7. Creates GitHub release
|
|
@@ -0,0 +1,57 @@
|
|
|
1
|
+
# Release BMad Module Execution
|
|
2
|
+
|
|
3
|
+
## Input
|
|
4
|
+
Project path (or run from project root)
|
|
5
|
+
|
|
6
|
+
## Execution Steps
|
|
7
|
+
|
|
8
|
+
### Step 1: Get Current State
|
|
9
|
+
- Verify git working tree is clean
|
|
10
|
+
- Get latest tag and current version
|
|
11
|
+
- Check for unpushed commits
|
|
12
|
+
|
|
13
|
+
### Step 2: Get Changelog Entry
|
|
14
|
+
|
|
15
|
+
Ask the user for the changelog entry (from draft-changelog skill or manual).
|
|
16
|
+
|
|
17
|
+
### Step 3: Confirm Changelog
|
|
18
|
+
|
|
19
|
+
Show project name, current version, proposed next version, and changelog. Get confirmation.
|
|
20
|
+
|
|
21
|
+
### Step 4: Confirm Version Bump Type
|
|
22
|
+
|
|
23
|
+
Ask what type of bump: patch, minor, major, prerelease, or custom.
|
|
24
|
+
|
|
25
|
+
### Step 5: Update CHANGELOG.md
|
|
26
|
+
|
|
27
|
+
Insert new entry at top, commit, and push.
|
|
28
|
+
|
|
29
|
+
### Step 6: Bump Version
|
|
30
|
+
|
|
31
|
+
Run `npm version` to update package.json, create commit, and create tag.
|
|
32
|
+
|
|
33
|
+
### Step 7: Push Tag
|
|
34
|
+
|
|
35
|
+
Push the new version tag to GitHub.
|
|
36
|
+
|
|
37
|
+
### Step 8: Publish to npm
|
|
38
|
+
|
|
39
|
+
Publish the package.
|
|
40
|
+
|
|
41
|
+
### Step 9: Create GitHub Release
|
|
42
|
+
|
|
43
|
+
Create release with changelog notes using `gh release create`.
|
|
44
|
+
|
|
45
|
+
### Step 10: Confirm Completion
|
|
46
|
+
|
|
47
|
+
Show npm and GitHub links.
|
|
48
|
+
|
|
49
|
+
## Error Handling
|
|
50
|
+
|
|
51
|
+
Stop immediately on any step failure. Inform user and suggest fix.
|
|
52
|
+
|
|
53
|
+
## Important Notes
|
|
54
|
+
|
|
55
|
+
- Wait for user confirmation before destructive operations
|
|
56
|
+
- Push changelog commit before version bump
|
|
57
|
+
- Use explicit directory paths in commands
|
|
@@ -0,0 +1,124 @@
|
|
|
1
|
+
name: Bug Report
|
|
2
|
+
description: File a bug report to help us improve BMad Method
|
|
3
|
+
title: "[BUG] "
|
|
4
|
+
labels: bug
|
|
5
|
+
assignees: []
|
|
6
|
+
body:
|
|
7
|
+
- type: markdown
|
|
8
|
+
attributes:
|
|
9
|
+
value: |
|
|
10
|
+
Thanks for filing a bug report! Please fill out the information below to help us reproduce and fix the issue.
|
|
11
|
+
|
|
12
|
+
- type: textarea
|
|
13
|
+
id: description
|
|
14
|
+
attributes:
|
|
15
|
+
label: Description
|
|
16
|
+
description: Clear and concise description of what the bug is
|
|
17
|
+
placeholder: e.g., When I run /dev-story, it crashes on step 3
|
|
18
|
+
validations:
|
|
19
|
+
required: true
|
|
20
|
+
|
|
21
|
+
- type: textarea
|
|
22
|
+
id: steps
|
|
23
|
+
attributes:
|
|
24
|
+
label: Steps to reproduce
|
|
25
|
+
description: Step-by-step instructions to reproduce the behavior
|
|
26
|
+
placeholder: |
|
|
27
|
+
1. Run 'npx bmad-method install'
|
|
28
|
+
2. Select option X
|
|
29
|
+
3. Run workflow Y
|
|
30
|
+
4. See error
|
|
31
|
+
validations:
|
|
32
|
+
required: true
|
|
33
|
+
|
|
34
|
+
- type: textarea
|
|
35
|
+
id: expected
|
|
36
|
+
attributes:
|
|
37
|
+
label: Expected behavior
|
|
38
|
+
description: What you expected to happen
|
|
39
|
+
placeholder: The workflow should complete successfully
|
|
40
|
+
validations:
|
|
41
|
+
required: true
|
|
42
|
+
|
|
43
|
+
- type: textarea
|
|
44
|
+
id: actual
|
|
45
|
+
attributes:
|
|
46
|
+
label: Actual behavior
|
|
47
|
+
description: What actually happened
|
|
48
|
+
placeholder: The workflow crashed with error "..."
|
|
49
|
+
validations:
|
|
50
|
+
required: true
|
|
51
|
+
|
|
52
|
+
- type: textarea
|
|
53
|
+
id: screenshots
|
|
54
|
+
attributes:
|
|
55
|
+
label: Screenshots
|
|
56
|
+
description: Add screenshots if applicable (paste images directly)
|
|
57
|
+
placeholder: Paste any relevant screenshots here
|
|
58
|
+
|
|
59
|
+
- type: dropdown
|
|
60
|
+
id: module
|
|
61
|
+
attributes:
|
|
62
|
+
label: Which module is this for?
|
|
63
|
+
description: Select the BMad module this issue relates to
|
|
64
|
+
options:
|
|
65
|
+
- BMad Method (BMM) - Core Framework
|
|
66
|
+
- BMad Builder (BMB) - Agent Builder Tool
|
|
67
|
+
- Test Architect (TEA) - Test Strategy Module
|
|
68
|
+
- Game Dev Studio (BMGD) - Game Development Module
|
|
69
|
+
- Creative Intelligence Suite (CIS) - Innovation Module
|
|
70
|
+
- Not sure / Other
|
|
71
|
+
validations:
|
|
72
|
+
required: true
|
|
73
|
+
|
|
74
|
+
- type: input
|
|
75
|
+
id: version
|
|
76
|
+
attributes:
|
|
77
|
+
label: BMad Version
|
|
78
|
+
description: "Check with: npx bmad-method --version or check package.json"
|
|
79
|
+
placeholder: e.g., 6.0.0-Beta.4
|
|
80
|
+
validations:
|
|
81
|
+
required: true
|
|
82
|
+
|
|
83
|
+
- type: dropdown
|
|
84
|
+
id: ide
|
|
85
|
+
attributes:
|
|
86
|
+
label: Which AI IDE are you using?
|
|
87
|
+
options:
|
|
88
|
+
- Claude Code
|
|
89
|
+
- Cursor
|
|
90
|
+
- Windsurf
|
|
91
|
+
- Copilot CLI / GitHub Copilot
|
|
92
|
+
- Kilo Code
|
|
93
|
+
- Other
|
|
94
|
+
validations:
|
|
95
|
+
required: true
|
|
96
|
+
|
|
97
|
+
- type: dropdown
|
|
98
|
+
id: platform
|
|
99
|
+
attributes:
|
|
100
|
+
label: Operating System
|
|
101
|
+
options:
|
|
102
|
+
- macOS
|
|
103
|
+
- Windows
|
|
104
|
+
- Linux
|
|
105
|
+
- Other
|
|
106
|
+
validations:
|
|
107
|
+
required: true
|
|
108
|
+
|
|
109
|
+
- type: textarea
|
|
110
|
+
id: logs
|
|
111
|
+
attributes:
|
|
112
|
+
label: Relevant log output
|
|
113
|
+
description: Copy and paste any relevant log output
|
|
114
|
+
render: shell
|
|
115
|
+
|
|
116
|
+
- type: checkboxes
|
|
117
|
+
id: terms
|
|
118
|
+
attributes:
|
|
119
|
+
label: Confirm
|
|
120
|
+
options:
|
|
121
|
+
- label: I've searched for existing issues
|
|
122
|
+
required: true
|
|
123
|
+
- label: I'm using the latest version
|
|
124
|
+
required: false
|
|
@@ -0,0 +1,55 @@
|
|
|
1
|
+
name: Documentation
|
|
2
|
+
description: Report issues or suggest improvements to documentation
|
|
3
|
+
title: "[DOCS] "
|
|
4
|
+
labels: documentation
|
|
5
|
+
assignees: []
|
|
6
|
+
body:
|
|
7
|
+
- type: markdown
|
|
8
|
+
attributes:
|
|
9
|
+
value: |
|
|
10
|
+
Help us improve the BMad Method documentation!
|
|
11
|
+
|
|
12
|
+
- type: dropdown
|
|
13
|
+
id: doc-type
|
|
14
|
+
attributes:
|
|
15
|
+
label: What type of documentation issue is this?
|
|
16
|
+
options:
|
|
17
|
+
- Error or inaccuracy
|
|
18
|
+
- Missing information
|
|
19
|
+
- Unclear or confusing
|
|
20
|
+
- Outdated content
|
|
21
|
+
- Request for new documentation
|
|
22
|
+
- Typo or grammar
|
|
23
|
+
validations:
|
|
24
|
+
required: true
|
|
25
|
+
|
|
26
|
+
- type: textarea
|
|
27
|
+
id: location
|
|
28
|
+
attributes:
|
|
29
|
+
label: Documentation location
|
|
30
|
+
description: Where is the documentation that needs improvement?
|
|
31
|
+
placeholder: e.g., http://docs.bmad-method.org/tutorials/getting-started/ or "In the README"
|
|
32
|
+
validations:
|
|
33
|
+
required: true
|
|
34
|
+
|
|
35
|
+
- type: textarea
|
|
36
|
+
id: issue
|
|
37
|
+
attributes:
|
|
38
|
+
label: What's the issue?
|
|
39
|
+
description: Describe the documentation issue in detail
|
|
40
|
+
placeholder: e.g., Step 3 says to run command X but it should be command Y
|
|
41
|
+
validations:
|
|
42
|
+
required: true
|
|
43
|
+
|
|
44
|
+
- type: textarea
|
|
45
|
+
id: suggestion
|
|
46
|
+
attributes:
|
|
47
|
+
label: Suggested improvement
|
|
48
|
+
description: How would you like to see this improved?
|
|
49
|
+
placeholder: e.g., Change the command to X and add an example
|
|
50
|
+
|
|
51
|
+
- type: input
|
|
52
|
+
id: version
|
|
53
|
+
attributes:
|
|
54
|
+
label: BMad Version (if applicable)
|
|
55
|
+
placeholder: e.g., 6.0.0-Beta.4
|
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,46 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [6.0.0-Beta.5]
|
|
4
|
+
|
|
5
|
+
### 🎁 Features
|
|
6
|
+
|
|
7
|
+
* **Add generate-project-context workflow** — New 3-step workflow for project context generation, integrated with quick-flow-solo-dev agent
|
|
8
|
+
* **Shard market research customer analysis** — Refactor monolithic customer insights into 4-step detailed customer behavior analysis workflow
|
|
9
|
+
|
|
10
|
+
### 🐛 Bug Fixes
|
|
11
|
+
|
|
12
|
+
* **Fix npm install peer dependency issues** — Add `.npmrc` with `legacy-peer-deps=true`, update Starlight to 0.37.5, and add `--legacy-peer-deps` flag to module installer (PR #1476)
|
|
13
|
+
* **Fix leaked source paths in PRD validation report** — Replace absolute `/src/core/` paths with `{project-root}/_bmad/core/` (#1481)
|
|
14
|
+
* **Fix orphaned market research customer analysis** — Connect step-01-init to step-02-customer-behavior to complete workflow sharding (#1486)
|
|
15
|
+
* **Fix duplicate 2-letter brainstorming code** — Change BS to BSP to resolve conflict with cis Brainstorming module
|
|
16
|
+
* **Fix tech writer sidecar functionality** — Enable proper sidecar operation (#1487)
|
|
17
|
+
* **Fix relative paths in workflow steps** — Correct paths in step-11-polish (#1497) and step-e-04-complete (#1498)
|
|
18
|
+
* **Fix party-mode workflow file extension** — Correct extension in workflow.xml (#1499)
|
|
19
|
+
* **Fix generated slash commands** — Add `disable-model-invocation` to all generated commands (#1501)
|
|
20
|
+
* **Fix agent scan and help CSV files** — Correct module-help.csv entries
|
|
21
|
+
* **Fix HELP_STEP placeholder replacement** — Fix placeholder not replaced in compiled agents, fix hardcoded path, fix single quote (#1437)
|
|
22
|
+
|
|
23
|
+
### 📚 Documentation
|
|
24
|
+
|
|
25
|
+
* **Add exact slash commands to Getting Started guide** — Provide precise command examples for users (#1505)
|
|
26
|
+
* **Remove .claude/commands from version control** — Commands are generated, not tracked (#1506)
|
|
27
|
+
|
|
28
|
+
### 🔧 Maintenance
|
|
29
|
+
|
|
30
|
+
* **Update Starlight to 0.37.5** — Latest version with peer dependency compatibility
|
|
31
|
+
* **Add GitHub issue templates** — New bug-report.yaml and documentation.yaml templates
|
|
32
|
+
|
|
33
|
+
---
|
|
34
|
+
|
|
35
|
+
## [6.0.0-Beta.4]
|
|
36
|
+
|
|
37
|
+
### 🐛 Bug Fixes
|
|
38
|
+
|
|
39
|
+
- **Activation steps formatting fix**: Fixed missing opening quote that caused infrequent menu rendering issues
|
|
40
|
+
- **Custom module installation fix**: Added missing yaml require in manifest.js to fix custom module installation
|
|
41
|
+
|
|
42
|
+
---
|
|
43
|
+
|
|
3
44
|
## [6.0.0-Beta.3]
|
|
4
45
|
|
|
5
46
|
### 🌟 Key Highlights
|
package/README.md
CHANGED
|
@@ -65,13 +65,13 @@ Every step tells you what's next. Optional phases (brainstorming, research, UX d
|
|
|
65
65
|
|
|
66
66
|
BMad Method extends with official modules for specialized domains. Modules are available during installation and can be added to your project at any time. After the V6 beta period these will also be available as Plugins and Granular Skills.
|
|
67
67
|
|
|
68
|
-
| Module | GitHub | NPM
|
|
69
|
-
| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
|
|
70
|
-
| **BMad Method (BMM)** | [bmad-code-org/BMAD-METHOD](https://github.com/bmad-code-org/BMAD-METHOD) | [bmad-method](https://www.npmjs.com/package/bmad-method) | Core framework with 34+ workflows across 4 development phases
|
|
71
|
-
| **BMad Builder (BMB)** | [bmad-code-org/bmad-builder](https://github.com/bmad-code-org/bmad-builder) | [bmad-builder](https://www.npmjs.com/package/bmad-builder) | Create custom BMad agents, workflows, and domain-specific modules
|
|
72
|
-
| **Test Architect (TEA)** 🆕
|
|
73
|
-
| **Game Dev Studio (BMGD)** | [bmad-code-org/bmad-module-game-dev-studio](https://github.com/bmad-code-org/bmad-module-game-dev-studio) | [bmad-game-dev-studio](https://www.npmjs.com/package/bmad-game-dev-studio) | Game development workflows for Unity, Unreal, and Godot
|
|
74
|
-
| **Creative Intelligence Suite (CIS)** | [bmad-code-org/bmad-module-creative-intelligence-suite](https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite) | [bmad-creative-intelligence-suite](https://www.npmjs.com/package/bmad-creative-intelligence-suite) | Innovation, brainstorming, design thinking, and problem-solving
|
|
68
|
+
| Module | GitHub | NPM | Purpose |
|
|
69
|
+
| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
|
|
70
|
+
| **BMad Method (BMM)** | [bmad-code-org/BMAD-METHOD](https://github.com/bmad-code-org/BMAD-METHOD) | [bmad-method](https://www.npmjs.com/package/bmad-method) | Core framework with 34+ workflows across 4 development phases |
|
|
71
|
+
| **BMad Builder (BMB)** | [bmad-code-org/bmad-builder](https://github.com/bmad-code-org/bmad-builder) | [bmad-builder](https://www.npmjs.com/package/bmad-builder) | Create custom BMad agents, workflows, and domain-specific modules |
|
|
72
|
+
| **Test Architect (TEA)** 🆕 | [bmad-code-org/tea](https://github.com/bmad-code-org/bmad-method-test-architecture-enterprise) | [tea](https://www.npmjs.com/package/bmad-method-test-architecture-enterprise) | Risk-based test strategy, automation, and release gates (8 workflows) |
|
|
73
|
+
| **Game Dev Studio (BMGD)** | [bmad-code-org/bmad-module-game-dev-studio](https://github.com/bmad-code-org/bmad-module-game-dev-studio) | [bmad-game-dev-studio](https://www.npmjs.com/package/bmad-game-dev-studio) | Game development workflows for Unity, Unreal, and Godot |
|
|
74
|
+
| **Creative Intelligence Suite (CIS)** | [bmad-code-org/bmad-module-creative-intelligence-suite](https://github.com/bmad-code-org/bmad-module-creative-intelligence-suite) | [bmad-creative-intelligence-suite](https://www.npmjs.com/package/bmad-creative-intelligence-suite) | Innovation, brainstorming, design thinking, and problem-solving |
|
|
75
75
|
|
|
76
76
|
* More modules are coming in the next 2 weeks from BMad Official, and a community marketplace for the installer also will be coming with the final V6 release!
|
|
77
77
|
|
|
@@ -116,6 +116,7 @@ BMad provides two testing options to fit your needs:
|
|
|
116
116
|
### For v4 Users
|
|
117
117
|
|
|
118
118
|
- **[v4 Documentation](https://github.com/bmad-code-org/BMAD-METHOD/tree/V4/docs)**
|
|
119
|
+
- If you need to install V4, you can do this with `npx bmad-method@4.44.3 install` - similar for any past version.
|
|
119
120
|
|
|
120
121
|
## Community
|
|
121
122
|
|
|
Binary file
|