Gantisstorm Claude Code Pair Planning Framework
gantisstorm-claude-code-pair-planning-framework is a Claude Code plugin for the Validate phase that orchestrates discovery agents and interchangeable planners (Claude, RepoPrompt, Codex) into structured implementation pl
by GantisStorm · github.com/GantisStorm/claude-code-pair-planning-framework
Adopt the Pair Planning Framework when you want the same discovery scouts and execution patterns in Claude Code while swapping the heavy planner between Claude, RepoPrompt, or Codex.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install gantisstorm-claude-code-pair-planning-framework@GantisStorm/claude-code-pair-planning-frameworkBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:GantisStorm/claude-code-pair-planning-framework") and the paste-ready config with skillselion.get_install_config("plugin:GantisStorm/claude-code-pair-planning-framework").
What it does
gantisstorm-claude-code-pair-planning-framework is a pluggable multi-agent planning system for Claude Code. It keeps a stable layer of discovery agents, scouts, and execution conventions while letting you choose which “brain” drafts the final plan—native Claude planning, RepoPrompt via rpcli, or Codex-style coders. Solo builders facing large or unfamiliar codebases use it to resolve ambiguities early: scouts pull selected context, synthesizers merge findings, and planners emit structured tasks with checkpoints instead of jumping straight to edits. The framework supports iterative loops, parallel per-file breakdowns, narrative architecture sections, and resume-friendly sessions so you can stop mid-plan and continue without losing thread. It fits validate-and-build handoffs when complexity, integration risk, or multi-repo relationships need explicit notes before implementation. Swap engines when one model is stronger for your stack or when you already pay for RepoPrompt or Codex seats, without rebuilding your discovery toolchain.
Highlights
- 8-plugin framework with pluggable planning engines: Claude, RepoPrompt (rpcli), and Codex (GPT-5.2 class) paths
- Discovery scouts and parallel gather steps that synthesize context before a structured planner runs
- Pair and swarm-style orchestration with session resume, continuation loops, and self-verification hooks
- Outputs detailed plans with implementation notes, per-file tasks, and architectural relationship sections
- Commands for one-shot, iterative, and minimal pipelines without rewriting your discovery agents
Why builders use it
Complex features stall when agents code before shared discovery, leaving ambiguities, missing integration notes, and no resumable plan artifact.
You get a verified, sectioned plan with per-file tasks and checkpoints, ready to hand to implementation agents using the same framework commands.
At a glance
- Type - Plugin in AI Agents.
- Adoption - 0 installs, 5 stars, 0 votes.
FAQ
Who is gantisstorm-claude-code-pair-planning-framework for?
Claude Code users who run structured planning with discovery scouts and want to switch planner engines without redoing agent wiring.
When should I use gantisstorm-claude-code-pair-planning-framework?
Use it when scope is unclear, architecture spans many files, or you need RepoPrompt or Codex to author the plan after automated context gathering.
How do I add gantisstorm-claude-code-pair-planning-framework to my agent?
Install the GantisStorm/claude-code-pair-planning-framework plugins in Claude Code, configure rpcli or Codex credentials if you use those engines, then invoke the framework’s planning commands from your repo root.
Comments
Share how you use gantisstorm-claude-code-pair-planning-framework, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.