lean-build
This skill is used for feature work with high overbuilding risk. It derives observable acceptance criteria and explicit non-goals from the request and repository, traces entry points through layers owning invariants, and reuses fitting seams to deliver a coherent end-to-end path. It helps developers maintain strict scope and an explicit stop condition, preventing over-engineering and improving delivery speed and code quality.
npx skills add https://github.com/juliusbrussee/caveman --skill lean-buildBefore / After Comparison
2 组Without this skill, developers tackling high-overbuilding-risk features often lack clear scope boundaries, constantly adding modes, configurations, and extension points, which lengthens delivery time and increases codebase complexity.
This skill derives observable acceptance criteria and explicit non-goals from the request and repository, and reuses fitting seams, making feature delivery focus on the necessary path, significantly shortening delivery time and keeping the system clean.
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.
User Reviews (0)
Write a Review
No reviews yet
Statistics
User Rating
Rate this Skill