plan-do-review

name: plan-do-review description: "[DEPRECATED — superseded 2026-05-15 by /project-tick + /triage + /plan + /do + /review-pr] Review a proposal issue with adversarial critics, converge on a plan, execute it, and iterate review-fix until clean. Drives the henyey project board (Backlog → in plan → In progress → In review → Done; Blocked on failure)." argument-hint: "[issue-number] [--model ] [--max-proposal-rounds N] [--max-review-rounds N]"

⚠️ DEPRECATED — 2026-05-15. This skill is superseded by the modular pipeline:

• /triage — backlog gate
• /plan — adversarial plan drafting (parallel critics)
• /do — implementation (two-mode)
• /review-pr — adversarial PR review with auto-merge
• /project-tick — orchestrator that dispatches to the right specialist

Driver loop: scripts/project-tick-loop.sh. Plan document: /home/tomer/.claude/plans/our-current-project-management-calm-biscuit.md.

This skill remains in tree for one release cycle as a fallback. Do not call it from new workflows. After the cycle, this file will be removed.

Parse $ARGUMENTS:

• The first positional argument, if present, is a GitHub issue number.
• --model <model>: Model for critic and review agents (default: "gpt-5.4").
• --max-proposal-rounds N: Max proposal↔critic iterations (default: 5).
• --max-review-rounds N: Max implement↔review-fix iterations (default: 3).

If no issue number was provided, auto-select one.

Auto-select only unassigned issues. Never auto-select an issue that is already assigned to anyone (including yourself) — an existing assignment signals that another worker, or a prior session of this skill, is or was working on it. Auto-claiming it races with that worker and silently piggybacks on stale context. To resume an in-progress issue, the caller must pass the issue number explicitly as an argument.

Auto-selection is project-board-native. Eligible issues are those on the henyey project (stellar-experimental/henyey, project #2) currently in the Backlog column. Issues not yet on the project are NOT auto-selectable — the operator adds them to the board first. The Blocked, in plan, In progress, In review, and Done columns are excluded automatically by the Backlog filter; that is how the board replaces the legacy not-ready and plan-do-review-loop-failed labels.

Fetch all open Backlog items once, then pick by priority label (urgent → high → medium → low) with oldest-first as the tiebreaker:

# One paginated GraphQL query for all Backlog items on project #2.
# `--paginate` requires the cursor variable to be named exactly $endCursor;
# `jq -s` is required because gh outputs one JSON object per page.
backlog_json=$(gh api graphql --paginate -f query='
  query($org: String!, $proj: Int!, $endCursor: String) {
    organization(login: $org) {
      projectV2(number: $proj) {
        items(first: 100, after: $endCursor) {
          pageInfo { endCursor hasNextPage }
          nodes {
            status: fieldValueByName(name: "Status") {
              ... on ProjectV2ItemFieldSingleSelectValue { optionId }
            }
            content {
              ... on Issue {
                number title createdAt state
                assignees(first: 5) { nodes { login } }
                labels(first: 20)    { nodes { name } }
              }
            }
          }
        }
      }
    }
  }' -f org=stellar-experimental -F proj=2)

# Backlog option id is f75ad846 (verified). Pick the first eligible issue
# per priority tier; oldest first within a tier.
ISSUE=
for priority in urgent high medium low; do
  ISSUE=$(jq -rs --arg p "$priority" '
    [ .[].data.organization.projectV2.items.nodes[]
      | select(.status.optionId == "f75ad846")
      | select(.content.state == "OPEN")
      | select((.content.assignees.nodes | length) == 0)
      | select(.content.labels.nodes | map(.name) | index($p))
    ] | sort_by(.content.createdAt) | .[0].content.number // empty
  ' <<< "$backlog_json")
  [ -n "$ISSUE" ] && break
done

# Priority-5 fallback: any Backlog open unassigned, oldest first.
if [ -z "$ISSUE" ]; then
  ISSUE=$(jq -rs '
    [ .[].data.organization.projectV2.items.nodes[]
      | select(.status.optionId == "f75ad846")
      | select(.content.state == "OPEN")
      | select((.content.assignees.nodes | length) == 0)
    ] | sort_by(.content.createdAt) | .[0].content.number // empty
  ' <<< "$backlog_json")
fi

If $ISSUE is still empty, stop with a message: "No eligible unassigned issues found in Backlog for auto-selection."

Otherwise, set $ISSUE to the selected issue number and announce: "Auto-selected issue #$ISSUE: