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

docs(plan-reviews): add execution-settings preamble to plan-ceo-review and plan-eng-review 

Adds a brief "Execution settings recommendation" blockquote at the top
of each skill's prompt body so users pick the right compute tier for
the task before invoking the skill.

The wording is intentionally task-shape framing ("bounded strategic
review", "second-tier compute (e.g., Opus Extra high)") rather than
pinned model names, so the guidance survives model-version changes.

Both templates and the regenerated rendered docs are included; CI's
skill-docs freshness check passes locally.
This commit is contained in:
shanbhagp 2026-04-25 12:30:11 -07:00
parent 23c4d7b228
commit 388f4075d3
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

@ -1086,6 +1086,12 @@ branch name wherever the instructions say "the base branch" or `<default>`.
# 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
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:

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

@ -33,6 +33,12 @@ triggers:
# 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
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:

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

@ -1048,6 +1048,13 @@ PLAN MODE EXCEPTION — always allowed (it's the plan file).
# 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.
## Priority hierarchy

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

@ -35,6 +35,13 @@ triggers:
# 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.
## Priority hierarchy