quick flow updates to aid discovery and implementation
This commit is contained in:
parent
208f27dcdb
commit
aba9d11c88
|
|
@ -76,7 +76,7 @@ a) **Before asking detailed questions, do a rapid scan to understand the landsca
|
||||||
|
|
||||||
b) **Check for existing context docs:**
|
b) **Check for existing context docs:**
|
||||||
|
|
||||||
- Check `{output_folder}` for planning documents (PRD, architecture, epics)
|
- Check `{output_folder}` and `{planning_artifacts}`for planning documents (PRD, architecture, epics, research)
|
||||||
- Check for `**/project-context.md` - if it exists, skim for patterns and conventions
|
- Check for `**/project-context.md` - if it exists, skim for patterns and conventions
|
||||||
- Check for any existing stories or specs related to user's request
|
- Check for any existing stories or specs related to user's request
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -69,7 +69,7 @@ This uses **step-file architecture** for disciplined execution:
|
||||||
|
|
||||||
Load and read full config from `{main_config}` and resolve:
|
Load and read full config from `{main_config}` and resolve:
|
||||||
|
|
||||||
- `project_name`, `output_folder`, `implementation_artifacts`, `user_name`
|
- `project_name`, `output_folder`, `planning_artifacts`, `implementation_artifacts`, `user_name`
|
||||||
- `communication_language`, `document_output_language`, `user_skill_level`
|
- `communication_language`, `document_output_language`, `user_skill_level`
|
||||||
- `date` as system-generated current datetime
|
- `date` as system-generated current datetime
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -40,7 +40,7 @@ First, check if the project uses Git version control:
|
||||||
|
|
||||||
### 2. Load Project Context
|
### 2. Load Project Context
|
||||||
|
|
||||||
Check if `{project_context}` exists (`**/project-context.md`). If found, load it - this is foundational reference for ALL implementation decisions.
|
Check if `{project_context}` exists (`**/project-context.md`). If found, load it as a foundational reference for ALL implementation decisions.
|
||||||
|
|
||||||
### 3. Parse User Input
|
### 3. Parse User Input
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -28,7 +28,7 @@ This uses **step-file architecture** for focused execution:
|
||||||
Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
|
Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
|
||||||
|
|
||||||
- `user_name`, `communication_language`, `user_skill_level`
|
- `user_name`, `communication_language`, `user_skill_level`
|
||||||
- `output_folder`, `sprint_artifacts`
|
- `output_folder`, `planning_artifacts`, `implementation_artifacts`
|
||||||
- `date` as system-generated current datetime
|
- `date` as system-generated current datetime
|
||||||
|
|
||||||
### Paths
|
### Paths
|
||||||
|
|
|
||||||
|
|
@ -142,11 +142,7 @@ function buildMenuXml(menuItems) {
|
||||||
}
|
}
|
||||||
// Handle legacy format menu items
|
// Handle legacy format menu items
|
||||||
else if (item.trigger) {
|
else if (item.trigger) {
|
||||||
// For legacy items, keep using cmd with *<trigger> format
|
|
||||||
let trigger = item.trigger || '';
|
let trigger = item.trigger || '';
|
||||||
if (!trigger.startsWith('*')) {
|
|
||||||
trigger = '*' + trigger;
|
|
||||||
}
|
|
||||||
|
|
||||||
const attrs = [`cmd="${trigger}"`];
|
const attrs = [`cmd="${trigger}"`];
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue