refactor: rename create-tech-spec to quick-spec for QuickFlow branding (#1290)

docs/explanation/agents/barry-quick-flow.md

@@ -37,9 +37,9 @@ Barry is the elite solo developer who lives and breathes the BMad Quick Flow wor
 
 Barry owns the entire BMad Quick Flow path, providing a streamlined 3-step development process that eliminates handoffs and maximizes velocity.
 
-### 1. **create-tech-spec**
+### 1. **quick-spec**
 
-- **Workflow:** `_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml`
+- **Workflow:** `_bmad/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md`
 - **Description:** Architect a technical spec with implementation-ready stories
 - **Use when:** You need to transform requirements into a buildable spec
 
@@ -89,7 +89,7 @@ Barry orchestrates a simple, efficient 3-step process:
 
 ```mermaid
 flowchart LR
-    A[Requirements] --> B[create-tech-spec]
+    A[Requirements] --> B[quick-spec]
     B --> C[Tech Spec]
     C --> D[quick-dev]
     D --> E[Implementation]
@@ -107,7 +107,7 @@ flowchart LR
     style H fill:#e0f2f1
 ```
 
-### Step 1: Technical Specification (`create-tech-spec`)
+### Step 1: Technical Specification (`quick-spec`)
 
 **Goal:** Transform user requirements into implementation-ready technical specifications
 
@@ -237,7 +237,7 @@ In party mode, Barry often acts as:
 /bmad:bmm:agents:quick-flow-solo-dev
 
 # Create a tech spec
-> create-tech-spec
+> quick-spec
 
 # Quick implementation
 > quick-dev tech-spec-auth.md

docs/explanation/core-concepts/agent-roles.md

@@ -173,7 +173,7 @@ Fast solo development without handoffs.
 - Code review
 
 **Key Workflows:**
-- `*create-tech-spec`
+- `*quick-spec`
 - `*quick-dev`
 - `*code-review`
 

docs/explanation/features/quick-flow.md

@@ -164,6 +164,6 @@ Start with Quick Flow, but switch to BMad Method when:
 
 ## Related
 
-- [Create Tech Spec](/docs/how-to/workflows/create-tech-spec.md) - How to use Quick Flow
+- [Quick Spec](/docs/how-to/workflows/quick-spec.md) - How to use Quick Flow
 - [Quick Start Guide](/docs/tutorials/getting-started/getting-started-bmadv6.md) - Getting started
 - [Four Phases](/docs/explanation/architecture/four-phases.md) - Understanding the full methodology

docs/explanation/game-dev/agents.md

@@ -303,7 +303,7 @@ Direct, confident, and gameplay-focused. Uses dev slang, thinks in game feel and
 | ------------------ | ------------------------------------------------------ |
 | `quick-prototype`  | Rapid prototype to test if a mechanic is fun           |
 | `quick-dev`        | Implement features end-to-end with game considerations |
-| `create-tech-spec` | Create implementation-ready technical spec             |
+| `quick-spec`       | Create implementation-ready technical spec             |
 | `code-review`      | Review code quality                                    |
 | `test-framework`   | Set up automated testing                               |
 | `party-mode`       | Bring in specialists when needed                       |

docs/how-to/get-answers-about-bmad.md

@@ -10,7 +10,7 @@ Point an LLM at BMad's source files and ask your question. That's the technique
 :::note[Example]
 **Q:** "Tell me the fastest way to build something with BMad"
 
-**A:** Use Quick Flow: Run `create-tech-spec` to write a technical specification, then `quick-dev` to implement it—skipping the full planning phases. This gets small features shipped in a single focused session instead of going through the full 4-phase BMM workflow.
+**A:** Use Quick Flow: Run `quick-spec` to write a technical specification, then `quick-dev` to implement it—skipping the full planning phases. This gets small features shipped in a single focused session instead of going through the full 4-phase BMM workflow.
 :::
 
 ## Why This Works

docs/how-to/workflows/bmgd-quick-flow.md

@@ -17,7 +17,7 @@ The Game Solo Dev agent includes:
 
 - `quick-prototype` - Rapid mechanic testing
 - `quick-dev` - Flexible feature implementation
-- `create-tech-spec` - Create implementation-ready specs
+- `quick-spec` - Create implementation-ready specs
 - `code-review` - Quality checks
 - `test-framework` - Automated testing setup
 

docs/how-to/workflows/quick-spec.md

@@ -1,6 +1,6 @@
 ---
-title: "How to Create a Tech Spec"
+title: "How to Use Quick Spec"
-description: How to create a technical specification using Quick Spec Flow
+description: How to create a technical specification using Quick Spec workflow
 ---
 
 
@@ -35,7 +35,7 @@ Start a fresh chat and load the PM agent (or Quick Flow Solo Dev agent).
 ### 2. Run the Tech Spec Workflow
 
 ```
-*create-tech-spec
+*quick-spec
 ```
 
 Or simply describe what you want to build:

docs/reference/agents/index.md

@@ -75,7 +75,7 @@ Story implementation and code review.
 Fast solo development without handoffs.
 
 **Commands:**
-- `*create-tech-spec` - Architect technical spec with implementation-ready stories
+- `*quick-spec` - Architect technical spec with implementation-ready stories
 - `*quick-dev` - Implement tech spec end-to-end solo
 - `*code-review` - Review and improve code
 

src/modules/bmgd/agents/game-solo-dev.agent.yaml

@@ -36,7 +36,7 @@ agent:
       description: "[QD] Implement features end-to-end solo with game-specific considerations"
 
     - trigger: TS or fuzzy match on tech-spec
-      workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/create-tech-spec/workflow.yaml"
+      workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-spec/workflow.yaml"
       description: "[TS] Architect a technical spec with implementation-ready stories"
 
     - trigger: CR or fuzzy match on code-review

src/modules/bmgd/workflows/bmgd-quick-flow/quick-spec/workflow.yaml

@@ -1,5 +1,5 @@
 # Quick-Flow: Create Tech-Spec (Game Development)
-name: create-tech-spec
+name: quick-spec
 description: "Conversational spec engineering for games - ask questions, investigate code, produce implementation-ready tech-spec."
 author: "BMad"
 
@@ -14,7 +14,7 @@ user_skill_level: "{config_source}:game_dev_experience"
 date: system-generated
 
 # Workflow components
-installed_path: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/create-tech-spec"
+installed_path: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-spec"
 instructions: "{installed_path}/instructions.md"
 
 # Related workflows

src/modules/bmgd/workflows/workflow-status/paths/quickflow-brownfield.yaml

@@ -11,10 +11,10 @@ phases:
     name: "Planning"
     required: true
     workflows:
-      - id: "create-tech-spec"
+      - id: "quick-spec"
         required: true
         agent: "game-solo-dev"
-        command: "create-tech-spec"
+        command: "quick-spec"
         output: "Technical specification"
         note: "Define changes for existing codebase"
 

src/modules/bmm/agents/quick-flow-solo-dev.agent.yaml

@@ -20,7 +20,7 @@ agent:
 
   menu:
     - trigger: TS or fuzzy match on tech-spec
-      exec: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.md"
+      exec: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md"
       description: "[TS] Architect a technical spec with implementation-ready stories (Required first step)"
 
     - trigger: QD or fuzzy match on quick-dev

src/modules/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-01-mode-detection.md

@@ -95,7 +95,7 @@ Present choice:
 **[e] Execute directly** - Start now
 ```
 
-- **[t]:** Direct user to `{create_tech_spec_workflow}`. **EXIT Quick Dev.**
+- **[t]:** Direct user to `{quick_spec_workflow}`. **EXIT Quick Dev.**
 - **[e]:** Ask for any additional guidance, then **NEXT:** Load `step-02-context-gathering.md`
 
 ### Escalation Triggered - Level 0-2
@@ -108,7 +108,7 @@ This looks like a focused feature with multiple components.
 **[e] Execute directly**
 ```
 
-- **[t]:** Direct to `{create_tech_spec_workflow}`. **EXIT Quick Dev.**
+- **[t]:** Direct to `{quick_spec_workflow}`. **EXIT Quick Dev.**
 - **[w]:** Direct to `{workflow_init}`. **EXIT Quick Dev.**
 - **[e]:** Ask for guidance, then **NEXT:** Load `step-02-context-gathering.md`
 
@@ -123,7 +123,7 @@ This sounds like platform/system work.
 ```
 
 - **[w]:** Direct to `{workflow_init}`. **EXIT Quick Dev.**
-- **[t]:** Direct to `{create_tech_spec_workflow}`. **EXIT Quick Dev.**
+- **[t]:** Direct to `{quick_spec_workflow}`. **EXIT Quick Dev.**
 - **[e]:** Ask for guidance, then **NEXT:** Load `step-02-context-gathering.md`
 
 ---

src/modules/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md

@@ -40,7 +40,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 
 ### Related Workflows
 
-- `create_tech_spec_workflow` = `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml`
+- `quick_spec_workflow` = `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md`
 - `workflow_init` = `{project-root}/_bmad/bmm/workflows/workflow-status/init/workflow.yaml`
 - `party_mode_exec` = `{project-root}/_bmad/core/workflows/party-mode/workflow.md`
 - `advanced_elicitation` = `{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml`

src/modules/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-01-understand.md

@@ -2,7 +2,7 @@
 name: 'step-01-understand'
 description: 'Analyze the requirement delta between current state and what user wants to build'
 
-workflow_path: '{project-root}/_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec'
+workflow_path: '{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-spec'
 nextStepFile: '{workflow_path}/steps/step-02-investigate.md'
 skipToStepFile: '{workflow_path}/steps/step-03-generate.md'
 templateFile: '{workflow_path}/tech-spec-template.md'

src/modules/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-02-investigate.md

@@ -2,7 +2,7 @@
 name: 'step-02-investigate'
 description: 'Map technical constraints and anchor points within the codebase'
 
-workflow_path: '{project-root}/_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec'
+workflow_path: '{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-spec'
 nextStepFile: '{workflow_path}/steps/step-03-generate.md'
 wipFile: '{implementation_artifacts}/tech-spec-wip.md'
 ---

src/modules/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-03-generate.md

@@ -2,7 +2,7 @@
 name: 'step-03-generate'
 description: 'Build the implementation plan based on the technical mapping of constraints'
 
-workflow_path: '{project-root}/_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec'
+workflow_path: '{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-spec'
 nextStepFile: '{workflow_path}/steps/step-04-review.md'
 wipFile: '{implementation_artifacts}/tech-spec-wip.md'
 ---

src/modules/bmm/workflows/bmad-quick-flow/quick-spec/steps/step-04-review.md

@@ -2,7 +2,7 @@
 name: 'step-04-review'
 description: 'Review and finalize the tech-spec'
 
-workflow_path: '{project-root}/_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec'
+workflow_path: '{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-spec'
 wipFile: '{implementation_artifacts}/tech-spec-wip.md'
 ---
 

src/modules/bmm/workflows/bmad-quick-flow/quick-spec/workflow.md

@@ -1,5 +1,5 @@
 ---
-name: create-tech-spec
+name: quick-spec
 description: Conversational spec engineering - ask questions, investigate code, produce implementation-ready tech-spec.
 main_config: '{project-root}/_bmad/bmm/config.yaml'
 web_bundle: true
@@ -10,7 +10,7 @@ party_mode_exec: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
 quick_dev_workflow: '{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md'
 ---
 
-# Create Tech-Spec Workflow
+# Quick-Spec Workflow
 
 **Goal:** Create implementation-ready technical specifications through conversational discovery, code investigation, and structured documentation.