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

chore: merge origin/main, resolve VERSION + CHANGELOG conflicts

Browse Source 
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
Garry Tan
2026-04-04 22:04:10 -07:00
parent 7ae97156eb 31943b2f02
commit 5ffa58cc40
9 changed files with 27 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plan-ceo-review/SKILL.md
+3 -1
View File
@@ -1082,7 +1082,9 @@ After mode is selected, confirm which implementation approach (from 0C-bis) appl
Once selected, commit fully. Do not silently drift.
**STOP.** AskUserQuestion once per issue. Do NOT batch. Recommend + WHY. If no issues or fix is obvious, state what you'll do and move on — don't waste a question. Do NOT proceed until user responds.
## Review Sections (10 sections, after scope and mode are agreed)
## Review Sections (11 sections, after scope and mode are agreed)
**Anti-skip rule:** Never condense, abbreviate, or skip any review section (1-11) regardless of plan type (strategy, spec, code, infra). Every section in this skill exists for a reason. "This is a strategy doc so implementation sections don't apply" is always wrong — implementation details are where strategy breaks down. If a section genuinely has zero findings, say "No issues found" and move on — but you must evaluate it.
### Section 1: Architecture Review
Evaluate and diagram:
plan-ceo-review/SKILL.md.tmpl
+3 -1
View File
@@ -353,7 +353,9 @@ After mode is selected, confirm which implementation approach (from 0C-bis) appl
Once selected, commit fully. Do not silently drift.
**STOP.** AskUserQuestion once per issue. Do NOT batch. Recommend + WHY. If no issues or fix is obvious, state what you'll do and move on — don't waste a question. Do NOT proceed until user responds.
## Review Sections (10 sections, after scope and mode are agreed)
## Review Sections (11 sections, after scope and mode are agreed)
**Anti-skip rule:** Never condense, abbreviate, or skip any review section (1-11) regardless of plan type (strategy, spec, code, infra). Every section in this skill exists for a reason. "This is a strategy doc so implementation sections don't apply" is always wrong — implementation details are where strategy breaks down. If a section genuinely has zero findings, say "No issues found" and move on — but you must evaluate it.
### Section 1: Architecture Review
Evaluate and diagram: