@cregis-dev/cckit 0.2.0 → 0.4.0

package/templates/bmad/commands/bmad-bmm-create-story.md

@@ -1,14 +1,14 @@
 ---
 name: 'create-story'
-description: 'Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says 'create the next story' or 'create story [story identifier]''
+description: 'Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]"'
 ---
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 
 <steps CRITICAL="TRUE">
-1. Always LOAD the FULL @{project-root}/_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml
-3. Pass the yaml path @{project-root}/_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+1. Always LOAD the FULL {project-root}/_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml
+3. Pass the yaml path {project-root}/_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>

package/templates/bmad/commands/bmad-bmm-create-ux-design.md

@@ -1,6 +1,6 @@
 ---
 name: 'create-ux-design'
-description: 'Plan UX patterns and design specifications. Use when the user says 'lets create UX design' or 'create UX specifications' or 'help me plan the UX''
+description: 'Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"'
 ---
 
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md, READ its entire contents and follow its directions exactly!
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md, READ its entire contents and follow its directions exactly!

package/templates/bmad/commands/bmad-bmm-dev-story.md

@@ -1,14 +1,14 @@
 ---
 name: 'dev-story'
-description: 'Execute story implementation following a context filled story spec file. Use when the user says 'dev this story [story file]' or 'implement the next story in the sprint plan''
+description: 'Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"'
 ---
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 
 <steps CRITICAL="TRUE">
-1. Always LOAD the FULL @{project-root}/_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml
-3. Pass the yaml path @{project-root}/_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+1. Always LOAD the FULL {project-root}/_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml
+3. Pass the yaml path {project-root}/_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>

package/templates/bmad/commands/bmad-bmm-document-project.md

@@ -1,14 +1,14 @@
 ---
 name: 'document-project'
-description: 'Document brownfield projects for AI context. Use when the user says 'document this project' or 'generate project docs''
+description: 'Document brownfield projects for AI context. Use when the user says "document this project" or "generate project docs"'
 ---
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 
 <steps CRITICAL="TRUE">
-1. Always LOAD the FULL @{project-root}/_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/document-project/workflow.yaml
-3. Pass the yaml path @{project-root}/_bmad/bmm/workflows/document-project/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+1. Always LOAD the FULL {project-root}/_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/_bmad/bmm/workflows/document-project/workflow.yaml
+3. Pass the yaml path {project-root}/_bmad/bmm/workflows/document-project/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>

package/templates/bmad/commands/bmad-bmm-domain-research.md

@@ -1,6 +1,6 @@
 ---
 name: 'domain-research'
-description: 'Conduct domain and industry research. Use when the user says 'lets create a research report on [domain or industry]'
+description: 'Conduct domain and industry research. Use when the user says "lets create a research report on [domain or industry]"'
 ---
 
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow-domain-research.md, READ its entire contents and follow its directions exactly!
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/_bmad/bmm/workflows/1-analysis/research/workflow-domain-research.md, READ its entire contents and follow its directions exactly!

package/templates/bmad/commands/bmad-bmm-edit-prd.md

@@ -1,6 +1,6 @@
 ---
 name: 'edit-prd'
-description: 'Edit an existing PRD. Use when the user says 'edit this PRD'.'
+description: 'Edit an existing PRD. Use when the user says "edit this PRD".'
 ---
 
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-edit-prd.md, READ its entire contents and follow its directions exactly!
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-edit-prd.md, READ its entire contents and follow its directions exactly!

package/templates/bmad/commands/bmad-bmm-generate-project-context.md

@@ -1,6 +1,6 @@
 ---
 name: 'generate-project-context'
-description: 'Create project-context.md with AI rules. Use when the user says 'generate project context' or 'create project context''
+description: 'Create project-context.md with AI rules. Use when the user says "generate project context" or "create project context"'
 ---
 
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/generate-project-context/workflow.md, READ its entire contents and follow its directions exactly!
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/_bmad/bmm/workflows/generate-project-context/workflow.md, READ its entire contents and follow its directions exactly!

package/templates/bmad/commands/bmad-bmm-market-research.md

@@ -1,6 +1,6 @@
 ---
 name: 'market-research'
-description: 'Conduct market research on competition and customers. Use when the user says 'create a market research report about [business idea]'.'
+description: 'Conduct market research on competition and customers. Use when the user says "create a market research report about [business idea]".'
 ---
 
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow-market-research.md, READ its entire contents and follow its directions exactly!
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/_bmad/bmm/workflows/1-analysis/research/workflow-market-research.md, READ its entire contents and follow its directions exactly!

package/templates/bmad/commands/bmad-bmm-qa-generate-e2e-tests.md

@@ -1,14 +1,14 @@
 ---
 name: 'qa-generate-e2e-tests'
-description: 'Generate end to end automated tests for existing features. Use when the user says 'create qa automated tests for [feature]''
+description: 'Generate end to end automated tests for existing features. Use when the user says "create qa automated tests for [feature]"'
 ---
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 
 <steps CRITICAL="TRUE">
-1. Always LOAD the FULL @{project-root}/_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/qa-generate-e2e-tests/workflow.yaml
-3. Pass the yaml path @{project-root}/_bmad/bmm/workflows/qa-generate-e2e-tests/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+1. Always LOAD the FULL {project-root}/_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/_bmad/bmm/workflows/qa-generate-e2e-tests/workflow.yaml
+3. Pass the yaml path {project-root}/_bmad/bmm/workflows/qa-generate-e2e-tests/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>

package/templates/bmad/commands/bmad-bmm-quick-dev.md

@@ -1,6 +1,6 @@
 ---
 name: 'quick-dev'
-description: 'Implement a Quick Tech Spec for small changes or features. Use when the user provides a quick tech spec and says 'implement this quick spec' or 'proceed with implementation of [quick tech spec]''
+description: 'Implement a Quick Tech Spec for small changes or features. Use when the user provides a quick tech spec and says "implement this quick spec" or "proceed with implementation of [quick tech spec]"'
 ---
 
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md, READ its entire contents and follow its directions exactly!
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md, READ its entire contents and follow its directions exactly!

package/templates/bmad/commands/bmad-bmm-quick-spec.md

@@ -1,6 +1,6 @@
 ---
 name: 'quick-spec'
-description: 'Very quick process to create implementation-ready quick specs for small changes or features. Use when the user says 'create a quick spec' or 'generate a quick tech spec''
+description: 'Very quick process to create implementation-ready quick specs for small changes or features. Use when the user says "create a quick spec" or "generate a quick tech spec"'
 ---
 
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md, READ its entire contents and follow its directions exactly!
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md, READ its entire contents and follow its directions exactly!

package/templates/bmad/commands/bmad-bmm-retrospective.md

@@ -1,14 +1,14 @@
 ---
 name: 'retrospective'
-description: 'Post-epic review to extract lessons and assess success. Use when the user says 'run a retrospective' or 'lets retro the epic [epic]''
+description: 'Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"'
 ---
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 
 <steps CRITICAL="TRUE">
-1. Always LOAD the FULL @{project-root}/_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml
-3. Pass the yaml path @{project-root}/_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+1. Always LOAD the FULL {project-root}/_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml
+3. Pass the yaml path {project-root}/_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>

package/templates/bmad/commands/bmad-bmm-sprint-planning.md

@@ -1,14 +1,14 @@
 ---
 name: 'sprint-planning'
-description: 'Generate sprint status tracking from epics. Use when the user says 'run sprint planning' or 'generate sprint plan''
+description: 'Generate sprint status tracking from epics. Use when the user says "run sprint planning" or "generate sprint plan"'
 ---
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 
 <steps CRITICAL="TRUE">
-1. Always LOAD the FULL @{project-root}/_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml
-3. Pass the yaml path @{project-root}/_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+1. Always LOAD the FULL {project-root}/_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml
+3. Pass the yaml path {project-root}/_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>

package/templates/bmad/commands/bmad-bmm-sprint-status.md

@@ -1,14 +1,14 @@
 ---
 name: 'sprint-status'
-description: 'Summarize sprint status and surface risks. Use when the user says 'check sprint status' or 'show sprint status''
+description: 'Summarize sprint status and surface risks. Use when the user says "check sprint status" or "show sprint status"'
 ---
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 
 <steps CRITICAL="TRUE">
-1. Always LOAD the FULL @{project-root}/_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml
-3. Pass the yaml path @{project-root}/_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+1. Always LOAD the FULL {project-root}/_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml
+3. Pass the yaml path {project-root}/_bmad/bmm/workflows/4-implementation/sprint-status/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>

package/templates/bmad/commands/bmad-bmm-technical-research.md

@@ -1,6 +1,6 @@
 ---
 name: 'technical-research'
-description: 'Conduct technical research on technologies and architecture. Use when the user says 'create a technical research report on [topic]'.'
+description: 'Conduct technical research on technologies and architecture. Use when the user says "create a technical research report on [topic]".'
 ---
 
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow-technical-research.md, READ its entire contents and follow its directions exactly!
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/_bmad/bmm/workflows/1-analysis/research/workflow-technical-research.md, READ its entire contents and follow its directions exactly!

package/templates/bmad/commands/bmad-bmm-validate-prd.md

@@ -1,6 +1,6 @@
 ---
 name: 'validate-prd'
-description: 'Validate a PRD against standards. Use when the user says 'validate this PRD' or 'run PRD validation''
+description: 'Validate a PRD against standards. Use when the user says "validate this PRD" or "run PRD validation"'
 ---
 
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md, READ its entire contents and follow its directions exactly!
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/_bmad/bmm/workflows/2-plan-workflows/create-prd/workflow-validate-prd.md, READ its entire contents and follow its directions exactly!

package/templates/bmad/commands/bmad-brainstorming.md

@@ -1,6 +1,6 @@
 ---
 name: 'brainstorming'
-description: 'Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods. Use when the user says 'help me brainstorm' or 'help me ideate'.'
+description: 'Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods. Use when the user says help me brainstorm or help me ideate.'
 ---
 
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/core/workflows/brainstorming/workflow.md, READ its entire contents and follow its directions exactly!
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/_bmad/core/workflows/brainstorming/workflow.md, READ its entire contents and follow its directions exactly!

package/templates/bmad/commands/bmad-editorial-review-prose.md

@@ -1,6 +1,6 @@
 ---
 name: 'editorial-review-prose'
-description: 'Clinical copy-editor that reviews text for communication issues. Use when user says 'review for prose' or 'improve the prose''
+description: 'Clinical copy-editor that reviews text for communication issues. Use when user says review for prose or improve the prose'
 ---
 
 # editorial-review-prose

package/templates/bmad/commands/bmad-editorial-review-structure.md

@@ -1,6 +1,6 @@
 ---
 name: 'editorial-review-structure'
-description: 'Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension. Use when user requests 'structural review' or 'cohesive reivew' or 'editorial review of structure'.'
+description: 'Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension. Use when user requests structural review or editorial review of structure'
 ---
 
 # editorial-review-structure

package/templates/bmad/commands/bmad-help.md

@@ -1,6 +1,6 @@
 ---
 name: 'help'
-description: 'Analyzes what is done and the users query and offers advice on what to do next. Use if user says 'bmad-help what should I do next' or 'bmad-help what do I do now''
+description: 'Analyzes what is done and the users query and offers advice on what to do next. Use if user says what should I do next or what do I do now'
 ---
 
 # help

package/templates/bmad/commands/bmad-index-docs.md

@@ -1,6 +1,6 @@
 ---
 name: 'index-docs'
-description: 'Generates or updates an index.md to reference all docs in the folder. Use if user requests to 'create an index of all files [here]' or 'reindex the folder [here].'
+description: 'Generates or updates an index.md to reference all docs in the folder. Use if user requests to create or update an index of all files in a specific folder'
 ---
 
 # index-docs

package/templates/bmad/commands/bmad-party-mode.md

@@ -1,6 +1,6 @@
 ---
 name: 'party-mode'
-description: 'Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations. Use when user requests 'party mode' only.'
+description: 'Orchestrates group discussions between all installed BMAD agents, enabling natural multi-agent conversations. Use when user requests party mode.'
 ---
 
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/core/workflows/party-mode/workflow.md, READ its entire contents and follow its directions exactly!
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/_bmad/core/workflows/party-mode/workflow.md, READ its entire contents and follow its directions exactly!

package/templates/bmad/commands/bmad-review-adversarial-general.md

@@ -1,6 +1,6 @@
 ---
 name: 'review-adversarial-general'
-description: 'Perform a Cynical Review and produce a findings report. Use when the user requests a 'critical review of' or 'cynical review of' something.'
+description: 'Perform a Cynical Review and produce a findings report. Use when the user requests a critical review of something'
 ---
 
 # review-adversarial-general

package/templates/bmad/commands/bmad-review-edge-case-hunter.md

@@ -0,0 +1,10 @@
+---
+name: 'review-edge-case-hunter'
+description: 'Walk every branching path and boundary condition in content, report only unhandled edge cases. Orthogonal to adversarial review - method-driven not attitude-driven.'
+---
+
+# review-edge-case-hunter
+
+Read the entire task file at: {project-root}/_bmad/core/tasks/review-edge-case-hunter.xml
+
+Follow all instructions in the task file exactly as written.

package/templates/bmad/commands/bmad-shard-doc.md

@@ -1,6 +1,6 @@
 ---
 name: 'shard-doc'
-description: 'Splits large markdown documents into smaller, organized files based on level 2 (default) sections. Use if the user says 'Shard Document [document]''
+description: 'Splits large markdown documents into smaller, organized files based on level 2 (default) sections. Use if the user says perform shard document'
 ---
 
 # shard-doc

package/templates/bmad/commands/bmad-tea-teach-me-testing.md

@@ -1,6 +1,6 @@
 ---
 name: 'teach-me-testing'
-description: 'Teach testing progressively through structured sessions. Use when user says 'lets learn testing' or 'I want to study test practices''
+description: 'Teach testing progressively through structured sessions. Use when user says "lets learn testing" or "I want to study test practices"'
 ---
 
-IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_bmad/tea/workflows/testarch/teach-me-testing/workflow.md, READ its entire contents and follow its directions exactly!
+IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL {project-root}/_bmad/tea/workflows/testarch/teach-me-testing/workflow.md, READ its entire contents and follow its directions exactly!

package/templates/bmad/commands/bmad-tea-testarch-atdd.md

@@ -1,14 +1,14 @@
 ---
 name: 'testarch-atdd'
-description: 'Generate failing acceptance tests using TDD cycle. Use when the user says 'lets write acceptance tests' or 'I want to do ATDD''
+description: 'Generate failing acceptance tests using TDD cycle. Use when the user says "lets write acceptance tests" or "I want to do ATDD"'
 ---
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 
 <steps CRITICAL="TRUE">
-1. Always LOAD the FULL @{project-root}/_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/tea/workflows/testarch/atdd/workflow.yaml
-3. Pass the yaml path @{project-root}/_bmad/tea/workflows/testarch/atdd/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+1. Always LOAD the FULL {project-root}/_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/_bmad/tea/workflows/testarch/atdd/workflow.yaml
+3. Pass the yaml path {project-root}/_bmad/tea/workflows/testarch/atdd/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>

package/templates/bmad/commands/bmad-tea-testarch-automate.md

@@ -1,14 +1,14 @@
 ---
 name: 'testarch-automate'
-description: 'Expand test automation coverage for codebase. Use when the user says 'lets expand test coverage' or 'I want to automate tests''
+description: 'Expand test automation coverage for codebase. Use when the user says "lets expand test coverage" or "I want to automate tests"'
 ---
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 
 <steps CRITICAL="TRUE">
-1. Always LOAD the FULL @{project-root}/_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/tea/workflows/testarch/automate/workflow.yaml
-3. Pass the yaml path @{project-root}/_bmad/tea/workflows/testarch/automate/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+1. Always LOAD the FULL {project-root}/_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/_bmad/tea/workflows/testarch/automate/workflow.yaml
+3. Pass the yaml path {project-root}/_bmad/tea/workflows/testarch/automate/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>

package/templates/bmad/commands/bmad-tea-testarch-ci.md

@@ -1,14 +1,14 @@
 ---
 name: 'testarch-ci'
-description: 'Scaffold CI/CD quality pipeline with test execution. Use when the user says 'lets setup CI pipeline' or 'I want to create quality gates''
+description: 'Scaffold CI/CD quality pipeline with test execution. Use when the user says "lets setup CI pipeline" or "I want to create quality gates"'
 ---
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 
 <steps CRITICAL="TRUE">
-1. Always LOAD the FULL @{project-root}/_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/tea/workflows/testarch/ci/workflow.yaml
-3. Pass the yaml path @{project-root}/_bmad/tea/workflows/testarch/ci/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+1. Always LOAD the FULL {project-root}/_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/_bmad/tea/workflows/testarch/ci/workflow.yaml
+3. Pass the yaml path {project-root}/_bmad/tea/workflows/testarch/ci/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>

package/templates/bmad/commands/bmad-tea-testarch-framework.md

@@ -1,14 +1,14 @@
 ---
 name: 'testarch-framework'
-description: 'Initialize test framework with Playwright or Cypress. Use when the user says 'lets setup test framework' or 'I want to initialize testing framework''
+description: 'Initialize test framework with Playwright or Cypress. Use when the user says "lets setup test framework" or "I want to initialize testing framework"'
 ---
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 
 <steps CRITICAL="TRUE">
-1. Always LOAD the FULL @{project-root}/_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/tea/workflows/testarch/framework/workflow.yaml
-3. Pass the yaml path @{project-root}/_bmad/tea/workflows/testarch/framework/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+1. Always LOAD the FULL {project-root}/_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/_bmad/tea/workflows/testarch/framework/workflow.yaml
+3. Pass the yaml path {project-root}/_bmad/tea/workflows/testarch/framework/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>

package/templates/bmad/commands/bmad-tea-testarch-nfr.md

@@ -1,14 +1,14 @@
 ---
 name: 'testarch-nfr'
-description: 'Assess NFRs like performance security and reliability. Use when the user says 'lets assess NFRs' or 'I want to evaluate non-functional requirements''
+description: 'Assess NFRs like performance security and reliability. Use when the user says "lets assess NFRs" or "I want to evaluate non-functional requirements"'
 ---
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 
 <steps CRITICAL="TRUE">
-1. Always LOAD the FULL @{project-root}/_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/tea/workflows/testarch/nfr-assess/workflow.yaml
-3. Pass the yaml path @{project-root}/_bmad/tea/workflows/testarch/nfr-assess/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+1. Always LOAD the FULL {project-root}/_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/_bmad/tea/workflows/testarch/nfr-assess/workflow.yaml
+3. Pass the yaml path {project-root}/_bmad/tea/workflows/testarch/nfr-assess/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>

package/templates/bmad/commands/bmad-tea-testarch-test-design.md

@@ -1,14 +1,14 @@
 ---
 name: 'testarch-test-design'
-description: 'Create system-level or epic-level test plans. Use when the user says 'lets design test plan' or 'I want to create test strategy''
+description: 'Create system-level or epic-level test plans. Use when the user says "lets design test plan" or "I want to create test strategy"'
 ---
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 
 <steps CRITICAL="TRUE">
-1. Always LOAD the FULL @{project-root}/_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/tea/workflows/testarch/test-design/workflow.yaml
-3. Pass the yaml path @{project-root}/_bmad/tea/workflows/testarch/test-design/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+1. Always LOAD the FULL {project-root}/_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/_bmad/tea/workflows/testarch/test-design/workflow.yaml
+3. Pass the yaml path {project-root}/_bmad/tea/workflows/testarch/test-design/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>

package/templates/bmad/commands/bmad-tea-testarch-test-review.md

@@ -1,14 +1,14 @@
 ---
 name: 'testarch-test-review'
-description: 'Review test quality using best practices validation. Use when the user says 'lets review tests' or 'I want to evaluate test quality''
+description: 'Review test quality using best practices validation. Use when the user says "lets review tests" or "I want to evaluate test quality"'
 ---
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 
 <steps CRITICAL="TRUE">
-1. Always LOAD the FULL @{project-root}/_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/tea/workflows/testarch/test-review/workflow.yaml
-3. Pass the yaml path @{project-root}/_bmad/tea/workflows/testarch/test-review/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+1. Always LOAD the FULL {project-root}/_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/_bmad/tea/workflows/testarch/test-review/workflow.yaml
+3. Pass the yaml path {project-root}/_bmad/tea/workflows/testarch/test-review/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>

package/templates/bmad/commands/bmad-tea-testarch-trace.md

@@ -1,14 +1,14 @@
 ---
 name: 'testarch-trace'
-description: 'Generate traceability matrix and quality gate decision. Use when the user says 'lets create traceability matrix' or 'I want to analyze test coverage''
+description: 'Generate traceability matrix and quality gate decision. Use when the user says "lets create traceability matrix" or "I want to analyze test coverage"'
 ---
 
 IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
 
 <steps CRITICAL="TRUE">
-1. Always LOAD the FULL @{project-root}/_bmad/core/tasks/workflow.xml
-2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config @{project-root}/_bmad/tea/workflows/testarch/trace/workflow.yaml
-3. Pass the yaml path @{project-root}/_bmad/tea/workflows/testarch/trace/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
+1. Always LOAD the FULL {project-root}/_bmad/core/tasks/workflow.xml
+2. READ its entire contents - this is the CORE OS for EXECUTING the specific workflow-config {project-root}/_bmad/tea/workflows/testarch/trace/workflow.yaml
+3. Pass the yaml path {project-root}/_bmad/tea/workflows/testarch/trace/workflow.yaml as 'workflow-config' parameter to the workflow.xml instructions
 4. Follow workflow.xml instructions EXACTLY as written to process and follow the specific workflow config and its instructions
 5. Save outputs after EACH section when generating any documents from templates
 </steps>

package/templates/bmad/core/config.yaml

@@ -1,6 +1,6 @@
 # CORE Module Configuration
 # Generated by BMAD installer
-# Version: 6.0.2
+# Version: 6.0.4
 # Date: {install_date}
 
 user_name: {user_name}

package/templates/bmad/core/module-help.csv

@@ -7,3 +7,4 @@ core,anytime,Shard Document,SD,,_bmad/core/tasks/shard-doc.xml,bmad-shard-doc,fa
 core,anytime,Editorial Review - Prose,EP,,_bmad/core/tasks/editorial-review-prose.xml,bmad-editorial-review-prose,false,,,"Review prose for clarity, tone, and communication issues. Use after drafting to polish written content.",report located with target document,"three-column markdown table with suggested fixes",
 core,anytime,Editorial Review - Structure,ES,,_bmad/core/tasks/editorial-review-structure.xml,bmad-editorial-review-structure,false,,,"Propose cuts, reorganization, and simplification while preserving comprehension. Use when doc produced from multiple subprocesses or needs structural improvement.",report located with target document,
 core,anytime,Adversarial Review (General),AR,,_bmad/core/tasks/review-adversarial-general.xml,bmad-review-adversarial-general,false,,,"Review content critically to find issues and weaknesses. Use for quality assurance or before finalizing deliverables. Code Review in other modules run this automatically, but its useful also for document reviews",,
+core,anytime,Edge Case Hunter Review,ECH,,_bmad/core/tasks/review-edge-case-hunter.xml,bmad-review-edge-case-hunter,false,,,"Walk every branching path and boundary condition in code, report only unhandled edge cases. Use alongside adversarial review for orthogonal coverage - method-driven not attitude-driven.",,

package/templates/bmad/core/tasks/editorial-review-prose.xml

@@ -1,6 +1,6 @@
 <task id="_bmad/core/tasks/editorial-review-prose.xml"
   name="Editorial Review - Prose"
-  description="Clinical copy-editor that reviews text for communication issues. Use when user says 'review for prose' or 'improve the prose'">
+  description="Clinical copy-editor that reviews text for communication issues. Use when user says review for prose or improve the prose">
 
   <objective>Review text for communication issues that impede comprehension and output suggested fixes in a three-column table</objective>
 

package/templates/bmad/core/tasks/editorial-review-structure.xml

@@ -3,7 +3,7 @@
   but no context except the content to review -->
 <task id="_bmad/core/tasks/editorial-review-structure.xml"
   name="Editorial Review - Structure"
-  description="Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension. Use when user requests 'structural review' or 'cohesive reivew' or 'editorial review of structure'.">
+  description="Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension. Use when user requests structural review or editorial review of structure">
   <objective>Review document structure and propose substantive changes
     to improve clarity and flow-run this BEFORE copy editing</objective>
   <inputs>

package/templates/bmad/core/tasks/help.md

@@ -1,6 +1,6 @@
 ---
 name: help
-description: "Analyzes what is done and the users query and offers advice on what to do next. Use if user says 'bmad-help what should I do next' or 'bmad-help what do I do now'"
+description: 'Analyzes what is done and the users query and offers advice on what to do next. Use if user says what should I do next or what do I do now'
 ---
 
 # Task: BMAD Help

package/templates/bmad/core/tasks/index-docs.xml

@@ -1,5 +1,5 @@
 <task id="_bmad/core/tasks/index-docs" name="Index Docs"
-  description="Generates or updates an index.md to reference all docs in the folder. Use if user requests to 'create an index of all files [here]' or 'reindex the folder [here].">
+  description="Generates or updates an index.md to reference all docs in the folder. Use if user requests to create or update an index of all files in a specific folder">
   <llm critical="true">
     <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
     <i>DO NOT skip steps or change the sequence</i>

package/templates/bmad/core/tasks/review-adversarial-general.xml

@@ -2,7 +2,7 @@
   but no context except the content to review -->
 
 <task id="_bmad/core/tasks/review-adversarial-general.xml" name="Adversarial Review (General)"
-  description="Perform a Cynical Review and produce a findings report. Use when the user requests a 'critical review of' or 'cynical review of' something.">
+  description="Perform a Cynical Review and produce a findings report. Use when the user requests a critical review of something">
   <objective>Cynically review content and produce findings</objective>
 
   <inputs>