Agent Plugins Marketplace
← All plugins

planning-flow

v1.5.0

Build one clean coding plan: explore in parallel, review the draft against the ask, batch the questions, write tickets and resolve spikes, log every decision, then hand off to implementation.

CodexClaude Code1 Skill

By Patrick D'appollonioLicense: MIT8 GitHub starsUpdated last week

Directory evidence

Runtimes
Codex and Claude Code
Parsed components
1 skill or MCP entry
Source updated
Sep 17, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install planning-flow for Codex and Claude Code

Installs for the current user
codex plugin marketplace add patrickdappollonio/claude-plugins
codex plugin marketplace upgrade patrickdappollonio
codex plugin add planning-flow@patrickdappollonio

Paste and run these commands in a terminal with Codex. They add and refresh the patrickdappollonio catalog, then install this plugin.

Compatibility: the page URL and API slug “planning-flow” remain stable.

  • Codex: planning-flow@agent-plugin-marketplace → planning-flow@patrickdappollonio

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/patrickdappollonio/claude-plugins

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/planning-flow/.

Plugin files

plugins/planning-flow/
├── .codex-plugin/plugin.json
├── .claude-plugin/plugin.json
└── skills/planning-flow/SKILL.md

Included Skills1

planning-flowskills/planning-flow/SKILL.md

Use when the user asks for a plan for a coding change — "plan this", "how would we build", "write me a plan for", "/planning-flow <ask>" — before any code is written, especially when the change needs research across a codebase, has open questions only the user can answer, or will be handed to an implementation step afterwards. Also use when a user complains that a previous plan read like a change-log of its own revisions.

Plugin manifests2

plugins/planning-flow/.codex-plugin/plugin.json
{
  "name": "planning-flow",
  "version": "1.5.0",
  "description": "Build one clean coding plan: explore in parallel, review the draft against the ask, batch the questions, write tickets and resolve spikes, log every decision, then hand off to implementation.",
  "author": {
    "name": "Patrick D'appollonio",
    "email": "[email protected]"
  },
  "homepage": "https://github.com/patrickdappollonio/claude-plugins/tree/main/plugins/planning-flow",
  "license": "MIT",
  "keywords": [
    "planning",
    "tickets",
    "spikes",
    "decisions",
    "adversarial-review"
  ],
  "skills": "./skills/",
  "interface": {
    "displayName": "Planning Flow",
    "shortDescription": "Turn an ask into one clean, reviewed, ticketed plan.",
    "longDescription": "Explores the codebase with parallel subagents, drafts a plan, has a zero-context reviewer hold it against the original ask, asks the user only the questions the code cannot answer, writes tickets with what, why, acceptance criteria, dependencies and a size, resolves cheap spikes on the spot, logs every decision with its reason, and always presents the current plan rather than the history of its revisions.",
    "developerName": "Patrick D'appollonio",
    "category": "Productivity",
    "capabilities": [
      "Plan",
      "Research",
      "Review"
    ],
    "defaultPrompt": [
      "Plan the following change for me."
    ]
  }
}
plugins/planning-flow/.claude-plugin/plugin.json
{
  "name": "planning-flow",
  "description": "Plan-building flow that ends in one clean plan, never a story of revisions — parallel codebase exploration, a zero-context review of the draft against the original ask, questions batched for the user, tickets with what/why/acceptance criteria/dependencies/size, spikes resolved on the spot, every decision logged with its reason, and a plain-text handoff to implementation.",
  "version": "1.5.0",
  "author": {
    "name": "Patrick D'appollonio",
    "email": "[email protected]"
  },
  "homepage": "https://github.com/patrickdappollonio/claude-plugins/tree/main/plugins/planning-flow",
  "license": "MIT",
  "keywords": [
    "planning",
    "plan",
    "tickets",
    "spikes",
    "decisions",
    "adversarial-review",
    "orchestration",
    "subagents"
  ]
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[planning-flow on Agent Plugins Marketplace](https://pluginsmp.com/plugins/planning-flow)