bmad-quick-dev

Implement user intent into code changes, specs, and review artifacts.

1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/mol4/BMAD-Board --skill bmad-quick-dev-mol4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-quick-dev
Source: https://github.com/mol4/BMAD-Board/tree/main/BMAD%20board/.agents/skills/bmad-quick-dev
Command: npx skills add https://github.com/mol4/BMAD-Board --skill bmad-quick-dev-mol4

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns clarified user intent into clean, reviewable code changes without skipping planning, validation, or project conventions. It helps when you need to build, fix, refactor, tweak, or extend a feature while keeping the work aligned with the existing codebase.

Core Features & Use Cases

  • Implementation workflow: Plans, implements, reviews, and presents changes in a disciplined sequence.
  • Spec-driven delivery: Produces ready-for-development specs, preserves frozen intent, and tracks task completion.
  • Safe project updates: Syncs sprint status, respects branch and version-control checks, and supports review loops before completion.
  • Use case: A developer needs to add a new UI feature, update supporting tests, and generate the review trail needed for human approval.

Quick Start

Ask the bmad-quick-dev skill to implement the requested change while following the project’s existing architecture, conventions, and review 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 generate review-ready code changes for a new feature?

To produce review-ready code changes, this Skill implements user intent through a disciplined sequence of planning, coding, and validation. It generates production-ready modifications alongside review artifacts needed for human approval.

What is spec-driven development and how does it preserve frozen intent during implementation?

Spec-driven development produces ready-for-development specs that track task completion. It preserves frozen intent by enforcing strict adherence to acceptance criteria and path-safe documentation throughout the modification workflow.

How do I manage sprint status updates when completing a bug fix or refactor?

To manage sprint status updates, this Skill syncs project status after implementing bug fixes or refactors. It respects branch and version-control checks while supporting review loops before final completion.

Can I use this workflow for targeted code modifications across existing project files?

Yes, you can use this workflow for targeted modifications across project files. It applies path-safe documentation and workflow state management to ensure changes remain consistent with existing architecture.

What is the best way to ensure code review artifacts match the original acceptance criteria?

The best way to ensure review artifacts match acceptance criteria is enforcing frozen intent throughout development. This Skill validates implementations against original specs and presents review-ready changes for approval.

When should I not use an automated implementation workflow for code changes?

You should not use an automated implementation workflow when changes lack clearly defined acceptance criteria or frozen intent. The process requires strict adherence to specs and path-safe documentation to preserve project safety.