bmad-quick-dev

Executes tech-spec-driven implementation workflows for small software changes with structured steps and escalation.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/imonmi/INTER-EDU --skill bmad-quick-dev-imonmi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-quick-dev
Source: https://github.com/imonmi/INTER-EDU/tree/main/_bmad/bmm/workflows/bmad-quick-flow/bmad-quick-dev
Command: npx skills add https://github.com/imonmi/INTER-EDU --skill bmad-quick-dev-imonmi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow solves the bottleneck of delivering small software changes by providing a fast, guided process that converts a tech-spec or direct instruction into a structured, step-by-step implementation plan.

Core Features & Use Cases

  • Deterministic step-file execution; each step loads fresh to prevent drift and preserves state through variables.
  • Flexible mode handling; supports both tech-spec-driven execution and direct instruction with escalation pathways.
  • Context-aware execution; loads project context when available and uses baseline commit tracking for reproducibility.
  • End-to-end workflow; covers initialization, execution, review, and adversarial resolution for rapid delivery.

Quick Start

Load a tech-spec path or provide direct task instructions and run the Quick Dev workflow to begin step-01 mode detection.

Frequently Asked Questions about bmad-quick-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate the implementation of small software changes from a tech spec?

You can automate small software changes by loading a tech spec into this guided workflow, which maps your input into a deterministic, step-by-step execution plan. It handles mode detection, execution, and final validation to ship small changes fast.

What is the best way to execute a structured development workflow without context drift?

Executing a structured development workflow without drift requires deterministic step-file execution. This process loads each step fresh, preserves state through variables, and loads available project context to maintain reproducibility throughout the task.

Can I run quick code changes using direct instructions instead of a formal tech spec?

Yes, you can run quick code changes using direct instructions. The workflow supports flexible mode handling that processes direct tasks and includes escalation pathways to automatically transition scope that exceeds simple changes.

Does this rapid development workflow include automated code review and validation?

This rapid development workflow includes end-to-end validation by running an adversarial review and self-check after execution. It performs final validation before delivery to ensure the structured implementation meets the required standards.

When should I escalate a task out of a quick dev execution flow?

You should escalate a task out of this quick dev execution flow when the scope exceeds simple changes. The workflow automatically detects this during mode detection and escalates the implementation to prevent bottlenecks in rapid delivery.

How does baseline commit tracking work during context-aware code execution?

Baseline commit tracking during context-aware code execution anchors the workflow to a specific repository state. It loads available project context and preserves execution variables to ensure reproducibility across each structured step.