Lean Build

作者 juliusbrussee2e08b9177c07無授權條款110K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫今天更新

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.

AI 產生的概覽

以嚴格範圍、儲存庫重用和明確停止條件指導功能實作,避免過度建構。

功能
提供一套精簡建構流程,把功能請求轉化為契合現有系統的狹窄而完整的端到端結果。它要求從請求與儲存庫推導可觀察的驗收標準和明確的非目標,沿著擁有不變量的各層追蹤進入點,重用合適的接縫,並在修補會導致行為重複或掩蓋根因時進行重構。它也限制新增模式、提供者、設定、相依性、服務或移轉,除非驗收或生命週期設計需要,最後執行聚焦驗證,只回報實質遺漏。
適用情境
適用於過度建構風險較高的新行為、產品切片或整合工作。適合需要儲存庫重用、嚴格控制範圍和明確停止點的情況。
執行需求
僅為說明性指示,不包含指令碼。需要能存取目標儲存庫並執行聚焦驗證。

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.

來源與署名

來源:juliusbrussee/caveman位於skills/lean-build提交2e08b91

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架