bmad-method 6.2.3-next.29 → 6.2.3-next.30
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,4 +1,5 @@
|
|
|
1
1
|
module,skill,display-name,menu-code,description,action,args,phase,after,before,required,output-location,outputs
|
|
2
|
+
BMad Method,_meta,,,,,,,,,false,https://docs.bmad-method.org/llms.txt,
|
|
2
3
|
BMad Method,bmad-document-project,Document Project,DP,Analyze an existing project to produce useful documentation.,,anytime,,,false,project-knowledge,*
|
|
3
4
|
BMad Method,bmad-generate-project-context,Generate Project Context,GPC,Scan existing codebase to generate a lean LLM-optimized project-context.md. Essential for brownfield projects.,,anytime,,,false,output_folder,project context
|
|
4
5
|
BMad Method,bmad-quick-dev,Quick Dev,QQ,Unified intent-in code-out workflow: clarify plan implement review and present.,,anytime,,,false,implementation_artifacts,spec and project implementation
|
|
@@ -7,7 +7,7 @@ description: 'Analyzes current state and user query to answer BMad questions or
|
|
|
7
7
|
|
|
8
8
|
## Purpose
|
|
9
9
|
|
|
10
|
-
Help the user understand where they are in their BMad workflow and what to do next
|
|
10
|
+
Help the user understand where they are in their BMad workflow and what to do next, and also answer broader questions when asked that could be augmented with remote sources such as module documentation sources.
|
|
11
11
|
|
|
12
12
|
## Desired Outcomes
|
|
13
13
|
|
|
@@ -18,6 +18,7 @@ When this skill completes, the user should:
|
|
|
18
18
|
3. **Know how to invoke it** — skill name, menu code, action context, and any args that shortcut the conversation
|
|
19
19
|
4. **Get offered a quick start** — when a single skill is the clear next step, offer to run it for the user right now rather than just listing it
|
|
20
20
|
5. **Feel oriented, not overwhelmed** — surface only what's relevant to their current position; don't dump the entire catalog
|
|
21
|
+
6. **Get answers to general questions** — when the question doesn't map to a specific skill, use the module's registered documentation to give a grounded answer
|
|
21
22
|
|
|
22
23
|
## Data Sources
|
|
23
24
|
|
|
@@ -25,6 +26,7 @@ When this skill completes, the user should:
|
|
|
25
26
|
- **Config**: `config.yaml` and `user-config.yaml` files in `{project-root}/_bmad/` and its subfolders — resolve `output-location` variables, provide `communication_language` and `project_knowledge`
|
|
26
27
|
- **Artifacts**: Files matching `outputs` patterns at resolved `output-location` paths reveal which steps are possibly completed; their content may also provide grounding context for recommendations
|
|
27
28
|
- **Project knowledge**: If `project_knowledge` resolves to an existing path, read it for grounding context. Never fabricate project-specific details.
|
|
29
|
+
- **Module docs**: Rows with `_meta` in the `skill` column carry a URL or path in `output-location` pointing to the module's documentation (e.g., llms.txt). Fetch and use these to answer general questions about that module.
|
|
28
30
|
|
|
29
31
|
## CSV Interpretation
|
|
30
32
|
|
|
@@ -70,4 +72,4 @@ For each recommended item, present:
|
|
|
70
72
|
- Present all output in `{communication_language}`
|
|
71
73
|
- Recommend running each skill in a **fresh context window**
|
|
72
74
|
- Match the user's tone — conversational when they're casual, structured when they want specifics
|
|
73
|
-
- If the active module is ambiguous,
|
|
75
|
+
- If the active module is ambiguous, retrieve all meta rows remote sources to find relevant info also to help answer their question
|
|
@@ -1,4 +1,5 @@
|
|
|
1
1
|
module,skill,display-name,menu-code,description,action,args,phase,after,before,required,output-location,outputs
|
|
2
|
+
Core,_meta,,,,,,,,,false,https://docs.bmad-method.org/llms.txt,
|
|
2
3
|
Core,bmad-brainstorming,Brainstorming,BSP,Use early in ideation or when stuck generating ideas.,,anytime,,,false,{output_folder}/brainstorming,brainstorming session
|
|
3
4
|
Core,bmad-party-mode,Party Mode,PM,Orchestrate multi-agent discussions when you need multiple perspectives or want agents to collaborate.,,anytime,,,false,,
|
|
4
5
|
Core,bmad-help,BMad Help,BH,,,anytime,,,false,,
|
|
@@ -969,6 +969,14 @@ class Installer {
|
|
|
969
969
|
outputs,
|
|
970
970
|
] = columns;
|
|
971
971
|
|
|
972
|
+
// Pass through _meta rows as-is (module metadata, not a skill)
|
|
973
|
+
if (phase === '_meta') {
|
|
974
|
+
const finalModule = (!module || module.trim() === '') && moduleName !== 'core' ? moduleName : module || '';
|
|
975
|
+
const metaRow = [finalModule, '_meta', '', '', '', '', '', 'false', '', '', '', '', '', '', outputLocation || '', ''];
|
|
976
|
+
allRows.push(metaRow.map((c) => this.escapeCSVField(c)).join(','));
|
|
977
|
+
continue;
|
|
978
|
+
}
|
|
979
|
+
|
|
972
980
|
// If module column is empty, set it to this module's name (except for core which stays empty for universal tools)
|
|
973
981
|
const finalModule = (!module || module.trim() === '') && moduleName !== 'core' ? moduleName : module || '';
|
|
974
982
|
|