ptp-brainstorm-full

Orchestrates brainstorm generation and dual-reviewer review of change proposals in one pass.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running a brainstorm and then a separate dual-reviewer review of a change idea normally requires two manual command invocations with a stop in between. This skill removes that seam by running the brainstorm phase and the main-agent plus reviewer-agent review loop in a single orchestrated flow, passing the change id explicitly between phases. ## Core Features & Use Cases - Two-phase orchestration: Phase A produces a decision capsule at openspec/changes/<change-id>/brainstorm.md; Phase B runs the dual-reviewer (default Claude + Codex) inline-fix review loop without re-confirming scope. - Brainstorm-gate safety: If Phase A fails to write brainstorm.md, the skill stops before Phase B and reports how to recover, instead of reviewing a missing artifact. - Pre-resolved inputs: Consumes an already-allocated change id, a pre-resolved codex.mode decision, and a resolved model target, so it never re-runs branch guards, mode resolution, or id allocation. - Use Case: You describe a feature in one line via /ptp:brainstorm-full; the skill brainstorms alternatives, records the decision capsule, then runs Claude and Codex review loops and reports a terminal state such as BOTH PHASES DONE with a review tally and the next-step recommendation /ptp:plan <change-id>. ## Quick Start Run the /ptp:brainstorm-full command with a one-line description of your change to brainstorm it and immediately dual-review the resulting brainstorm document.

Frequently Asked Questions about ptp-brainstorm-full

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

FAQPage Schema
How do I run brainstorm and review in one command?▼

Invoke /ptp:brainstorm-full with your change request text. It runs the brainstorm phase to write openspec/changes/<change-id>/brainstorm.md, then continues directly into the dual-reviewer review loop without requiring a separate /ptp:review-brainstorm-full invocation.

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

ptp-brainstorm stops after writing brainstorm.md and recommends /ptp:plan. ptp-brainstorm-full suppresses that stop and continues into the full dual-reviewer brainstorm review, passing the change id explicitly so the review phase skips scope confirmation.

Does ptp-brainstorm-full require the Codex CLI?▼

Codex is optional and controlled by the pre-resolved codex.mode decision. Under required mode without codex on PATH the command stops before this skill runs; under auto or off the skill proceeds and Phase 2 may be skipped, reported as PHASE 1 DONE — CODEX SKIPPED.

What happens if the brainstorm phase fails to write brainstorm.md?▼

The brainstorm-gate stops the skill before Phase B. It reports that Phase A failed and recommends running /ptp:brainstorm <change-id> manually to produce the brainstorm, then re-running /ptp:review-brainstorm-full <change-id> for the review.

Does ptp-brainstorm-full commit or archive changes automatically?▼

No. The skill never auto-commits edits made during brainstorming or review, and it never archives the change. Archiving is always an explicit /ptp:archive <id> user action.