design-feature

# Design Feature Product definition — the stage that turns an idea or a feature request into an exhaustive, checkable set of acceptance criteria, before any engineering planning happens. **Docs only — no code, no branch.** ## Turn contract — verify before ending the turn ``` ✓ The Product half of the SPEC is filled (Context, Business goals, Scope, Capability closure, Expectation sweep, Tooling, Product decisions, Deferred decisions) OR a `NEEDS_INPUT` question is pending — never a half-filled section left silently incomplete ✓ Every Capability closure row resolves to a filled surface (UI + API + test) or an explicit `n/a: <reason>` — a blank row is not a valid end state ✓ Integration closure walked the capability inventory (`docs/CAPABILITIES.md`, or the derived inventory when the project has none) with one resolved row per subsystem — zero subsystems skipped; every capability's role matrix lists EVERY inventory role as `allowed`/`denied` ✓ The Expectation sweep table is present and fully resolved (≥ 10 rows M/L, ≥ 5 XS/S; each `in-scope`/`out-of-scope`/`deferred` with a pointer) — an enumerated expectation left unresolved is not a valid end state ✓ Interview questions (when any were needed) went out ONE per turn — never a batched round ✓ `## Design status` is set to `designed` only when the Spec-lint product boxes all tick (closure complete included) — otherwise it stays `not designed` and the turn reports the failed boxes ✓ The roadmap row's statu...