Lean Build

by juliusbrussee2e08b9177c07No licenseListed Oct 8, 2026Updated Oct 8, 2026

Build feature work with high overbuilding risk. Use for new behavior, product slices, or integrations where repository reuse, strict scope, and an explicit stop condition matter.

Instructions onlySoftware Development
AI-generated overview

Guides feature implementation with strict scope, repository reuse, and an explicit stop condition to avoid overbuilding.

What it does
Provides a lean-build procedure for turning a feature request into a narrow, complete, end-to-end outcome that fits the existing system. It directs deriving observable acceptance criteria and non-goals, tracing entry points through the layers that own invariants, reusing fitting seams, and refactoring when patching would duplicate behavior or hide root causes. It also limits added modes, providers, config, dependencies, services, and migrations unless acceptance or lifecycle design requires them, and it ends with running focused proof and reporting only material omissions.
When to use it
Use for new behavior, product slices, or integrations where overbuilding risk is high. It fits work that needs repository reuse, strict scope control, and a clear stopping point.
Requirements
Instructions only; no scripts are included. It assumes access to the target repository and the ability to run focused proof.

Lean build

Native Core's architecture-first simplicity remains mandatory. Turn feature into complete narrow outcome fitting system.

  • Derive observable acceptance and explicit non-goals from request and repository.
  • Trace entry point through layers owning invariants.
  • Deliver coherent end-to-end path across responsible layers; never force work into one file, direct expression, or local patch.
  • Reuse fitting seam. Refactor when patching duplicates behavior, weakens ownership, or hides root cause.
  • Omit modes, providers, config, extensibility, and polish unless acceptance needs them.
  • Add surface, dependency, service, config, or migration only for lifecycle design or acceptance; state material tradeoff.
  • Keep work runnable; preserve Core safety.

Exercise path. Run focused proof. Stop when acceptance passes. Report only material omissions and trigger.

Source and attribution

Source:juliusbrussee/cavemaninskills/lean-buildat commit2e08b91

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal