Skip to content

Add review-planning.sh for independent planning review - #49

Merged
taspinar merged 1 commit into
mainfrom
feature/45-review-planning
Oct 2, 2026
Merged

taspinar merged 1 commit into
mainfrom
feature/45-review-planning

Conversation

@taspinar

@taspinar taspinar commented Oct 2, 2026

Copy link
Copy Markdown
Owner

What changed

  • New ./scripts/review-planning.sh [--agent] [--model]: runs in a planning worktree with role planning-reviewer and the read-only profile. It refuses another branch, missing planning documents, and unapproved requirements before starting an agent.
  • The reviewer receives the planning documents (description when present, requirements, architecture, roadmap, ADRs) and their diff against origin/main, including deleted documents.
  • New contract .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.
  • Each round is stored as .agents/reviews/planning-<name>-review-NN.json with a generated report, in the shared review format with kind: "planning" and no Issue.
  • The review records the planning scope (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.sh refuses planning reviews.
  • Running a reviewer with retry and storing its result moved to scripts/lib/review-run.sh, shared by review-feature.sh and review-planning.sh.
  • docs/development.md describes the planning review.

Issue / acceptance criteria

Closes #45

Risk

  • Low
  • Medium
  • High

Verification evidence

  • ./scripts/verify.sh passed (12 checks)
  • Tests added/updated where appropriate (tests/review-planning-test.sh, also passing under macOS system bash 3.2)
  • Independent review completed when required
  • Architecture/docs/ADR updated when required

Real run: review-planning.sh with 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

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>
@taspinar
taspinar merged commit 5badfca into main Oct 2, 2026
1 check failed
@taspinar
taspinar deleted the feature/45-review-planning branch October 2, 2026 18:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add review-planning.sh for independent planning review

1 participant