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

Merge 388f4075d3 into 3bef43bc5a

This commit is contained in:
shanbhagp 2026-06-02 08:45:33 +01:00 committed by GitHub
parent 3bef43bc5a 388f4075d3
commit 875e6330ed
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
4 changed files with 26 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -809,6 +809,12 @@ branch name wherever the instructions say "the base branch" or `<default>`.
# Mega Plan Review Mode # Mega Plan Review Mode
> **Execution settings recommendation**
> Bounded strategic review: assess a plan against business / product /
> investor framing. Second-tier compute (e.g., Opus Extra high) is
> right. Top-tier compute is warranted only when the plan involves
> material strategic ambiguity that benefits from open-ended exploration.
## Philosophy ## Philosophy
You are not here to rubber-stamp this plan. You are here to make it extraordinary, catch every landmine before it explodes, and ensure that when this ships, it ships at the highest possible standard. You are not here to rubber-stamp this plan. You are here to make it extraordinary, catch every landmine before it explodes, and ensure that when this ships, it ships at the highest possible standard.
But your posture depends on what the user needs: But your posture depends on what the user needs:

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

@ -57,6 +57,12 @@ gbrain:
# Mega Plan Review Mode # Mega Plan Review Mode
> **Execution settings recommendation**
> Bounded strategic review: assess a plan against business / product /
> investor framing. Second-tier compute (e.g., Opus Extra high) is
> right. Top-tier compute is warranted only when the plan involves
> material strategic ambiguity that benefits from open-ended exploration.
## Philosophy ## Philosophy
You are not here to rubber-stamp this plan. You are here to make it extraordinary, catch every landmine before it explodes, and ensure that when this ships, it ships at the highest possible standard. You are not here to rubber-stamp this plan. You are here to make it extraordinary, catch every landmine before it explodes, and ensure that when this ships, it ships at the highest possible standard.
But your posture depends on what the user needs: But your posture depends on what the user needs:

7
plan-eng-review/SKILL.md
View File

@ -748,6 +748,13 @@ Skills that run plan reviews (`/plan-*-review`, `/codex review`) include the EXI
# Plan Review Mode # Plan Review Mode
> **Execution settings recommendation**
> Bounded engineering planning: produce a build plan from a spec, with
> known target files and patterns. Second-tier compute (e.g., Opus
> Extra high) handles this cleanly. Top-tier compute is warranted only
> if the spec is unusually large or touches an unfamiliar codebase
> region.
Review this plan thoroughly before making any code changes. For every issue or recommendation, explain the concrete tradeoffs, give me an opinionated recommendation, and ask for my input before assuming a direction. Review this plan thoroughly before making any code changes. For every issue or recommendation, explain the concrete tradeoffs, give me an opinionated recommendation, and ask for my input before assuming a direction.
## Priority hierarchy ## Priority hierarchy

7
plan-eng-review/SKILL.md.tmpl
View File

@ -35,6 +35,13 @@ triggers:
# Plan Review Mode # Plan Review Mode
> **Execution settings recommendation**
> Bounded engineering planning: produce a build plan from a spec, with
> known target files and patterns. Second-tier compute (e.g., Opus
> Extra high) handles this cleanly. Top-tier compute is warranted only
> if the spec is unusually large or touches an unfamiliar codebase
> region.
Review this plan thoroughly before making any code changes. For every issue or recommendation, explain the concrete tradeoffs, give me an opinionated recommendation, and ask for my input before assuming a direction. Review this plan thoroughly before making any code changes. For every issue or recommendation, explain the concrete tradeoffs, give me an opinionated recommendation, and ask for my input before assuming a direction.
## Priority hierarchy ## Priority hierarchy