fix: correct 3 broken file refs and enforce validator in CI (#1717)
- create-architecture/workflow.md: fix installed_path dir name from 'architecture' to 'create-architecture' - create-story/checklist.md: fix 2 refs from validate-workflow.xml to workflow.xml (file does not exist with validate- prefix) - package.json: add --strict to validate:refs so broken references fail CI instead of logging warnings and exiting 0 Co-authored-by: Brian <bmadcode@gmail.com>
This commit is contained in:
parent
e72b82ed31
commit
fb05848dd3
|
|
@ -45,7 +45,7 @@
|
||||||
"test:install": "node test/test-installation-components.js",
|
"test:install": "node test/test-installation-components.js",
|
||||||
"test:refs": "node test/test-file-refs-csv.js",
|
"test:refs": "node test/test-file-refs-csv.js",
|
||||||
"test:schemas": "node test/test-agent-schema.js",
|
"test:schemas": "node test/test-agent-schema.js",
|
||||||
"validate:refs": "node tools/validate-file-refs.js",
|
"validate:refs": "node tools/validate-file-refs.js --strict",
|
||||||
"validate:schemas": "node tools/validate-agent-schema.js"
|
"validate:schemas": "node tools/validate-agent-schema.js"
|
||||||
},
|
},
|
||||||
"lint-staged": {
|
"lint-staged": {
|
||||||
|
|
|
||||||
|
|
@ -36,7 +36,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
|
||||||
|
|
||||||
### Paths
|
### Paths
|
||||||
|
|
||||||
- `installed_path` = `{project-root}/_bmad/bmm/workflows/3-solutioning/architecture`
|
- `installed_path` = `{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture`
|
||||||
- `template_path` = `{installed_path}/architecture-decision-template.md`
|
- `template_path` = `{installed_path}/architecture-decision-template.md`
|
||||||
- `data_files_path` = `{installed_path}/data/`
|
- `data_files_path` = `{installed_path}/data/`
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -33,7 +33,7 @@ This is a COMPETITION to create the **ULTIMATE story context** that makes LLM de
|
||||||
|
|
||||||
### **When Running from Create-Story Workflow:**
|
### **When Running from Create-Story Workflow:**
|
||||||
|
|
||||||
- The `{project-root}/_bmad/core/tasks/validate-workflow.xml` framework will automatically:
|
- The `{project-root}/_bmad/core/tasks/workflow.xml` framework will automatically:
|
||||||
- Load this checklist file
|
- Load this checklist file
|
||||||
- Load the newly created story file (`{story_file_path}`)
|
- Load the newly created story file (`{story_file_path}`)
|
||||||
- Load workflow variables from `{installed_path}/workflow.yaml`
|
- Load workflow variables from `{installed_path}/workflow.yaml`
|
||||||
|
|
@ -63,7 +63,7 @@ You will systematically re-do the entire story creation process, but with a crit
|
||||||
|
|
||||||
1. **Load the workflow configuration**: `{installed_path}/workflow.yaml` for variable inclusion
|
1. **Load the workflow configuration**: `{installed_path}/workflow.yaml` for variable inclusion
|
||||||
2. **Load the story file**: `{story_file_path}` (provided by user or discovered)
|
2. **Load the story file**: `{story_file_path}` (provided by user or discovered)
|
||||||
3. **Load validation framework**: `{project-root}/_bmad/core/tasks/validate-workflow.xml`
|
3. **Load validation framework**: `{project-root}/_bmad/core/tasks/workflow.xml`
|
||||||
4. **Extract metadata**: epic_num, story_num, story_key, story_title from story file
|
4. **Extract metadata**: epic_num, story_num, story_key, story_title from story file
|
||||||
5. **Resolve all workflow variables**: implementation_artifacts, epics_file, architecture_file, etc.
|
5. **Resolve all workflow variables**: implementation_artifacts, epics_file, architecture_file, etc.
|
||||||
6. **Understand current status**: What story implementation guidance is currently provided?
|
6. **Understand current status**: What story implementation guidance is currently provided?
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue