From cc86fe86a62b08ba1af4308e08297d6fb3a956e4 Mon Sep 17 00:00:00 2001 From: Thao Le Date: Sun, 17 May 2026 09:24:47 -0400 Subject: [PATCH] feat(plan-ceo-review): add /absolute-brainstorm branch to mid-session detection When mid-session pivots are detected during Step 0A (Premise Challenge), surface BOTH /office-hours (broad design interview, opens problem back up) and /absolute-brainstorm (precise design-interview gate for adopting a specific new proposal) so users get the option that fits where they are. Edits canonical source (.tmpl); SKILL.md regenerated via gen:skill-docs. skill-validation + gen-skill-docs tests pass. Co-Authored-By: Claude Opus 4.7 (1M context) --- plan-ceo-review/SKILL.md | 19 ++++++++++++++----- plan-ceo-review/SKILL.md.tmpl | 19 ++++++++++++++----- 2 files changed, 28 insertions(+), 10 deletions(-) diff --git a/plan-ceo-review/SKILL.md b/plan-ceo-review/SKILL.md index 91c1cfc79..5bff777be 100644 --- a/plan-ceo-review/SKILL.md +++ b/plan-ceo-review/SKILL.md @@ -994,13 +994,17 @@ If none was produced (user may have cancelled), proceed with standard review. **Mid-session detection:** During Step 0A (Premise Challenge), if the user can't articulate the problem, keeps changing the problem statement, answers with "I'm not -sure," or is clearly exploring rather than reviewing — offer `/office-hours`: +sure," or is clearly exploring rather than reviewing — offer two branches: -> "It sounds like you're still figuring out what to build — that's totally fine, but -> that's what /office-hours is designed for. Want to run /office-hours right now? -> We'll pick up right where we left off." +> "It sounds like you're still figuring out what to build — that's totally fine. +> Two ways to handle it: +> - `/office-hours` — broad design interview, opens the problem back up +> - `/absolute-brainstorm` — precise design-interview gate for adopting a specific +> new proposal, when you have a concrete idea you want vetted before scoping it in +> +> Which one fits where you are right now?" -Options: A) Yes, run /office-hours now. B) No, keep going. +Options: A) Run /office-hours. B) Run /absolute-brainstorm. C) No, keep going. If they keep going, proceed normally — no guilt, no re-asking. If they choose A: @@ -1025,6 +1029,11 @@ Follow its instructions from top to bottom, **skipping these sections** (already Execute every other section at full depth. When the loaded skill's instructions are complete, continue with the next step below. +If they choose B: tell the user to run `/absolute-brainstorm` directly in their +next message — it's a sibling skill, not a sub-invocation. Note current Step 0A +progress, pause this review, and pick up once they return with the brainstorm's +output. + Note current Step 0A progress so you don't re-ask questions already answered. After completion, re-run the design doc check and resume the review. diff --git a/plan-ceo-review/SKILL.md.tmpl b/plan-ceo-review/SKILL.md.tmpl index 4e4861d62..22b65f9ae 100644 --- a/plan-ceo-review/SKILL.md.tmpl +++ b/plan-ceo-review/SKILL.md.tmpl @@ -164,19 +164,28 @@ context to pick up where we left off." **Mid-session detection:** During Step 0A (Premise Challenge), if the user can't articulate the problem, keeps changing the problem statement, answers with "I'm not -sure," or is clearly exploring rather than reviewing — offer `/office-hours`: +sure," or is clearly exploring rather than reviewing — offer two branches: -> "It sounds like you're still figuring out what to build — that's totally fine, but -> that's what /office-hours is designed for. Want to run /office-hours right now? -> We'll pick up right where we left off." +> "It sounds like you're still figuring out what to build — that's totally fine. +> Two ways to handle it: +> - `/office-hours` — broad design interview, opens the problem back up +> - `/absolute-brainstorm` — precise design-interview gate for adopting a specific +> new proposal, when you have a concrete idea you want vetted before scoping it in +> +> Which one fits where you are right now?" -Options: A) Yes, run /office-hours now. B) No, keep going. +Options: A) Run /office-hours. B) Run /absolute-brainstorm. C) No, keep going. If they keep going, proceed normally — no guilt, no re-asking. If they choose A: {{INVOKE_SKILL:office-hours}} +If they choose B: tell the user to run `/absolute-brainstorm` directly in their +next message — it's a sibling skill, not a sub-invocation. Note current Step 0A +progress, pause this review, and pick up once they return with the brainstorm's +output. + Note current Step 0A progress so you don't re-ask questions already answered. After completion, re-run the design doc check and resume the review.