CalvinBackup/gstack
1
0
Fork 0
mirror of https://github.com/garrytan/gstack.git synced 2026-07-20 14:31:12 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge remote-tracking branch 'origin/main' into garrytan/upload-transcripts

Browse Source
This commit is contained in:
Garry Tan
2026-05-02 08:00:24 -07:00
parent a0136e2132 b512be7117
commit 7ba8bdf63d
17 changed files with 849 additions and 51 deletions
Download Patch File Download Diff File Expand all files Collapse all files
office-hours/SKILL.md
+4 -2
View File
@@ -1275,9 +1275,11 @@ Rules:
- One can be **creative/lateral** (unexpected approach, different framing of the problem).
- If the second opinion (Codex or Claude subagent) proposed a prototype in Phase 3.5, consider using it as a starting point for the creative/lateral approach.
**RECOMMENDATION:** Choose [X] because [one-line reason].
**RECOMMENDATION:** Choose [X] because [one-line reason mapped to the founder's stated goal].
Present via AskUserQuestion. Do NOT proceed without user approval of the approach.
Emit ONE AskUserQuestion that lists every alternative (A/B and optionally C) as numbered options, using the preamble's AskUserQuestion Format section. The AskUserQuestion call is a tool_use, not prose — write the question text and call the tool. If no AskUserQuestion variant is callable in this session, follow the preamble's "Tool resolution" fallback: in plan mode, write `## Decisions to confirm` into the plan file and ExitPlanMode; outside plan mode, output the decision brief as prose and stop. Never silently auto-decide.
**STOP.** Do NOT proceed to Phase 4.5 (Founder Signal Synthesis), Phase 5 (Design Doc), Phase 6 (Closing), or any design-doc generation until the user responds. A "clearly winning approach" is still an approach decision and still needs explicit user approval before it lands in the design doc. Writing the recommendation in chat prose and continuing forward is the failure mode this gate exists to prevent.
---
office-hours/SKILL.md.tmpl
+4 -2
View File
@@ -438,9 +438,11 @@ Rules:
- One can be **creative/lateral** (unexpected approach, different framing of the problem).
- If the second opinion (Codex or Claude subagent) proposed a prototype in Phase 3.5, consider using it as a starting point for the creative/lateral approach.
**RECOMMENDATION:** Choose [X] because [one-line reason].
**RECOMMENDATION:** Choose [X] because [one-line reason mapped to the founder's stated goal].
Present via AskUserQuestion. Do NOT proceed without user approval of the approach.
Emit ONE AskUserQuestion that lists every alternative (A/B and optionally C) as numbered options, using the preamble's AskUserQuestion Format section. The AskUserQuestion call is a tool_use, not prose — write the question text and call the tool. If no AskUserQuestion variant is callable in this session, follow the preamble's "Tool resolution" fallback: in plan mode, write `## Decisions to confirm` into the plan file and ExitPlanMode; outside plan mode, output the decision brief as prose and stop. Never silently auto-decide.
**STOP.** Do NOT proceed to Phase 4.5 (Founder Signal Synthesis), Phase 5 (Design Doc), Phase 6 (Closing), or any design-doc generation until the user responds. A "clearly winning approach" is still an approach decision and still needs explicit user approval before it lands in the design doc. Writing the recommendation in chat prose and continuing forward is the failure mode this gate exists to prevent.
---