From 2cff51e377c89e325ccbc10fae7c76b730a88571 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Tue, 2 Jun 2026 21:21:11 -0500 Subject: feat(start-work): add a spec-prerequisite check to the Approach gate MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The Approach gate planned tests, migration, and commits but never asked whether the work needs a design spec it does not yet have. Added item 5: a spec is warranted for large or wide-surface work, unresolved design questions, or a new interface others build on. For a big task it is never a silent skip — the approach summary must state why no spec is needed, so the call is visible and challengeable at the gate. Small contained tasks pass without comment. --- todo.org | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'todo.org') diff --git a/todo.org b/todo.org index f08fff8..3b25a31 100644 --- a/todo.org +++ b/todo.org @@ -56,7 +56,8 @@ CLOSED: [2026-06-02 Tue] :END: From a work handoff (2026-06-02, surfaced running /start-work on a clean low-risk refactor). The Phase 2 Justify gate has "Downsides" and "Alternatives considered" but no forced devil's-advocate verdict on "should we even do this?" Add a "top reasons not to do this" item: surface the top three objections if any exist; when none rise to a real objection, state one line instead of manufacturing three (e.g. "Nothing material argues against this; no reason to defer or drop it"). Building the case against the work before committing is cheapest exactly at this gate, which is its purpose. Edit the start-work skill's Justify-gate phase. -** TODO [#C] start-work Approach gate: spec-needed check :feature:quick:solo: +** DONE [#C] start-work Approach gate: spec-needed check :feature:quick:solo: +CLOSED: [2026-06-02 Tue] :PROPERTIES: :LAST_REVIEWED: 2026-06-02 :END: -- cgit v1.2.3