skills.rest
MazenMrad
MazenMradCOMMUNITY
Explore all skills by this author →
GitHub

bmad-quick-dev

Translate user intent into architecture-aligned code artifacts via the BMAD workflow.

1|Updated Aug 3, 2025
Search Tags:#workflow#planning#architecture#spec#generate#code-artifacts
One-click install
npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-quick-dev-mazenmrad
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-quick-dev
Source: https://github.com/MazenMrad/Obsidio/tree/main/.cursor/skills/bmad-quick-dev
Command: npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-quick-dev-mazenmrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implements a rapid-development workflow that translates user intent (e.g., feature, bug fix, refactor) into clean, architecture-aligned code artifacts that follow the project's existing conventions and patterns.

Core Features & Use Cases

  • Automatically generates code artifacts that adhere to the project's architecture, styles, and templates.
  • Supports planning, specification, and traceability by producing spec-driven outputs that can drive PRs and reviews.
  • Facilitates quick iteration: create, plan, implement, review, and present changes within the BMAD workflow.

Quick Start

Provide the user’s intent and let the skill generate a clean, architecture-compliant code artifact that fits the project conventions.

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 production-ready code that matches existing project architecture?▼

To generate production-ready code aligned with your architecture, provide your feature or refactor intent to trigger a workflow that produces spec-driven artifacts following your project's conventions, styles, and structural patterns.

What is a spec-driven workflow for code generation?▼

A spec-driven workflow translates user intent into code artifacts using a strict spec pipeline, requiring frontmatter-driven metadata, task lists, and traceable changes maintained within a single spec file per modification.

How do I plan and implement bug fixes without breaking existing architectural patterns?▼

Plan and implement bug fixes by passing the intent through a structured pipeline that generates architecture-compliant code artifacts, ensuring changes are traceable and aligned with existing project styles and templates.

Can I use this workflow to iterate quickly from planning to code review?▼

Yes, you can iterate quickly by using the workflow to create, plan, implement, review, and present changes. It outputs spec-driven artifacts designed to drive pull requests and facilitate code reviews.

Do I need to define metadata and task lists to generate code artifacts?▼

Yes, the workflow requires strict adherence to a spec pipeline that includes frontmatter-driven metadata and task lists to ensure all generated code changes are fully traceable within a single spec file.

What is the best way to ensure code refactoring follows project conventions?▼

The best way to ensure refactoring follows conventions is to use a workflow that automatically generates code artifacts adhering to the project's existing architecture, styles, and templates based on your refactor intent.

Related Skills

Explore More Software Engineering Skills→
sejassejas
2

intent-start

Guide spec-driven development intent creation with structured spec and notes files.

Community
Intermediate
salazarsebassalazarsebas
9

code-review

Identify code changes and assess them with layered adversarial reviews.

Community
Advanced
civictechdccivictechdc
1

python-code-style

Enforce Python linting, formatting, naming, and docstring standards with Ruff and MyPy.

Official
Intermediate
Sir-chawakornSir-chawakorn
33

code-generation

Generate React components, Next.js API routes, and project templates.

Community
Intermediate