plan

Runs CEO, design, and engineering plan reviews sequentially with auto-decisions and a final approval gate.

107|7|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/no-session/pstack --skill plan-no-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/no-session/pstack/tree/main/plan
Command: npx skills add https://github.com/no-session/pstack --skill plan-no-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a development plan from strategy, design, and engineering angles normally means running three separate review skills and answering 15-30 intermediate questions. This Skill runs the full review pipeline in one command, auto-deciding routine questions so you only weigh in on genuine taste decisions. ## Core Features & Use Cases - Sequential Multi-Perspective Review: Loads the CEO, design, and eng review skills from disk and executes them in strict order (CEO → Design → Eng), each at full depth. - Six Decision Principles: Auto-answers intermediate questions using completeness, blast-radius scope, pragmatism, DRY, explicitness, and bias toward action, with every decision logged in an audit trail. - Final Approval Gate: Surfaces taste decisions (close approaches, borderline scope, codex disagreements) and user challenges at one gate instead of interrupting you throughout. - Restore Point Safety: Captures the plan file's original state to disk before any changes, so you can roll back and re-run. - Use Case: You have a rough plan for a new billing feature. Run /plan and get back a fully reviewed plan with strategy challenges, architecture validation, and a short list of decisions that actually need your judgment. ## Quick Start Ask the AI to run /plan on your current plan file to execute the full auto-review pipeline and present the final approval gate.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I review a development plan automatically before writing code?

Run /plan with your plan file. It loads the CEO, design, and engineering review skills from disk and executes them sequentially, auto-deciding routine questions using six decision principles and presenting only taste decisions at a final approval gate.

What questions does the auto plan review still ask the user?

Two types are never auto-decided: premise confirmations in the CEO phase, which require human judgment about what problem to solve, and user challenges where both models agree your stated direction should change. Everything else follows the six decision principles.

Can I undo changes made by the automated plan review?

Yes. Before modifying anything, the pipeline writes a restore point containing the plan file's original contents to ~/.pstack/projects/ with re-run instructions. You can copy the original state back and re-run the review at any time.

Does the plan review pipeline run design review for backend-only changes?

No. During intake it greps the plan for UI terms like component, screen, form, modal, and dashboard, requiring at least two matches. The design review skill is only loaded when UI scope is detected.

Why does the plan review run both Claude and Codex voices?

Dual independent voices catch blind spots a single reviewer misses. Both run sequentially in the foreground, and their findings are merged into a consensus table. Disagreements where Codex has a valid point are surfaced as taste decisions at the final gate.