lean-build

juliusbrussee/caveman/lean-build

This skill is for feature work with high overbuilding risk. Use it for new behavior, product slices, or integrations where repository reuse, strict scope, and an explicit stop condition matter. It maintains Native Core's architecture-first simplicity, turning features into complete narrow outcomes that fit the system. Derive observable acceptance and explicit non-goals from the request and repository. Trace entry points through layers that own invariants, delivering coherent end-to-end paths across responsible layers. Reuse fitting seams and refactor when patching duplicates behavior, weakens ownership, or hides root causes. Omit modes, providers, config, extensibility, and polish unless acceptance requires them. Keep work runnable and preserve Core safety. Exercise the path, run focused proof, stop when acceptance passes, and report only material omissions and triggers.

설치 수 · 1,232출처 보기

Installation

npx skills add https://github.com/juliusbrussee/caveman --skill lean-build

스킬 파일

SKILL.md

최근 동기화 · 2026. 10. 22.

agents/openai.yaml›

interface:
  display_name: "Lean Build"
  short_description: "Build smallest coherent feature slice"
  default_prompt: "Use $lean-build to implement this feature without speculative scope."

SKILL.md›

---
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.