lean-build

Implements narrow feature slices with explicit acceptance criteria and stop conditions.

1|Updated Aug 31, 2026
One-click install
npx skills add https://github.com/nguyenhungtran18/skill-and-tool-tracker --skill lean-build-nguyenhungtran18
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lean-build
Source: https://github.com/nguyenhungtran18/skill-and-tool-tracker/tree/main/skills/lean-build
Command: npx skills add https://github.com/nguyenhungtran18/skill-and-tool-tracker --skill lean-build-nguyenhungtran18

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Feature work often balloons into overbuilt implementations with speculative modes, providers, and configuration that nobody asked for. This Skill constrains AI-driven feature development to the smallest coherent end-to-end slice that satisfies observable acceptance criteria. ## Core Features & Use Cases - Scope Discipline: Derives explicit acceptance criteria and non-goals from the request and repository before writing code. - Architecture-First Delivery: Traces the entry point through the layers that own invariants, delivering a coherent path across responsible layers rather than a local patch. - Reuse and Refactor Judgment: Reuses fitting seams and refactors only when patching would duplicate behavior, weaken ownership, or hide root causes. - Use Case: When adding a new API endpoint to an existing service, the Skill implements only the required path through routing, domain, and persistence layers, omits speculative configuration, runs a focused proof, and stops once acceptance passes. ## Quick Start Use $lean-build to implement this feature without speculative scope.

Frequently Asked Questions about lean-build

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

FAQPage Schema
How do I prevent an AI coding agent from overbuilding a feature?▼

Define observable acceptance criteria and explicit non-goals before implementation, then instruct the agent to stop when acceptance passes. This Skill enforces that workflow by omitting modes, providers, config, and polish unless acceptance requires them.

How to implement a minimal feature slice across multiple layers?▼

Trace the entry point through the layers that own invariants and deliver a coherent end-to-end path across those responsible layers. Avoid forcing the work into one file or a local patch that bypasses ownership boundaries.

When should I refactor versus patch during feature work?▼

Refactor when patching would duplicate behavior, weaken ownership, or hide the root cause. Otherwise reuse the fitting existing seam and keep the change narrow and runnable.

When is lean-build not the right approach?▼

It is not suited for exploratory prototyping, broad architectural redesigns, or work where extensibility and configuration are themselves the requirement. It targets features with high overbuilding risk and clear acceptance conditions.

Does lean-build work with any programming language or framework?▼

Yes, it is a language-agnostic methodology skill with no runtime dependencies. It operates as prompt instructions that guide feature implementation within any repository structure.