bmad-quick-dev

Automates user intents into production-ready code artifacts aligned with project architecture.

3|2|Updated Mar 29, 2024

Search Tags:#dev-workflow #spec-to-implementation #review-process #sprint-status #code-artifacts #llm-assisted

Ready to run

npx skills add https://github.com/josemariafs/MVTools --skill bmad-quick-dev-josemariafs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-quick-dev
Source: https://github.com/josemariafs/MVTools/tree/main/.cursor/skills/bmad-quick-dev
Command: npx skills add https://github.com/josemariafs/MVTools --skill bmad-quick-dev-josemariafs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly transforms user intents, requirements, stories, bugs, or change requests into clean, ready-to-ship code artifacts that align with the project's architecture, patterns, and conventions.

Core Features & Use Cases

Translates high-level intents into concrete code artifacts (modules, components, tests) that follow existing architecture and style guides.
Generates scaffolding and integration pieces that fit current repositories, enabling faster review and integration.
Use Case: A developer requests a new feature; the skill outputs a ready-to-ship artifact that adheres to the project's conventions, ready for review.

Quick Start

Follow the intent guide to describe the requested change; the agent will produce a ready-to-build artifact and guide the next steps.

Frequently Asked Questions about bmad-quick-dev

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

FAQPage Schema

How do I turn intent into production-ready code that matches existing architecture?▼

You can turn intents into production-ready code by describing the requested change, and the agent generates artifacts that align with your project's architecture, patterns, and conventions for immediate review.

Can I generate code artifacts for bug fixes and refactors using LLM-assisted development?▼

Yes, LLM-assisted development applies across bug fixes, feature requests, refactors, and changes, tailoring the generated code artifacts to fit the existing codebase and style guidelines.

What's the best way to ensure generated code follows my project's conventions and style?▼

The best way to ensure compliance is to use an automated process that enforces architectural rules, ensuring testability, reviewability, and consistent style across all generated code artifacts.

How do I start a spec-to-implementation workflow for new feature requests?▼

To start spec-to-implementation, follow the intent guide to describe the requested change; the agent produces a ready-to-build artifact and guides you through the next steps for integration.

Does this code generation process work with existing repositories and patterns?▼

Yes, the process generates scaffolding and integration pieces that fit current repositories, enabling faster review and integration while adhering to existing project patterns.

What are the limitations of automated code generation for complex architectural changes?▼

Automated code generation requires clear intent descriptions to produce accurate artifacts, and while it enforces compliance, complex architectural changes may still need manual review to ensure proper integration.