Skills juliusbrussee/caveman Caveman
lean-build
- Use it when
- you're adding a feature or an integration and want it complete, but no bigger than what was asked
- It does
- writes down what must work and what's out of scope, reuses the existing code, and leaves out options, config and polish nobody asked for
- You get
- a narrow feature working end to end, tested against what was asked, plus a note of any omission that matters
- Unlike surgical-patch
- which corrects existing behavior in one place, this adds new behavior through all the code involved
- Runs
- on its own, whenever the agent sees a task that fits; it's a short list of rules, not a step-by-step guide
Skill 9 of 12 in the Caveman bundle · Before it: investigate-first · After it: surgical-patch
TLDR
The agent derives acceptance criteria and explicit non-goals from your request and the repository. It follows the feature from where it starts through every part of the code involved and builds one complete path, rather than cramming it into one file or a local patch. It hooks into existing code where that fits, and refactors only when patching would duplicate behavior or blur which code is responsible for what. Extra modes, options, configuration and polish stay out unless the criteria need them, and any new dependency, service or migration needs a stated reason. It runs the new path, runs a focused test, and stops as soon as the criteria pass.
Summarizes the skill at bad48a0.
npx skills add https://github.com/juliusbrussee/caveman --skill lean-buildskills.sh page · Source on GitHub · All skills from juliusbrussee/caveman
- Installs
- 61,411 on skills.sh, Sep 21, 2026
- Repo stars
- 106,976 juliusbrussee/caveman
- First seen
- Aug 11, 2026 on skills.sh
Weekly values
| Week to | Installs |
|---|---|
| Aug 3 | 0 |
| Aug 10 | 0 |
| Aug 17 | 6,249 |
| Aug 24 | 8,836 |
| Aug 31 | 8,946 |
| Sep 7 | 11,043 |
| Sep 14 | 12,451 |
| Sep 21 | 13,111 |
| Category |
Test-first work, implementation from specs, git hygiene and scope control. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
A multi-step process the agent follows: interview, debug, run a TDD loop, review. |
| Effect |
Its own steps create or change files, git state or local tools. |
| Needs |
Instructions only. Works in any agent that supports skills. |
| Publisher |
Everyone else. Unverified vendor claims default to community. |
| Topics |
SKILL.md
From juliusbrussee/caveman at bad48a0. Checked daily, last changed Oct 20, 2026.
Frontmatter
name: lean-build
description: 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.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.