bmad-method 6.2.1-next.2 → 6.2.1-next.3

package/AGENTS.md

@@ -7,3 +7,5 @@ Open source framework for structured, agent-assisted software delivery.
 - Use Conventional Commits for every commit.
 - Before pushing, run `npm ci && npm run quality` on `HEAD` in the exact checkout you are about to push.
   `quality` mirrors the checks in `.github/workflows/quality.yaml`.
+
+- Skill validation rules are in `tools/skill-validator.md`.

package/package.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://json.schemastore.org/package.json",
   "name": "bmad-method",
-  "version": "6.2.1-next.2",
+  "version": "6.2.1-next.3",
   "description": "Breakthrough Method of Agile AI-driven Development",
   "keywords": [
     "agile",

package/src/bmm/workflows/bmad-quick-flow/bmad-quick-dev-new-preview/{steps/step-02-plan.md → step-02-plan.md}

@@ -13,7 +13,7 @@ deferred_work_file: '{implementation_artifacts}/deferred-work.md'
 ## INSTRUCTIONS
 
 1. Investigate codebase. _Isolate deep exploration in sub-agents/tasks where available. To prevent context snowballing, instruct subagents to give you distilled summaries only._
-2. Read `../tech-spec-template.md` fully. Fill it out based on the intent and investigation, and write the result to `{wipFile}`.
+2. Read `./tech-spec-template.md` fully. Fill it out based on the intent and investigation, and write the result to `{wipFile}`.
 3. Self-review against READY FOR DEVELOPMENT standard.
 4. If intent gaps exist, do not fantasize, do not leave open questions, HALT and ask the human.
 5. Token count check (see SCOPE STANDARD). If spec exceeds 1600 tokens:

package/src/bmm/workflows/bmad-quick-flow/bmad-quick-dev-new-preview/workflow.md

@@ -76,4 +76,4 @@ YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `
 
 ### 3. First Step Execution
 
-Read fully and follow: `./steps/step-01-clarify-and-route.md` to begin the workflow.
+Read fully and follow: `./step-01-clarify-and-route.md` to begin the workflow.