bmild-dev

Implement planned BMILD Slices, fix bugs, and build prototypes.

3|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/micfre/BMILD --skill bmild-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmild-dev
Source: https://github.com/micfre/BMILD/tree/main/.agents/skills/bmild-dev
Command: npx skills add https://github.com/micfre/BMILD --skill bmild-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When working with the BMILD spec-driven development framework, you need a reliable senior engineer persona to implement planned Slices, fix production bugs, and build small prototypes while strictly adhering to your repository's existing conventions, design contracts, and quality standards — without unnecessary ceremony or scope creep.

Core Features & Use Cases

  • Slice Implementation: Executes planned BMILD Slices per signed design contracts and acceptance criteria, updating all required planning artifacts and verification matrices.
  • Bug Fixing: Investigates and fixes localized production bugs with minimal, targeted changes and regression tests to prevent recurrence.
  • Prototype Development: Builds bounded, throwaway or exploratory prototypes and small features outside formal Slices, matching existing repo patterns.
  • Use Case: If you have a planned Slice to add user profile editing, a bug where the settings page crashes on null input, or a small prototype for a new notification system, this skill handles the implementation while following your repo's standards.

Quick Start

Use the bmild-dev skill to implement the planned Slice for adding user profile editing, fix the bug where the settings page crashes on null input, or build a small prototype for the new notification system.

Frequently Asked Questions about bmild-dev

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

FAQPage Schema
How do I implement planned Slices using spec-driven development?

Implementing planned Slices requires executing design contracts and acceptance criteria while updating verification matrices. This approach enforces repository conventions and produces minimal, verifiable code changes with appropriate quality gates.

What is the best way to fix production bugs with regression testing?

Fixing production bugs with regression testing involves making localized, targeted changes to the codebase and adding tests to prevent recurrence. This ensures minimal scope creep while strictly adhering to existing repository conventions.

How do I build bounded prototypes without violating existing code conventions?

Building bounded prototypes without violating code conventions requires matching existing repository patterns during development. This process creates exploratory features outside formal planning artifacts while maintaining adherence to design contracts.

Can I execute Slice implementation tasks outside of formal planning artifacts?

Yes, you can execute small feature or prototype work outside formal planning artifacts. This includes building bounded, exploratory prototypes that match existing repo patterns without requiring signed design contracts.

When do I need spec-driven development for bug fixing and feature work?

You need spec-driven development for bug fixing and feature work when your repository requires strict adherence to design contracts and contributor guidelines. It ensures minimal, verifiable changes with appropriate quality gates and artifact updates.

Why does Slice implementation require updating verification matrices?

Slice implementation requires updating verification matrices to maintain adherence to signed design contracts and acceptance criteria. This ensures all required planning artifacts reflect the minimal, verifiable changes made during execution.