gstack/plan-design-review
Garry Tan 496ce80293
feat(plan-review): ask-first scope gate for plan-eng + plan-design review
On an empty/cold invocation, plan-eng-review and plan-design-review would dive
straight into repo exploration (plan-eng) or a 7-pass mockup+audit (plan-design)
and only ask the user much later, if at all. plan-ceo-review already asks first
via an unconditional Step-0 gate and behaves well; these two did not.

Add a hard-STOP scope gate as the FIRST operational instruction in each skill
(above the design-doc check / pre-review audit / mockup defaults it explicitly
overrides): the first tool call must be AskUserQuestion confirming the review
target, before any git/Read/Grep/Glob/Bash or mockup generation. Under
--disallowedTools the options render as plain column-0 lettered prose with a
Recommendation + "Reply with A, B, or C" line so the answer is detectable.

This is correct cold-start UX (confirm what to review before grinding a full
review on nothing) and it is the product half of the plan-mode smoke fix; the
harness collapsed-form detector is the deterministic half that catches the ask
however it renders. Templates + regenerated SKILL.md (default variant).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-18 00:59:03 -07:00
..
sections v1.57.7.0 feat: GSTACK REVIEW REPORT always declares unresolved decisions (#1916) 2026-06-08 21:17:18 -07:00
SKILL.md feat(plan-review): ask-first scope gate for plan-eng + plan-design review 2026-06-18 00:59:03 -07:00
SKILL.md.tmpl feat(plan-review): ask-first scope gate for plan-eng + plan-design review 2026-06-18 00:59:03 -07:00