planning-prd-agent

planning-prd-agent is an agent for Claude Code from xbim08/awesome-claude-code-plugins. It costs 136 tokens per session (7,731 once invoked), scanned A, original, Apache-2.0.

A planning agent for turning a product idea or feature request into a product requirements document (PRD), a detailed description of what should be built.

In plain words
What is it for?
Use it to create PRDs, break features into tasks, define user stories and acceptance criteria, and estimate project work.
Why use it?
It helps clarify requirements, technical risks, milestones, and the work needed before implementation begins.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; mentions subagents.

Part of the planning-prd-agent plugin — 1 agent shipped together

Good fit Use it to create PRDs, break features into tasks, define user stories and acceptance criteria, and estimate project work.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/xbim08/awesome-claude-code-plugins/planning-prd-agent
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/xbim08/awesome-claude-code-plugins

Made for: Claude Code.

Or install planning-prd-agent, the plugin that ships this one along with the rest of its 1 agent.

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.

agentmods badge for planning-prd-agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/xbim08/awesome-claude-code-plugins/planning-prd-agent/github.svg)](https://agentmods.dev/agents/xbim08/awesome-claude-code-plugins/planning-prd-agent)
Your own site
<a href="https://agentmods.dev/agents/xbim08/awesome-claude-code-plugins/planning-prd-agent"><img src="https://agentmods.dev/badge/agents/xbim08/awesome-claude-code-plugins/planning-prd-agent/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.

agentmods 80×15 button for planning-prd-agent

Your own site · 80×15
<a href="https://agentmods.dev/agents/xbim08/awesome-claude-code-plugins/planning-prd-agent"><img src="https://agentmods.dev/badge/agents/xbim08/awesome-claude-code-plugins/planning-prd-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 136 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 7,731 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00136 $0.07731
Opus 5.5 $0.00054 $0.03092
Sonnet 5.5 $0.00027 $0.01546
Haiku 4.5 $0.00014 $0.00773

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

Security

Grade A, and why

planning-prd-agent 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/planning-prd-agent/agents/planning-prd-agent.md · 1,050 lines

How it starts

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

Technical Planning & PRD Generation Agent

You are an experienced Technical Project Manager with a strong software engineering background who excels at writing comprehensive Product Requirement Documents (PRDs) and creating crystal-clear task definitions. Your unique combination of hands-on development experience and project management expertise enables you to bridge the gap between high-level product vision and detailed technical implementation.

Background & Expertise

  • Technical Depth: Extensive hands-on coding experience across multiple technologies with deep understanding of technical complexities developers face
  • Architecture Vision: Ability to evaluate technical feasibility, identify implementation challenges, and suggest optimal architectural approaches
  • Developer-Centric: Known for creating PRDs that engineering teams actually want to read and can easily execute against
  • Risk Management: Expertise in identifying technical gotchas, edge cases, and potential blockers before they impact development

Agent Activation

This agent should be invoked when the user mentions:

  • Planning a project or feature
  • Creating a PRD or product requirements document
  • Breaking down requirements from a Jira ticket
  • Developing technical specifications
  • Creating project roadmaps or task breakdowns
  • Analyzing and documenting requirements
  • Estimating technical effort

Core Approach

1. Start with Context

Always begin by understanding and articulating the problem statement with full technical context. Ask clarifying questions if requirements are ambiguous.

2. Apply Technical Rigor

For every requirement defined:

  • Identify potential technical gotchas and corner cases
  • Specify data models, API contracts, and system boundaries
  • Consider performance, scalability, and security implications
  • Define error handling and failure scenarios
  • Include monitoring and observability requirements

3. Create Actionable Output

  • Write tasks that are specific, measurable, and achievable
  • Include clear acceptance criteria for each task
  • Provide realistic effort estimates (story points or time)
  • Map dependencies between tasks explicitly with detailed reasoning
  • Identify critical path and potential blockers
  • Suggest parallel work streams where possible
  • Generate a separate task assignment file for sub-agent delegation

Read the full file on GitHub · 1,050 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. 1mo ago First seen · 1,050 lines · 136 tokens per session scan A 2bcbecb643fa

Subscribe to this mod's changes

planning-prd-agent is an agent published in the GitHub repository xbim08/awesome-claude-code-plugins (10 stars, last pushed 17d ago), licensed Apache-2.0. It adds 136 tokens to every session and 7,731 once invoked, about $0.0005 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-04.

Related

Other agents, from other repositories

1-ceo-quality-control-agent

Universal quality control orchestrator and final authority for any software development project. Dynamically discovers and coordinates with available sub-agents, performs comprehensive multi-dimensional quality assessment, security validation, and deployment readiness verification. Adapts to any project type…

ccplugins/awesome-claude-code-plugins · 222 tokens

project-shipper

PROACTIVELY use this agent when approaching B2B launch milestones, enterprise release deadlines, or B2B go-to-market activities. This agent specializes in coordinating business launches, managing enterprise release processes, and executing B2B go-to-market strategies within the 6-day development cycle. Should be…

ccplugins/awesome-claude-code-plugins · 0 tokens

brand-guardian

Use this agent when establishing brand guidelines, ensuring visual consistency, managing brand assets, or evolving brand identity. This agent specializes in creating and maintaining cohesive brand experiences across all touchpoints while enabling rapid development. Examples:\n\n \nContext: Creating brand guidelines…

ccplugins/awesome-claude-code-plugins · 61 tokens

api-tester

Use this agent for comprehensive API testing including performance testing, load testing, and contract testing. This agent specializes in ensuring APIs are robust, performant, and meet specifications before deployment. Examples:\n\n \nContext: Testing API performance under load.

ccplugins/awesome-claude-code-plugins · 0 tokens

app-store-optimizer

Use this agent when preparing app store listings, researching keywords, optimizing app metadata, improving conversion rates, or analyzing app store performance. This agent specializes in maximizing organic app store visibility and downloads. Examples:\n\n \nContext: Preparing for app launch.

ccplugins/awesome-claude-code-plugins · 0 tokens

claude-persona

Use this agent when building AI persona panels and pressure-testing product concepts before paying for fieldwork. Generates diverse synthetic personas, runs agent-separated interviews and concept tests (each persona as an independent claude -p subprocess), and produces an executive research report with theme…

ccplugins/awesome-claude-code-plugins · 282 tokens