wtk-lean
Tech Lead's Club - Spec, Lean
Run a decided feature through four moves: PLAN → CHECKS → BUILD → VERIFY. A human reviews the
feature shape before checks freeze its obligations; builders choose reversible implementation detail;
one fresh Verifier proves the complete feature. There is no task breakdown or component catalogue.
At execution or verification start, read execution metrics; include the assigned stage receipt with session identity, interval and baseline/snapshot counters after its source checks, using the normal handoff format.
Before environment setup or handoff, apply runtime lifecycle to the checkout's application/test services.
For explicit reuse, construction-order or approval requirements, apply construction constraints at Plan, Checks, Build and Verify. At phase boundaries or context recovery, use context handoff.