bmild-planner

Transform approved design artifacts into ordered, implementation-ready vertical slices.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill eliminates the manual, error-prone work of sequencing implementation tasks and verifying design coverage for software features, ensuring teams build the right things in the right order without ambiguity-driven rework.

Core Features & Use Cases

  • Design-to-Slice Decomposition: Breaks approved product, UX, and system design artifacts into dependency-safe, vertical implementation slices for MVP or specific project phases.
  • Readiness Verification: Validates that all upstream design inputs are complete and aligned before planning begins, blocking decomposition if gaps exist to prevent costly rework later.
  • Course Correction & Replanning: Handles design changes, execution blockers, and scope shifts by coordinating cross-artifact updates, facilitating roundtable consultations, and routing handoffs to the correct team members.
  • Use Case: For example, if your team has finalized the design for a new user notification system, use this Skill to decompose it into thin, testable slices, verify every PRD requirement is covered, and hand off the first slice to the engineering team for implementation.

Quick Start

Ask the bmild-planner skill to decompose the approved user notification system design into MVP vertical slices and confirm all PRD must-have requirements are fully covered.

Frequently Asked Questions about bmild-planner

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

FAQPage Schema
How do I decompose approved product and UX designs into build-ready vertical slices?

Decomposing approved designs into vertical slices requires sequencing dependency-safe implementation tasks and verifying backward coverage against PRD must-haves, ensuring teams build the right things in the right order without ambiguity-driven rework.

What is spec-driven development planning for feature phases?

Spec-driven development planning transforms approved product, UX, and system design artifacts into ordered, implementation-ready vertical slices, applying dependency-safe work sequencing and token-budgeted slice sizing for MVP or specific project phases.

How do I verify readiness before planning implementation tasks?

Readiness verification validates that all upstream design inputs are complete and aligned before planning begins, blocking decomposition if gaps exist to prevent costly rework later in the spec-driven development workflow.

Can I replan vertical slices if execution blockers or design changes occur?

Replanning for execution blockers or design changes involves coordinating cross-artifact updates, facilitating roundtable consultations, and routing handoffs to the correct team members for effective course correction.

What is the best way to ensure PRD requirements are covered during feature decomposition?

Ensuring PRD coverage during feature decomposition requires backward coverage verification against product requirement must-haves, confirming every approved design artifact is fully accounted for before handing off to engineering.

Does this approach apply to MVP scoping and phase-scoped decomposition?

Yes, applying vertical slicing to MVP scoping and phase-scoped decomposition breaks approved designs into thin, testable slices, verifying readiness and routing coordinated handoffs to implementation personas.