Skip to content

docs(plan-reviews): add Execution-settings recommendation preamble #1229

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
shanbhagp wants to merge 1 commit into
base: main
Choose a base branch
from
+26 −0
Open

docs(plan-reviews): add Execution-settings recommendation preamble #1229

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions plan-ceo-review/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
6 changes: 6 additions & 0 deletions plan-ceo-review/SKILL.md.tmpl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
7 changes: 7 additions & 0 deletions plan-eng-review/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
7 changes: 7 additions & 0 deletions plan-eng-review/SKILL.md.tmpl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down