ptp-review-brainstorm-full

Runs dual-reviewer inline-fix review loops over a change's brainstorm.md until convergence.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/AlmogMaayan/ptp --skill ptp-review-brainstorm-full-almogmaayan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ptp-review-brainstorm-full
Source: https://github.com/AlmogMaayan/ptp/tree/main/skills/ptp-review-brainstorm-full
Command: npx skills add https://github.com/AlmogMaayan/ptp --skill ptp-review-brainstorm-full-almogmaayan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A thin or hand-wavy brainstorm silently produces thin OpenSpec proposal and spec artifacts downstream. This Skill catches and fixes brainstorm weaknesses before any artifacts exist by reviewing the change's brainstorm.md with two independent reviewers and editing it inline until both loops converge. ## Core Features & Use Cases - Dual-reviewer convergence loop: Runs the main agent's review loop first, then a gated reviewer-agent loop (Codex by default), each iterating review, confirm, and inline fix until zero confirmed findings or the configured iteration cap. - Inline targeted fixes: Resolves confirmed findings with minimal edits to brainstorm.md, never regenerating the brainstorm and never running openspec validate. - Combined terminal state and marker: Folds both phases into one terminal state (e.g. BOTH PHASES DONE) and performs a single atomic write of the stages/brainstorm.json convergence marker. - Use Case: After drafting a brainstorm for a new feature change, run the full brainstorm review so Claude and Codex independently audit it, fix gaps like missing options or undocumented assumptions, and confirm it is sound before authoring OpenSpec artifacts. ## Quick Start Ask the agent to run /ptp:review-brainstorm-full on your change id to dual-review and inline-fix its brainstorm.md before planning.

Frequently Asked Questions about ptp-review-brainstorm-full

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a brainstorm before creating OpenSpec artifacts?▼

Run /ptp:review-brainstorm-full with the change id. It reviews brainstorm.md with two independent reviewer loops, fixes confirmed findings inline, and reports a combined terminal state such as BOTH PHASES DONE before you proceed to /ptp:plan.

What is the difference between review-brainstorm and review-brainstorm-full?▼

review-brainstorm is report-only with a single reviewer, while review-brainstorm-full runs two reviewer loops (main agent then reviewer agent) and edits brainstorm.md inline to resolve confirmed findings until each phase converges or hits the iteration cap.

What happens if the Codex CLI is not installed during the review?▼

The reviewer phase is gated by codex.mode. With mode off, or auto without codex on PATH, Phase 2 is skipped and the run reports the green state PHASE 1 DONE — CODEX SKIPPED. With mode required and codex missing, the command stops in its outer preconditions.

Why does the brainstorm review never run openspec validate?▼

A brainstorm precedes any proposal or spec, so there is nothing for openspec validate to check. This is the one deliberate divergence from review-plan-full, and adding a validate call would error.

What happens when the review hits the iteration cap?▼

If Phase 1 reaches the cap, the run stops without starting Phase 2 and recommends resolving the remaining findings, then re-running the review. If the artifact budget is exceeded, it recommends splitting the change with /ptp:plan-multiple instead of more review rounds.