Catalog
JuliusBrussee/lean-build

JuliusBrussee

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.

NewUpdated Sep 9, 2026

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.

Files2
2 files · 1.6 KB

Select a file to preview

Overall Score

58/100

Grade

C

Adequate

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

75

Quality

45

Clarity

52

Completeness

48

Summary

Lean Build is a high-level architecture and development methodology skill that guides AI agents to implement feature work by deriving acceptance criteria, tracing system layers, delivering coherent end-to-end paths, and reusing existing seams. It emphasizes constraint-driven development, strict scope boundaries, and explicit stop conditions to prevent overbuilding and maintain architectural coherence.

Detected Capabilities

code analysisarchitecture reasoningscope constraint enforcementrequirement tracingrefactoring guidance

Trigger Keywords

Phrases that agents use to match this skill to user intent.

implement feature slicetrace system layersreuse seamsbounded scope designarchitecture-first build

Use Cases

  • Implement new product features with bounded scope and clear acceptance criteria
  • Design feature slices that fit existing system architecture without speculative extensions
  • Refactor duplicated behavior by identifying and reusing appropriate seams
  • Trace feature requirements through layers to ensure each component has clear ownership
  • Stop implementation at acceptance rather than overbuilding with unnecessary polish or configuration

Quality Notes

  • Skill content is highly abstract and domain-specific (appears tailored to a specific organization's 'Native Core' architecture)
  • Instructions prioritize architectural principles over concrete, step-by-step procedural guidance
  • Language is prescriptive but lacks concrete examples of what successful implementation looks like
  • No explicit error handling or edge case guidance provided
  • Scope is well-bounded (architectural compliance, acceptance-driven stop condition) but very implicit
  • Unclear how an agent would validate adherence to principles like 'never force work into one file' or 'reuse fitting seam' without domain knowledge
  • Support file (agents/openai.yaml) provides a default prompt that contextualizes the skill but does not add procedural detail
Model: claude-haiku-4-5-20251001Analyzed: Sep 9, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

  1. v1.1

    Content updated

    ✦ AILicense file updated; core skill content unchanged.

    2026-09-09

    LATEST
  2. v1.0

    2026-08-17

    View This VersionInitial version

Use JuliusBrussee/lean-build in your dev environment

Command Palette

Search for a command to run...