bmad-method 1.1.0 → 4.2.0
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/.bmad-core/tasks/index-docs.md +3 -5
- package/.claude/settings.local.json +22 -0
- package/README.md +1 -1
- package/docs/versioning-and-releases.md +4 -4
- package/expansion-packs/infrastructure-devops/agents/infra-devops-platform.md +2 -2
- package/package.json +1 -1
- package/tools/installer/README.md +2 -2
|
@@ -56,7 +56,7 @@ You are now operating as a Documentation Indexer. Your goal is to ensure all doc
|
|
|
56
56
|
|
|
57
57
|
The index should be organized as follows:
|
|
58
58
|
|
|
59
|
-
|
|
59
|
+
```markdown
|
|
60
60
|
# Documentation Index
|
|
61
61
|
|
|
62
62
|
## Root Documents
|
|
@@ -88,8 +88,7 @@ Documents within the `another-folder/` directory:
|
|
|
88
88
|
### [Nested Document](./another-folder/document.md)
|
|
89
89
|
|
|
90
90
|
Description of nested document.
|
|
91
|
-
|
|
92
|
-
````text
|
|
91
|
+
```text
|
|
93
92
|
|
|
94
93
|
### Index Entry Format
|
|
95
94
|
|
|
@@ -99,8 +98,7 @@ Each entry should follow this format:
|
|
|
99
98
|
### [Document Title](relative/path/to/file.md)
|
|
100
99
|
|
|
101
100
|
Brief description of the document's purpose and contents.
|
|
102
|
-
|
|
103
|
-
````
|
|
101
|
+
```
|
|
104
102
|
|
|
105
103
|
### Rules of Operation
|
|
106
104
|
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
{
|
|
2
|
+
"permissions": {
|
|
3
|
+
"allow": [
|
|
4
|
+
"Bash(npm run build:*)",
|
|
5
|
+
"Bash(rm:*)",
|
|
6
|
+
"Bash(ls:*)",
|
|
7
|
+
"Bash(cat:*)",
|
|
8
|
+
"Bash(npm install:*)",
|
|
9
|
+
"Bash(npx husky init:*)",
|
|
10
|
+
"Bash(chmod:*)",
|
|
11
|
+
"Bash(node:*)",
|
|
12
|
+
"Bash(git add:*)",
|
|
13
|
+
"Bash(npx lint-staged:*)",
|
|
14
|
+
"Bash(npx prettier:*)",
|
|
15
|
+
"Bash(git commit:*)",
|
|
16
|
+
"Bash(mkdir:*)",
|
|
17
|
+
"Bash(npm run version:minor:*)",
|
|
18
|
+
"Bash(npm uninstall:*)"
|
|
19
|
+
],
|
|
20
|
+
"deny": []
|
|
21
|
+
}
|
|
22
|
+
}
|
package/README.md
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
[](https://www.npmjs.com/package/bmad-method)
|
|
4
4
|
[](LICENSE)
|
|
5
5
|
[](https://nodejs.org)
|
|
6
|
-
[](https://discord.gg/
|
|
6
|
+
[](https://discord.gg/g6ypHytrCB)
|
|
7
7
|
|
|
8
8
|
**AI-Powered Agile Development Framework** - Transform your software development with specialized AI agents that work as your complete Agile team.
|
|
9
9
|
|
|
@@ -8,7 +8,7 @@ The easiest way to release new versions is through **automatic semantic releases
|
|
|
8
8
|
|
|
9
9
|
Use these prefixes to control what type of release happens:
|
|
10
10
|
|
|
11
|
-
|
|
11
|
+
```bash
|
|
12
12
|
fix: resolve CLI argument parsing bug # → patch release (4.1.0 → 4.1.1)
|
|
13
13
|
feat: add new agent orchestration mode # → minor release (4.1.0 → 4.2.0)
|
|
14
14
|
feat!: redesign CLI interface # → major release (4.1.0 → 5.0.0)
|
|
@@ -35,13 +35,13 @@ git push
|
|
|
35
35
|
|
|
36
36
|
# That's it! Release happens automatically 🎉
|
|
37
37
|
# Users can now run: npx bmad-method (and get the new version)
|
|
38
|
-
|
|
38
|
+
```
|
|
39
39
|
|
|
40
40
|
### Commits That DON'T Trigger Releases
|
|
41
41
|
|
|
42
42
|
These commit types won't create releases (use them for maintenance):
|
|
43
43
|
|
|
44
|
-
|
|
44
|
+
```bash
|
|
45
45
|
chore: update dependencies # No release
|
|
46
46
|
docs: fix typo in readme # No release
|
|
47
47
|
style: format code # No release
|
|
@@ -52,7 +52,7 @@ test: add unit tests # No release
|
|
|
52
52
|
|
|
53
53
|
```bash
|
|
54
54
|
npm run release:test # Safe to run locally - tests the config
|
|
55
|
-
|
|
55
|
+
```
|
|
56
56
|
|
|
57
57
|
---
|
|
58
58
|
|
|
@@ -31,8 +31,8 @@ persona:
|
|
|
31
31
|
- Collaborative Operations - Work closely with development teams fostering shared responsibility for system reliability
|
|
32
32
|
startup:
|
|
33
33
|
- Announce: Hey! I'm Alex, your DevOps Infrastructure Specialist. I love when things run secure, stable, reliable and performant. I can help with infrastructure architecture, platform engineering, CI/CD pipelines, and operational excellence. What infrastructure challenge can I help you with today?
|
|
34
|
-
-
|
|
35
|
-
-
|
|
34
|
+
- 'List available tasks: review-infrastructure, validate-infrastructure, create infrastructure documentation'
|
|
35
|
+
- 'List available templates: infrastructure-architecture, infrastructure-platform-from-arch'
|
|
36
36
|
- Execute selected task or stay in persona to help guided by Core DevOps Principles
|
|
37
37
|
commands:
|
|
38
38
|
- '*help" - Show: numbered list of the following commands to allow selection'
|
package/package.json
CHANGED