Overview

Quick Flow is a lean solo-developer workflow that accelerates turning a written spec into implemented features with tests. It follows a three-stage cycle—Quick Spec, Quick Dev, and Code Review—delivering a technical spec, per-story implementations, and a 0-100 multi-dimensional quality score for stakeholder-ready results.

How This Skill Works

Inputs include projectName, projectDescription, techStack (optional), and storyCount (default 5). The process generates a technical specification with architecture decisions, implements each story with tests, and finishes with a multi-dimensional Code Review scoring 0-100. The lifecycle is codified in bmad-quick-flow.js to ensure repeatability.

When to Use It

• Starting a new solo project with tight deadlines.
• Prototyping an MVP with a clear set of user stories.
• When you need architecture decisions documented alongside code.
• Preparing stakeholder-ready summaries from developer work.
• Reviewing code quality with a standardized 0-100 score before demos.

Quick Start

1. Step 1: Provide inputs: projectName, projectDescription, techStack (optional), storyCount.
2. Step 2: Run Quick Spec to generate stories and architecture decisions, then implement each story with tests (Quick Dev).
3. Step 3: Run Code Review to obtain a 0-100 quality score and a stakeholder-ready summary.

Best Practices

• Define clear, testable stories in Quick Spec.
• Set a realistic storyCount default or cap.
• Write tests per story and capture architecture decisions.
• Use multi-dimensional Code Review results to drive improvements.
• Keep outputs and stakeholder summaries up to date.

Example Use Cases

• Solo SaaS MVP delivered in two weeks with documented architecture decisions.
• Prototype internal tooling to automate a repetitive workflow.
• Open-source feature sprint with contributor-friendly specs.
• Client demo-ready prototype with per-story results and QA notes.
• CLI tool kickoff with a captured architecture and review score.

Frequently Asked Questions