bmad-bmm-quick-dev

Convert brief engineering specs into executable development workflows.

1|1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/LucaDeLeo/ASTN --skill bmad-bmm-quick-dev-lucadeleo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-bmm-quick-dev
Source: https://github.com/LucaDeLeo/ASTN/tree/main/.agents/skills/bmad-bmm-quick-dev
Command: npx skills add https://github.com/LucaDeLeo/ASTN --skill bmad-bmm-quick-dev-lucadeleo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline the initiation and execution of small feature changes by converting quick tech specs into ready-to-follow workflows.

Core Features & Use Cases

  • Generates a concrete, executable workflow from a concise spec.
  • Guides engineers through immediate implementation steps with alignment to project standards.
  • Use case: when a product owner submits a brief enhancement spec, this Skill translates it into an actionable dev plan and start/stop criteria.

Quick Start

Provide a concise quick spec and ask the AI to implement it using the defined workflow.

Frequently Asked Questions about bmad-bmm-quick-dev

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

FAQPage Schema
How do I convert a quick tech spec into an executable development workflow?

To convert a quick tech spec into an executable development workflow, provide the concise spec to the AI. It loads a predefined workflow to translate brief enhancement requests into actionable dev plans with start and stop criteria.

What is the best way to implement small feature changes from brief specs?

Implementing small feature changes from brief specs is best handled by generating a concrete, executable workflow. This approach guides engineers through immediate implementation steps while ensuring alignment with project standards.

Can I use a predefined workflow for rapid and repeatable delivery of engineering tasks?

Yes, you can use a predefined workflow for rapid and repeatable delivery of engineering tasks. It ensures traceability and consistent execution across small features when a product owner submits a brief enhancement spec.

How does a quick development spec workflow ensure traceability during implementation?

A quick development spec workflow ensures traceability by loading and following a strict predefined process. This translates concise specs into actionable plans, guiding engineers step-by-step to maintain consistent execution and clear start and stop criteria.

Does this quick dev workflow require any specific dependencies or environment setup?

No specific dependencies or environment setup are required to use this quick dev workflow. It operates independently to convert concise tech specs into ready-to-follow implementation steps for rapid feature delivery.

When should I not use an automated workflow for spec implementation?

You should not use an automated workflow for spec implementation when dealing with large, complex features outside the scope of quick dev. It is specifically designed for small feature changes requiring rapid, repeatable delivery from brief specs.