A project-level planning tool that coordinates multiple development tasks, branches, and worktrees, which are isolated working folders.

Use it to create a shared project plan, manage parallel feature work, recover execution context, and coordinate merging.

It helps organize dependencies and progress when a project contains several features being built at the same time.

mega-plan — Skill by Taoidle

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/taoidle/plan-cascade/mega-plan

Any agent

npx skills add Taoidle/plan-cascade --skill mega-plan

Clone the repo

git clone --depth 1 https://github.com/Taoidle/plan-cascade

Made for: Claude Code, Codex.

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,366 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00035	$0.03366
Opus 5	$0.00017	$0.01683
Sonnet 5	$0.00007	$0.00673
Haiku 4.5	$0.00003	$0.00337

Measured 2d ago against content hash 94e177915ad0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mega-plan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

The scan reads SKILL.md. This mod also ships 8 executable files (core/__init__.py, core/feature_orchestrator.py, core/mega_generator.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/mega-plan/SKILL.md · 505 lines

How it starts

The opening of the file, as written. The whole thing — 505 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Mega Plan

A project-level orchestration system that sits above hybrid-ralph to manage multiple parallel features as a unified project plan.

Auto-Recovery Protocol (CRITICAL)

At the START of any interaction, perform this check to recover context after compression/truncation:

Check if .mega-execution-context.md exists in the project root
If YES:
- Read the file content using Read tool
- Display: "Detected ongoing mega-plan execution"
- Show current batch and active worktrees from the file
- CRITICAL: All feature work MUST happen in worktrees, NOT main branch
- If unsure of state, suggest: /mega:resume --auto-prd
If NO but mega-plan.json exists:
- Run: uv run python "${CLAUDE_PLUGIN_ROOT}/skills/mega-plan/scripts/mega-context-reminder.py" both
- This will generate the context file and display current state

This ensures context recovery even after:

Context compression (AI summarizes old messages)
Context truncation (old messages deleted)
New conversation session
Claude Code restart

Architecture

Level 1: Mega Plan (Project Level)
    └── Level 2: Features (Feature Level) = hybrid:worktree
              └── Level 3: Stories (Story Level) = hybrid internal parallelism

Quick Start

Create a Mega Plan

Generate a mega-plan from your project description:

/mega:plan Build an e-commerce platform with user authentication, product catalog, shopping cart, and order processing

This will:

Analyze your project description
Break it into features with dependencies
Create mega-plan.json, mega-findings.md, .mega-status.json
Display the plan for review

Approve and Execute

After reviewing the mega-plan:

/mega:approve

Or with automatic PRD approval for all features:

/mega:approve --auto-prd

This will:

Calculate feature batches based on dependencies
Create worktrees for Batch 1 features
Generate PRDs in each worktree
Wait for PRD approvals (or auto-approve with --auto-prd)
Execute story batches within each feature
Progress to next feature batch when complete

Read the full file on GitHub · 505 lines

Files

What ships with it

14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 505 lines · 35 tokens per session scan A 94e177915ad0

Subscribe to this mod's changes

mega-plan is a skill published in the GitHub repository Taoidle/plan-cascade (131 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 3,366 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Multi-Agent Planning Project management claude-code claude-code-plugin developer-tools llm-agents mcp-server

dos-goal-fleet

Launch multiple goal-scoped workers in waves, each with a witness-gated stop condition and dos arbitrate file-tree safety. Use when an operator asks to run several independent goals in parallel and fold only verified ships.

anthony-chaudhary/dos-kernel · 51 tokens

dos-dispatch-loop

Run recurring dos-dispatch cycles, switching to dos-replan when the backlog drains and stopping on the kernel's loop verdict. Use for unattended dispatch->replan->dispatch work across disjoint lanes.

anthony-chaudhary/dos-kernel · 49 tokens

dos-dispatch

Plan and ship the next batch on one lane: run dos-next-up, acquire a lease with dos arbitrate, gate empty work, dispatch the packet, and archive the run. Use when a single lane should move end to end with collision safety.

anthony-chaudhary/dos-kernel · 56 tokens

dos-next-up

Snapshot the repo's phased-plan portfolio into a dispatch packet: audit candidates with dos verify, render who-does-what, and emit a dos gate verdict. Use when you need the current next-work view before dispatching agents.

anthony-chaudhary/dos-kernel · 53 tokens

issue-work

Pick the next most important open GitHub issue this agent can actually complete, make its done-condition true, land it with witnesses (suite + parity + commit-audit), and priority-tag every issue touched along the way. Use when asked to "work the backlog", "complete the next most important issue", or to fix a specific…

anthony-chaudhary/dos-kernel · 75 tokens

dos-replan

Refresh a plan portfolio from evidence: close shipped queue items, update cooldown state, and surface the few decisions an operator must make. Use after dispatch bursts, drained backlogs, or recurring findings.

anthony-chaudhary/dos-kernel · 43 tokens