Back to skills

Agent Skill

Lean Build

lean-build

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.

JuliusbrusseeGeneralGoAiAnthropicCavemanClaudeClaude-codeLlmMemePrompt-engineeringSkillTokens

60K installs

juliusbrussee/caveman

by Juliusbrussee

Score

8.5

/ 10

Installs

60K

Repo Stars

106.8K

Last Updated

0d ago

Fresh

Quality Ratio

86%

Description

Verified

Language

Go

First Published

Aug 2026

Summary

The Lean Build agent skill guides agents to develop new features or product slices by focusing on a narrow outcome and minimizing the risk of overbuilding. It particularly benefits developers working on new behaviors or integrations in mature systems, where maintaining strict scope and architectural consistency is crucial. This agent skill is in the tier of skills with 12K installs. It instructs the agent to derive observable acceptance and explicit non-goals from the request, delivering a coherent end-to-end path across responsible architectural layers without forcing changes into single files. The skill emphasizes reusing existing "seams" and only refactoring when necessary, while also guiding the omission of unnecessary modes, providers, or extensibility unless critical for acceptance.

Skill Definition

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.

How to Use

Use in O-mega

Claude Code

npx skills add juliusbrussee/caveman lean-build
Lean Build | Agent Skills | o-mega