What is phase-planner?

A planning agent that turns a completed product requirements document or large requirements file into a phase plan stored beside the source document. It also refreshes the source document's backlink to that plan.

Use it to create or refresh a durable phase-by-phase delivery plan for a product or feature.

It breaks a large body of requirements into delivery phases without editing code or unrelated project files.

phase-planner — Agent for Claude Code by rp1-run/rp1

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.

Clone the repo

git clone --depth 1 https://github.com/rp1-run/rp1

Made for: Claude Code.

Or install rp1-dev, the plugin that ships this one along with the rest of its 23 skills, 36 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/agents/rp1-run/rp1/phase-planner/github.svg)](https://agentmods.dev/agents/rp1-run/rp1/phase-planner)

Your own site

<a href="https://agentmods.dev/agents/rp1-run/rp1/phase-planner"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/phase-planner/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/agents/rp1-run/rp1/phase-planner"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/phase-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00025	$0.02608
Opus 5.5	$0.00010	$0.01043
Sonnet 5.5	$0.00005	$0.00522
Haiku 4.5	$0.00003	$0.00261

Measured 1mo ago against content hash 5d5cb8a37ea5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

phase-planner 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 1mo 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.

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.

plugins/dev/agents/phase-planner.md · 302 lines

How it starts

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

Phase Planner

Turn a completed PRD or oversized feature requirements artifact into a durable, source-adjacent phase-plan.md handoff. Refresh the source backlink section without disturbing unrelated content.

$1 <update_context>$2</update_context> <afk_mode>$3</afk_mode> <kb_root>{{KB_ROOT from prompt}}</kb_root> <work_root>{{WORK_ROOT from prompt}}</work_root> <run_id>$RUN_ID</run_id>

§SCOPE

Only read from {KB_ROOT}/ and {WORK_ROOT}/, plus these read-only canonical template references required for artifact generation:
- plugins/base/skills/artifact-templates/SKILL.md
- plugins/base/skills/artifact-templates/templates/phase-planner/phase-plan.md
Only write:
- the resolved source-adjacent phase plan
- the resolved source artifact, and only its ## Delivery Phase Plan section
Do not read any other files outside {KB_ROOT}/ and {WORK_ROOT}/.
Do not edit source code, docs outside the planning source, legacy tracker artifacts, or feature execution artifacts.

§1 KB Loading

{% include_shared "kb-progressive-loading.md" %}

Additional files:

{KB_ROOT}/architecture.md
{KB_ROOT}/modules.md
{KB_ROOT}/patterns.md

§2 Source Resolution

Resolve SOURCE to exactly one supported planning source.

Supported Inputs

Explicit path to a markdown file under {WORK_ROOT}/prds/ or {WORK_ROOT}/features/*/requirements.md
PRD basename or title matching {WORK_ROOT}/prds/*.md
Feature ID matching {WORK_ROOT}/features/{FEATURE_ID}/requirements.md

Resolution Rules

Reject any source that already points to phase-plan.md or *-phase-plan.md.
Prefer exact path matches, then exact basename / feature ID matches, then title matches.
If multiple candidates remain:
- AFK_MODE=true: pick the strongest match, document the choice in afk_decisions[]
- AFK_MODE=false: do NOT ask a follow-up question. Return an error JSON object that lists the candidate source paths and tells the user to rerun /phase-plan with one explicit path.
If no supported source resolves, return:

Read the full file on GitHub · 302 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.

1mo ago First seen · 302 lines · 25 tokens per session scan A 5d5cb8a37ea5

Subscribe to this mod's changes

phase-planner is an agent published in the GitHub repository rp1-run/rp1 (38 stars, last pushed 3d ago), licensed Apache-2.0. It adds 25 tokens to every session and 2,608 once invoked, about $0.0001 per session on Opus 5.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-09-07.

Claude Code Planning Project management ai context-engineering developer-tools opencode prompt-engineering

react18-commander

Master orchestrator for React 16/17 → 18.3.1 migration. Designed for class-component-heavy codebases. Coordinates audit, dependency upgrade, class component surgery, automatic batching fixes, and test verification. Uses memory to gate each phase and resume interrupted sessions. 18.3.1 is the target - it…

github/awesome-copilot · 101 tokens

ai-team-producer

AI team producer (Remy). Use when planning work, clarifying scope, coordinating Dev and optional QA, triaging issues, maintaining project context, or preparing and merging pull requests. Never writes application code.

github/awesome-copilot · 47 tokens

adversarial-reviewer

Reviews adversarial-authoring drafts.

intent-driven-dev/intent-driven-template · 7 tokens

senior-qa

Senior QA engineer for acceptance tests. Use for creating or modifying acceptance tests, Gherkin specs, step definitions, cucumber-js or behave runner configuration, or OpenSpec tasks involving acceptance tests. Follows the acceptance-test-authoring skill.

intent-driven-dev/intent-driven-template · 47 tokens

gsd-executor

Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.

gsd-build/get-shit-done · 36 tokens

planner

Turns a goal or spec into an ordered, dependency-aware task plan with acceptance criteria and a named critical path. Use when work needs sequencing before implementation starts.

emtcmca/promptsmith · 33 tokens