bmad-auto-copilot 1.1.3 → 1.2.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bmad-auto-copilot",
-  "version": "1.1.3",
+  "version": "1.2.0",
   "description": "Automated BMAD story development loop using GitHub Copilot CLI — install into any BMAD project",
   "keywords": [
     "bmad",

package/templates/prompts/code-review.md

@@ -6,9 +6,12 @@ Timestamp: {TIMESTAMP}
 
 ## Step 1: Load Configuration and Workflow
 Read the BMAD config from: `_bmad/bmm/config.yaml` — resolve all variables ({project-root}, {output_folder}, etc.)
-Read the workflow definition from: `_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml`
-Read the workflow instructions from: `_bmad/bmm/workflows/4-implementation/code-review/instructions.xml`
-Read the workflow checklist from: `_bmad/bmm/workflows/4-implementation/code-review/checklist.md`
+Read the workflow definition from: `_bmad/bmm/workflows/4-implementation/bmad-code-review/workflow.md`
+Read and follow these review step files:
+- `_bmad/bmm/workflows/4-implementation/bmad-code-review/steps/step-01-gather-context.md`
+- `_bmad/bmm/workflows/4-implementation/bmad-code-review/steps/step-02-review.md`
+- `_bmad/bmm/workflows/4-implementation/bmad-code-review/steps/step-03-triage.md`
+- `_bmad/bmm/workflows/4-implementation/bmad-code-review/steps/step-04-present.md`
 
 ## Step 2: Find Next Story
 Read `_bmad-output/implementation-artifacts/sprint-status.yaml` and find the FIRST story in `review` state (scan top to bottom, exclude retrospectives).
@@ -24,8 +27,8 @@ Perform a thorough ADVERSARIAL code review following the workflow instructions:
 - Do NOT review files in `_bmad/`, `_bmad-output/`, `.cursor/`, `.windsurf/`, or `.claude/` directories — only review application source code
 - Verify EVERY task marked [x] is actually implemented
 - Verify EVERY Acceptance Criterion is actually satisfied
-- Find 3-10 specific problems: code quality, test coverage, architecture compliance, security, performance
-- **AUTOMATICALLY FIX all HIGH and MEDIUM issues** (this is option [1] from instructions.xml Step 4 — always choose this)
+- Run the review layers and triage to identify specific problems: code quality, test coverage, architecture compliance, security, performance
+- **AUTOMATICALLY FIX all HIGH and MEDIUM issues** as an automation override after triage
 - Run all tests to verify fixes pass
 - Update the story File List and Dev Agent Record with any fixes applied
 - NEVER accept "looks good" without finding real issues
@@ -39,7 +42,7 @@ Based on review outcome:
 ## Rules
 - Use best judgment for ALL decisions — never ask the user
 - Execute ALL steps without pausing — this is YOLO mode (no confirmation between steps)
-- When instructions.xml has `<ask>` tags, always choose "Fix them automatically" (option 1)
+- When workflow step files contain `<ask>` tags or checkpoint confirmations, use best judgment and continue automatically
 - Document issues you cannot auto-fix in the story file
 - All tests must pass after any fixes
 - Follow the workflow checklist to verify completeness

package/templates/prompts/create-story.md

@@ -6,16 +6,16 @@ Timestamp: {TIMESTAMP}
 
 ## Step 1: Load Configuration and Workflow
 Read the BMAD config from: `_bmad/bmm/config.yaml` — resolve all variables ({project-root}, {output_folder}, etc.)
-Read the workflow definition from: `_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml`
-Read the workflow instructions from: `_bmad/bmm/workflows/4-implementation/create-story/instructions.xml`
-Read the workflow template from: `_bmad/bmm/workflows/4-implementation/create-story/template.md`
-Read the workflow checklist from: `_bmad/bmm/workflows/4-implementation/create-story/checklist.md`
+Read the workflow definition from: `_bmad/bmm/workflows/4-implementation/bmad-create-story/workflow.md`
+Read the input discovery protocol from: `_bmad/bmm/workflows/4-implementation/bmad-create-story/discover-inputs.md`
+Read the workflow template from: `_bmad/bmm/workflows/4-implementation/bmad-create-story/template.md`
+Read the workflow checklist from: `_bmad/bmm/workflows/4-implementation/bmad-create-story/checklist.md`
 
 ## Step 2: Find Next Story
 Read `_bmad-output/implementation-artifacts/sprint-status.yaml` and find the FIRST story in `backlog` state (scan top to bottom, exclude retrospectives).
 
 ## Step 3: Load and Analyze Context (Exhaustive)
-Follow the instructions.xml discover_inputs protocol:
+Follow the workflow.md analysis flow and discover-inputs protocol:
 - Read the corresponding epic file from `_bmad-output/planning-artifacts/`
 - Read PRD, architecture docs, and any referenced project context artifacts
 - Analyze previous story files for context continuity (patterns, conventions, decisions)
@@ -32,5 +32,5 @@ Update `_bmad-output/implementation-artifacts/sprint-status.yaml` — change the
 - Do NOT implement the story code — only create the story file
 - Follow the workflow template precisely
 - Execute ALL steps without pausing — this is YOLO mode (no confirmation between steps)
-- When instructions.xml has `<ask>` tags, use best judgment instead of asking
+- When workflow files contain `<ask>` tags or checkpoint confirmations, use best judgment and continue automatically
 - If blocking issues arise, document them in the story file and continue

package/templates/prompts/dev-story.md

@@ -6,10 +6,8 @@ Timestamp: {TIMESTAMP}
 
 ## Step 1: Load Configuration and Workflow
 Read the BMAD config from: `_bmad/bmm/config.yaml` — resolve all variables ({project-root}, {output_folder}, etc.)
-Read the workflow definition from: `_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml`
-Read the workflow instructions from: `_bmad/bmm/workflows/4-implementation/dev-story/instructions.xml`
-Read the workflow template (if exists) from: `_bmad/bmm/workflows/4-implementation/dev-story/`
-Read the workflow checklist from: `_bmad/bmm/workflows/4-implementation/dev-story/checklist.md`
+Read the workflow definition from: `_bmad/bmm/workflows/4-implementation/bmad-dev-story/workflow.md`
+Read the workflow checklist from: `_bmad/bmm/workflows/4-implementation/bmad-dev-story/checklist.md`
 
 ## Step 2: Find Next Story
 Read `_bmad-output/implementation-artifacts/sprint-status.yaml` and find the FIRST story in `ready-for-dev` or `in-progress` state (scan top to bottom, exclude retrospectives).
@@ -25,7 +23,7 @@ Update `_bmad-output/implementation-artifacts/sprint-status.yaml` — change the
 
 ## Step 5: Implement
 Follow the workflow instructions to implement ALL tasks and subtasks defined in the story:
-- Follow the red-green-refactor TDD cycle as specified in instructions.xml
+- Follow the red-green-refactor TDD cycle as specified in workflow.md
 - Write failing tests first, then minimal code to pass, then refactor
 - Write comprehensive unit tests — tests must pass 100%
 - Follow ALL acceptance criteria precisely
@@ -43,7 +41,7 @@ After ALL tasks are complete and ALL tests pass:
 ## Rules
 - Use best judgment for ALL decisions — never ask the user
 - Execute ALL steps without pausing — this is YOLO mode (no confirmation between steps)
-- When instructions.xml has `<ask>` tags, use best judgment instead of asking
+- When workflow files contain `<ask>` tags or checkpoint confirmations, use best judgment and continue automatically
 - Follow the workflow checklist to verify completeness
 - Ensure all existing tests continue to pass
 - NEVER mark a task [x] unless it is truly complete with passing tests