RomanNum3ral
/
gstack
mirror of https://github.com/garrytan/gstack.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge 27ae4fbd9c into a3259400a3

This commit is contained in:
GainMarketing123 2026-07-14 19:16:59 -07:00 committed by GitHub
parent a3259400a3 27ae4fbd9c
commit dea1a5fbbd
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 64 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
plan-ceo-review/SKILL.md
View File

@ -1030,13 +1030,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:
@ -1062,7 +1066,29 @@ 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.
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.
After option A completes, re-run the design doc check and resume the review.
If they choose B:
Write a handoff note to `~/.gstack/projects/$SLUG/$(date -u +%Y%m%d-%H%M%S)-$BRANCH-ceo-handoff-brainstorm.md`
with:
- Current Step 0A progress (the questions already answered)
- The specific proposal the user wanted vetted
- A note that the review paused for `/absolute-brainstorm`
Then say: "Saved a handoff note. Run `/absolute-brainstorm` in your next
message. When you come back to `/plan-ceo-review`, I'll read the handoff
plus the brainstorm output and pick up Step 0A from where we left off."
**STOP here and wait for the user's next message.** Do not continue with
the rest of `/plan-ceo-review` in this turn — `/absolute-brainstorm` is
a sibling skill, not a sub-invocation, so control must return to the user
before any further work in this review happens.
When the user returns to `/plan-ceo-review`, the standard handoff-note
check at the top of this skill will read `*-ceo-handoff-brainstorm.md` the
same way it reads other handoff notes, and the review resumes from the
recorded Step 0A point with the brainstorm's output as additional input.
When reading TODOS.md, specifically:
* Note any TODOs this plan touches, blocks, or unlocks

38
plan-ceo-review/SKILL.md.tmpl
View File

@ -164,13 +164,17 @@ 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:
@ -178,7 +182,29 @@ If they choose A:
{{INVOKE_SKILL:office-hours}}
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.
After option A completes, re-run the design doc check and resume the review.
If they choose B:
Write a handoff note to `~/.gstack/projects/$SLUG/$(date -u +%Y%m%d-%H%M%S)-$BRANCH-ceo-handoff-brainstorm.md`
with:
- Current Step 0A progress (the questions already answered)
- The specific proposal the user wanted vetted
- A note that the review paused for `/absolute-brainstorm`
Then say: "Saved a handoff note. Run `/absolute-brainstorm` in your next
message. When you come back to `/plan-ceo-review`, I'll read the handoff
plus the brainstorm output and pick up Step 0A from where we left off."
**STOP here and wait for the user's next message.** Do not continue with
the rest of `/plan-ceo-review` in this turn — `/absolute-brainstorm` is
a sibling skill, not a sub-invocation, so control must return to the user
before any further work in this review happens.
When the user returns to `/plan-ceo-review`, the standard handoff-note
check at the top of this skill will read `*-ceo-handoff-brainstorm.md` the
same way it reads other handoff notes, and the review resumes from the
recorded Step 0A point with the brainstorm's output as additional input.
When reading TODOS.md, specifically:
* Note any TODOs this plan touches, blocks, or unlocks