approve

A command that approves a PRD and starts implementing its stories in parallel. It examines dependencies, groups work into batches, launches background agents, and monitors execution.

In plain words
What is it for?
Use it to execute a feature plan, choose flow or TDD options, assign implementation agents, and optionally control verification and retries.
Why use it?
It removes the manual coordination needed to start independent stories in the right order and apply execution settings.

Command

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 commands/taoidle/plan-cascade/approve
Clone the repo
git clone --depth 1 https://github.com/Taoidle/plan-cascade
Per session 119 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 15,209 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5 $0.00119 $0.15209
Opus 5 $0.00060 $0.07605
Sonnet 5 $0.00024 $0.03042
Haiku 4.5 $0.00012 $0.01521

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

Security

Grade C, and why

approve scanned grade C with 1 finding 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.

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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf .agent-outputs
commands/approve.md · 1,888 lines

How it starts

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

Hybrid Ralph - Approve PRD and Execute

You are approving the PRD and starting parallel execution of user stories.

Execution Flow Parameters

This command accepts flow control parameters that affect quality gates and execution:

Parameter Priority

Parameters can be specified in three places. When the same parameter is defined in multiple sources, the following priority order applies:

  1. Command-line flags (highest priority)

    • Example: /plan-cascade:approve --flow full
    • Overrides all other sources
  2. PRD configuration (prd.json)

    • flow_config.level, tdd_config.mode, execution_config.require_batch_confirm
    • Used when no command-line flag is provided
  3. Default values (lowest priority)

    • Used when no command-line flag or PRD config is present

Example Priority Resolution:

# Scenario 1: Command-line overrides PRD
prd.json contains: flow_config.level = "standard"
You run: /plan-cascade:approve --flow full
Result: FLOW = "full" (command-line wins)

# Scenario 2: PRD config used when no command-line flag
prd.json contains: tdd_config.mode = "on"
You run: /plan-cascade:approve
Result: TDD = "on" (from PRD)

# Scenario 3: Default used when neither specified
prd.json has no tdd_config
You run: /plan-cascade:approve
Result: TDD = "auto" (default)

Debugging Tip: The command displays resolved parameter values at Step 2.1, showing which source each parameter came from.

--flow <quick|standard|full>

Override the execution flow depth. This controls quality gate strictness.

Flow Gate Mode AI Verification Code Review Test Enforcement
quick soft (warnings) disabled no no
standard soft (warnings) enabled no no
full hard (blocking) enabled required required

FULL Flow Enforcement:

  • Quality gates BLOCK execution on failure (not just warn)
  • Code review is REQUIRED after each story
  • Test file changes are REQUIRED alongside code changes
  • Batch confirmation is shown before each batch

Read the full file on GitHub · 1,888 lines

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.

  1. 2d ago First seen · 1,888 lines · 119 tokens per session scan C a44373790ba9

Subscribe to this mod's changes

approve is a command published in the GitHub repository Taoidle/plan-cascade (131 stars, last pushed 5mo ago), licensed MIT. It adds 119 tokens to every session and 15,209 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.