diff --git a/CHANGELOG.md b/CHANGELOG.md index 52ea4f00d..05d0fe3a7 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,14 @@ # Changelog +## [0.15.6.2] - 2026-04-04 — Anti-Skip Review Rule + +Review skills now enforce that every section gets evaluated, regardless of plan type. No more "this is a strategy doc so implementation sections don't apply." If a section genuinely has nothing to flag, say so and move on, but you have to look. + +### Added + +- **Anti-skip rule in all 4 review skills.** CEO review (sections 1-11), eng review (sections 1-4), design review (passes 1-7), and DX review (passes 1-8) all now require explicit evaluation of every section. Models can no longer skip sections by claiming the plan type makes them irrelevant. +- **CEO review header fix.** Corrected "10 sections" to "11 sections" to match the actual section count (Section 11 is conditional but exists). + ## [0.15.6.1] - 2026-04-04 ### Fixed diff --git a/VERSION b/VERSION index 505dd1b08..bd774f378 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -0.15.6.1 +0.15.6.2 diff --git a/plan-ceo-review/SKILL.md b/plan-ceo-review/SKILL.md index 4d1253cba..3cafdb6f9 100644 --- a/plan-ceo-review/SKILL.md +++ b/plan-ceo-review/SKILL.md @@ -1042,7 +1042,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: diff --git a/plan-ceo-review/SKILL.md.tmpl b/plan-ceo-review/SKILL.md.tmpl index 319c3c1a7..225cd05da 100644 --- a/plan-ceo-review/SKILL.md.tmpl +++ b/plan-ceo-review/SKILL.md.tmpl @@ -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: diff --git a/plan-design-review/SKILL.md b/plan-design-review/SKILL.md index b0f7f3a67..7d24477b8 100644 --- a/plan-design-review/SKILL.md +++ b/plan-design-review/SKILL.md @@ -1023,6 +1023,8 @@ descriptions of what 10/10 looks like. ## Review Sections (7 passes, after scope is agreed) +**Anti-skip rule:** Never condense, abbreviate, or skip any review pass (1-7) regardless of plan type (strategy, spec, code, infra). Every pass in this skill exists for a reason. "This is a strategy doc so design passes don't apply" is always wrong — design gaps are where implementation breaks down. If a pass genuinely has zero findings, say "No issues found" and move on — but you must evaluate it. + ## Prior Learnings Search for relevant learnings from previous sessions: diff --git a/plan-design-review/SKILL.md.tmpl b/plan-design-review/SKILL.md.tmpl index 4d12d2f62..ff271191c 100644 --- a/plan-design-review/SKILL.md.tmpl +++ b/plan-design-review/SKILL.md.tmpl @@ -256,6 +256,8 @@ descriptions of what 10/10 looks like. ## Review Sections (7 passes, after scope is agreed) +**Anti-skip rule:** Never condense, abbreviate, or skip any review pass (1-7) regardless of plan type (strategy, spec, code, infra). Every pass in this skill exists for a reason. "This is a strategy doc so design passes don't apply" is always wrong — design gaps are where implementation breaks down. If a pass genuinely has zero findings, say "No issues found" and move on — but you must evaluate it. + {{LEARNINGS_SEARCH}} ### Pass 1: Information Architecture diff --git a/plan-devex-review/SKILL.md b/plan-devex-review/SKILL.md index e954f737c..6c2547ca4 100644 --- a/plan-devex-review/SKILL.md +++ b/plan-devex-review/SKILL.md @@ -1079,6 +1079,8 @@ Pattern: ## Review Sections (8 passes, after Step 0 is complete) +**Anti-skip rule:** Never condense, abbreviate, or skip any review pass (1-8) regardless of plan type (strategy, spec, code, infra). Every pass in this skill exists for a reason. "This is a strategy doc so DX passes don't apply" is always wrong — DX gaps are where adoption breaks down. If a pass genuinely has zero findings, say "No issues found" and move on — but you must evaluate it. + ## Prior Learnings Search for relevant learnings from previous sessions: diff --git a/plan-devex-review/SKILL.md.tmpl b/plan-devex-review/SKILL.md.tmpl index ffdad7170..946393525 100644 --- a/plan-devex-review/SKILL.md.tmpl +++ b/plan-devex-review/SKILL.md.tmpl @@ -442,6 +442,8 @@ Pattern: ## Review Sections (8 passes, after Step 0 is complete) +**Anti-skip rule:** Never condense, abbreviate, or skip any review pass (1-8) regardless of plan type (strategy, spec, code, infra). Every pass in this skill exists for a reason. "This is a strategy doc so DX passes don't apply" is always wrong — DX gaps are where adoption breaks down. If a pass genuinely has zero findings, say "No issues found" and move on — but you must evaluate it. + {{LEARNINGS_SEARCH}} ### DX Trend Check diff --git a/plan-eng-review/SKILL.md b/plan-eng-review/SKILL.md index de21a370a..32f3d9799 100644 --- a/plan-eng-review/SKILL.md +++ b/plan-eng-review/SKILL.md @@ -649,6 +649,8 @@ Always work through the full interactive review: one section at a time (Architec ## Review Sections (after scope is agreed) +**Anti-skip rule:** Never condense, abbreviate, or skip any review section (1-4) 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. + ## Prior Learnings Search for relevant learnings from previous sessions: diff --git a/plan-eng-review/SKILL.md.tmpl b/plan-eng-review/SKILL.md.tmpl index cf86f498b..36c9d59e8 100644 --- a/plan-eng-review/SKILL.md.tmpl +++ b/plan-eng-review/SKILL.md.tmpl @@ -114,6 +114,8 @@ Always work through the full interactive review: one section at a time (Architec ## Review Sections (after scope is agreed) +**Anti-skip rule:** Never condense, abbreviate, or skip any review section (1-4) 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. + {{LEARNINGS_SEARCH}} ### 1. Architecture review