Add review-planning.sh for independent planning review - #49
Merged
Merged
Conversation
review-planning.sh runs in a planning worktree with role planning-reviewer and the read-only profile. It supplies the planning documents and their diff against origin/main, including deletions, and stores each round as a planning review in the shared review format, without an Issue. The review covers the planning scope, so adding, changing, or deleting a planning document makes it stale. Running and storing a reviewer is now shared with review-feature.sh in scripts/lib/review-run.sh. Planning reviews are not triaged. Closes #45 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
./scripts/review-planning.sh [--agent] [--model]: runs in a planning worktree with roleplanning-reviewerand the read-only profile. It refuses another branch, missing planning documents, and unapproved requirements before starting an agent.origin/main, including deleted documents..agents/prompts/planning-reviewer.md: consistency with the approved requirements and between documents, requirement coverage, justified choices, testable roadmap features with valid dependencies, and necessary ADRs. Findings about the requirements themselves are allowed and labelled..agents/reviews/planning-<name>-review-NN.jsonwith a generated report, in the shared review format withkind: "planning"and no Issue.reviewed_paths, including the optional description and the decisions directory) and its fingerprint, so adding, changing, or deleting a planning document makes it stale; other changes do not.triage-review.shrefuses planning reviews.scripts/lib/review-run.sh, shared byreview-feature.shandreview-planning.sh.docs/development.mddescribes the planning review.Issue / acceptance criteria
Closes #45
Risk
Verification evidence
./scripts/verify.shpassed (12 checks)tests/review-planning-test.sh, also passing under macOS system bash 3.2)Real run:
review-planning.shwith Codex (gpt-6-astra) on a deliberately thin throwaway planning (a household recipe app) returned CHANGES REQUIRED with five relevant Major findings (unresolved product decisions, unplanned access control, missing data flows, unjustified technology choices, untestable roadmap features).Independent review of this change: Codex (
gpt-6-astra), read-only. CHANGES REQUIRED:Not re-reviewed after the fixes.
Agent involvement
Planner: —
Implementer: Claude (Opus 5.5)
Reviewer: Codex (gpt-6-astra)
Production impact
None.
🤖 Generated with Claude Code