mb-lead-dev

Decompose technical tasks into function-level implementation tasks with API contracts and dependency ordering.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Yanick-mj/mb-framework --skill mb-lead-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mb-lead-dev
Source: https://github.com/Yanick-mj/mb-framework/tree/main/agents/lead-dev
Command: npx skills add https://github.com/Yanick-mj/mb-framework --skill mb-lead-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The lead developer Skill prevents integration faults, missing contracts, and hidden dependencies by converting high-level plans into exhaustive, function-level implementation tasks and by validating completed work against the original plan and acceptance criteria.

Core Features & Use Cases

  • Map execution flows with decision gates and identify blocking conditions before any destructive actions occur.
  • Produce a function inventory and ordered task list that assigns work to backend and frontend agents with explicit API contracts.
  • Review implemented changes for contract compliance, cross-stack consistency, AC coverage, and edge case handling.
  • Use Case: Given an architect's plan to add a new feature, generate a complete tech breakdown, list blockers and required migrations, and verify that completed PRs match the agreed contracts.

Quick Start

Ask the lead developer to produce a function-level tech breakdown by providing the task, the architect's plan, context, and the phase set to breakdown or review.

Frequently Asked Questions about mb-lead-dev

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

FAQPage Schema
How do I decompose technical tasks into function-level implementation steps?

To decompose technical tasks, you validate the high-level architect plan and convert it into exhaustive, function-level implementation steps. This process produces an ordered task list with explicit API contracts and dependency mapping for cross-stack development.

What is a tech breakdown for cross-stack development?

A tech breakdown for cross-stack development is a function inventory that assigns work to backend and frontend agents. It defines explicit API contracts, ordered task dependencies, and blocking gate definitions before any destructive actions occur.

How do I review code for API contract compliance and cross-stack consistency?

You review code for API contract compliance by validating implemented changes against the original plan and acceptance criteria. This checks cross-stack consistency, edge case handling, and verifies that completed PRs match the agreed contracts.

How do I identify blocking conditions and decision gates before implementing a feature?

Identify blocking conditions by mapping execution flows with decision gates during the tech breakdown phase. This process highlights blockers, required migrations, and dependencies before assigning work to backend and frontend agents.

Can I use this to verify acceptance criteria coverage for completed PRs?

Yes, you can verify acceptance criteria coverage by reviewing implemented changes during the review phase. It validates that completed PRs match agreed contracts, ensures edge case handling, and checks cross-stack consistency against original requirements.

What do I need to provide to generate a complete tech breakdown and list blockers?

To generate a complete tech breakdown and list blockers, you need to provide the task, the architect's plan, context, and the phase set to breakdown or review. This input produces function-level tasks and identifies required migrations.