disciplined-deliverylisted

# Disciplined Delivery ## Overview A universal engine for shipping any project correctly without skipping steps. Distilled from canonical 50k+ star engineering repos (see Essence Sources). **Two core laws:** 1. **No phase skipped.** Frame → Plan → Slice → Verify, in order. Violating the letter violates the spirit — "I'll just start coding" is a skip. 2. **"Done" requires evidence, never assertion.** A claim of complete must carry the command output / test result / eval score that proves it. "Should work" is not done. **Announce at start:** "Using disciplined-delivery: framing and planning before building." ## When to Use / Not - **Use:** any new project, feature, or multi-step change; before saying "done/fixed/complete". - **Skip:** one-line edits, trivial throwaway scripts, pure questions. ## The Loop ### Phase 0 — Frame (before any code) - Capture: who/what/why, scale assumptions (load, data size, users), hard constraints. - Write **acceptance criteria** in testable form: "WHEN [trigger], system SHALL [observable behavior]." Each becomes a check later. - **Clarify gate:** kill ambiguity now. If two readings exist, ask — don't guess. (Unattended/CI run that can't ask: record the assumption explicitly in writing, then proceed.) - State trade-offs explicitly (consistency vs availability, speed vs cost). No silent defaults. ### Phase 1 — Plan (break into slices) - Decompose into **vertical slices**, each independently testable and shippable, ordered by dependency. - A