chore(todo): file start-work Approach-gate spec-check task

1 files changed, 3 insertions, 0 deletions

diff --git a/todo.org b/todo.org
index 865937e..fa3a454 100644
--- a/todo.org
+++ b/todo.org
@@ -46,6 +46,9 @@ From an .emacs.d handoff (2026-06-02): running task-audit against a large todo.o
 ** TODO [#C] start-work Justify gate: explicit "reasons not to do this" item :feature:
 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:
+From Craig (2026-06-02). The Approach phase should consider whether the work needs a spec when one doesn't already exist. For a big task, this isn't a silent skip — the pre-confirmation summary must explicitly report why a spec isn't needed, so the decision is visible and challengeable at the gate rather than assumed. Small tasks can pass without comment. Edit the start-work skill's Approach-gate phase to add the spec-needed consideration and the big-task report-why-not requirement.
+
 ** TODO [#B] Cross-project pattern catalog :spec:thinking:
 :PROPERTIES:
 :LAST_REVIEWED: 2026-05-28