bmad-method 6.11.0 → 6.11.1-next.1

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/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "$schema": "https://json.schemastore.org/package.json",
3
3
  "name": "bmad-method",
4
- "version": "6.11.0",
4
+ "version": "6.11.1-next.1",
5
5
  "description": "Breakthrough Method of Agile AI-driven Development",
6
6
  "keywords": [
7
7
  "agile",
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: bmad-project-context
3
- description: 'Set up, refresh, or audit a repository''s agent instructions (the AGENTS.md block) so AI agents work well in that repo. Also records observed agent mistakes as pitfall lines. Must be invoked by name.'
3
+ description: 'Set up, refresh, or audit a repository''s agent instructions (the AGENTS.md block) so AI agents work well in that repo. Also records observed agent mistakes as pitfalls. Must be invoked by name.'
4
4
  ---
5
5
 
6
6
  # Overview
@@ -72,7 +72,7 @@ Never commit.
72
72
  ### 6. Close
73
73
 
74
74
  - What went in, and what was left out and why.
75
- - Why, in the user's terms, from `best-practices.md` — why it is small, why what the repo already states stays out, why a pitfall line stays until its cause is gone.
75
+ - Why, in the user's terms, from `best-practices.md` — why it is small, why what the repo already states stays out, why a pitfall stays until its cause is gone.
76
76
  - How it loads, and that other harness files can point at it.
77
77
  - Maintenance: re-run after significant change, `record` the moment an agent gets something wrong, prefer a check over a new line.
78
78
  - Rules repeating across their projects, or personal rather than the team's, belong in their global agent config.
@@ -91,7 +91,7 @@ If the target has a `project-context.md` from the retired skills, commonly under
91
91
 
92
92
  ## Record
93
93
 
94
- Capture one observed agent mistake as it happens — the only admissible source for a pitfall line.
94
+ Capture one observed agent mistake as it happens — the only admissible source for a pitfall.
95
95
 
96
96
  Take the task, the mistake, the correction, and its evidence. Check the block for a line already covering it. One occurrence is noted; a recurring or costly mistake earns a line now — an exact invocation under **Running and verifying** when it is a command error, otherwise a pitfall. Write it and show the diff. If it is mechanically preventable, propose the hook, lint rule, or CI check instead.
97
97
 
@@ -99,7 +99,7 @@ Take the task, the mistake, the correction, and its evidence. Check the block fo
99
99
 
100
100
  Re-check every caveat, path-check every file, follow every pointer, and ask of every line whether removing it would change agent behavior. Check for contradictions with other instruction files.
101
101
 
102
- Failing lines move behind an observable trigger, get fixed, or are deleted — confirm deletions first. **A policy or pitfall line goes only when the thing it guards is gone or the user retires it; nothing failing lately is not grounds.** Audit ends smaller or equal.
102
+ Failing lines move behind an observable trigger, get fixed, or are deleted — confirm deletions first. **A policy or pitfall goes only when the thing it guards is gone or the user retires it; nothing failing lately is not grounds.** Audit ends smaller or equal.
103
103
 
104
104
  ## Children
105
105
 
@@ -32,7 +32,7 @@ Prefer prohibitions to advice, and name the permitted alternative in the same li
32
32
 
33
33
  ## Retire
34
34
 
35
- A policy or pitfall line goes only when the thing it guards is gone, or the user retires it. Nothing failing lately is not evidence — a working rule erases its own evidence.
35
+ A policy or pitfall goes only when the thing it guards is gone, or the user retires it. Nothing failing lately is not evidence — a working rule erases its own evidence.
36
36
 
37
37
  Every other line faces one question at each write: would removing it change agent behavior? If no, cut it.
38
38
 
@@ -335,6 +335,13 @@ platforms:
335
335
  target_dir: .agents/skills
336
336
  global_target_dir: ~/.agents/skills
337
337
 
338
+ zcode:
339
+ name: "ZCode"
340
+ preferred: false
341
+ installer:
342
+ target_dir: .zcode/skills
343
+ global_target_dir: ~/.zcode/skills
344
+
338
345
  zencoder:
339
346
  name: "Zencoder"
340
347
  preferred: false