bmad-quick-dev

Automate end-to-end rapid development from tech-specs or direct instructions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? This Skill automates the end-to-end Quick Dev workflow so teams can implement quick tech specs or direct instructions efficiently without losing track.

## Core Features & Use Cases

  • Step-file architecture provides isolated steps to keep progress deterministic and auditable.
  • Mode detection & escalation handles tech-spec vs direct input and guides next steps with explicit NEXT directives.
  • End-to-end execution loop covers context gathering, implementation, testing, self-check, and adversarial review for a production-ready release.

### Quick Start Provide a tech-spec path or a direct task description to initiate the Quick Dev workflow.

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 rapid development sprints from a tech spec?

You can automate rapid development sprints by loading a tech spec or direct instructions to initiate a step-based workflow that gathers context, executes changes, runs tests, and conducts an adversarial review.

What is an adversarial review in a quick-dev workflow?

An adversarial review is a lifecycle step that critically evaluates the completed implementation and self-checks to ensure production-ready delivery before finalizing the quick-dev sprint.

How do I execute direct instructions without a full tech spec?

You can execute direct instructions by providing a task description instead of a tech spec path; the workflow detects the input mode and guides the subsequent execution and testing steps.

Does this automated workflow require external dependencies to run?

No external dependencies are required to run the workflow, as it operates independently to load project context, implement changes, and manage the end-to-end lifecycle.

What is the best way to track progress during an automated implementation?

The best way to track progress is through its step-file architecture, which provides isolated steps to keep the implementation deterministic and fully auditable throughout the execution loop.