bmad-quick-dev

Automate end-to-end implementation of quick tech specs in a guided workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates a rapid, end-to-end implementation flow driven by a quick tech spec or direct user instructions, reducing time-to-value for small changes.

Core Features & Use Cases

  • Guided multi-step workflow from mode detection to self-check, ensuring consistent execution.
  • Tech-spec or direct modes with escalation handling to match user intent and project scope.
  • Automated context gathering and execution loop that updates baseline state and validates outcomes.

Quick Start

Run the Quick Dev workflow to implement the supplied tech spec and progress the feature end-to-end.

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 end-to-end implementation of a quick tech spec?

You can automate implementation of a quick tech spec using a guided workflow that handles mode detection, context gathering, execution, adversarial review, and self-checks to ship small feature changes fast.

What is the best way to execute small feature changes with clear acceptance criteria?

Executing small feature changes with clear acceptance criteria is best handled by an automated workflow that progresses end-to-end from mode detection to self-check, reducing time-to-value and ensuring consistent execution.

Can I implement code directly from instructions instead of writing a tech spec?

Yes, you can implement code directly from instructions using the tech-spec or direct modes, which include escalation handling to match user intent and project scope without a formal tech spec.

How does adversarial review work in an automated feature execution loop?

Adversarial review in an automated execution loop validates outcomes and updates baseline state after context gathering, ensuring the implemented feature satisfies requirements through a self-check mechanism.

When should I escalate a small feature change instead of using quick dev automation?

You should escalate a small feature change when the project scope exceeds the boundaries of quick tech specs, triggering the workflow's escalation handling to match user intent with a more appropriate execution path.