Batch Plan Validate

Overview

Orchestrates superpowers:writing-plans / superpowers:brainstorming (or another doc-producing skill) across a queue of tasks, so the user reviews N plans/specs one at a time through the standard EnterPlanMode → ExitPlanMode → Plannotator pattern, without being interrupted by blocking questions until drafting is done.

Drafting and validation are decoupled: Phase 1 always drafts the entire queue (a full roadmap can be dozens of tasks), while Phase 2 validates at most 3 tasks per invocation. Progress across both phases is persisted in a queue state file, so the user can validate 3 tasks, go implement them, and re-invoke this skill later — it resumes exactly where it left off instead of re-drafting or re-validating anything.

REQUIRED BACKGROUND: the underlying skills for each task are writing-prd, superpowers:writing-plans, and superpowers:brainstorming — this skill only adds the queue/phase orchestration around them. Storage/naming (the per-task docs/<feature-slug>/steps/<step-slug>/ folder) is governed by roadmap-conventions — read it before drafting anything. Read the project overrides for the underlying skills (.claude/rules/skills/writing-plans.md, .claude/rules/skills/brainstorming.md) if the current project has them.

When to Use

• The user wants several related planning/spec documents produced and reviewed in sequence (a roadmap's remaining steps, a list of independent tickets, etc.).
• NOT for a single plan/spec — use writing-plans/brainstorming directly.
• NOT when the tasks aren't independent enough to draft without resolving cross-task decisions first — resolve that dependency with the user before starting the queue.

Input

Ask the user (if not already given) which of these the task queue comes from: