mirror of
https://github.com/bmad-code-org/BMAD-METHOD.git
synced 2026-01-30 04:32:02 +00:00
refactor: rename create-tech-spec to quick-spec for QuickFlow branding (#1290)
This commit is contained in:
@@ -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
|
||||
|
||||
@@ -173,7 +173,7 @@ Fast solo development without handoffs.
|
||||
- Code review
|
||||
|
||||
**Key Workflows:**
|
||||
- `*create-tech-spec`
|
||||
- `*quick-spec`
|
||||
- `*quick-dev`
|
||||
- `*code-review`
|
||||
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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 |
|
||||
|
||||
@@ -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
|
||||
|
||||
@@ -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
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: "How to Create a Tech Spec"
|
||||
description: How to create a technical specification using Quick Spec Flow
|
||||
title: "How to Use Quick Spec"
|
||||
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:
|
||||
@@ -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
|
||||
|
||||
|
||||
Reference in New Issue
Block a user