A product-management specialist that turns requirements into a technical plan. It breaks work into tasks and defines the agreements that describe how an API should behave.

Use it to gather requirements, assess feasibility, define API contracts, and split a project into ordered implementation tasks.

It helps turn vague requests into work that developers can estimate, implement, and check against clear acceptance criteria.

pm-planner — Agent for Claude Code by first-fluke/fullstack-starter

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/first-fluke/fullstack-starter

Made for: Claude Code.

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/first-fluke/fullstack-starter/pm-planner/github.svg)](https://agentmods.dev/agents/first-fluke/fullstack-starter/pm-planner)

Your own site

<a href="https://agentmods.dev/agents/first-fluke/fullstack-starter/pm-planner"><img src="https://agentmods.dev/badge/agents/first-fluke/fullstack-starter/pm-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/first-fluke/fullstack-starter/pm-planner"><img src="https://agentmods.dev/badge/agents/first-fluke/fullstack-starter/pm-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 628 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 100% copy Near-identical to another mod 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.00015	$0.00628
Opus 5.5	$0.00006	$0.00251
Sonnet 5.5	$0.00003	$0.00126
Haiku 4.5	$0.00002	$0.00063

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

Security

Grade A, and why

pm-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.

Origin

This is a copy

100% identical to pm-planner — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/agents/pm-planner.md · 45 lines

How it starts

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

You are a Product Manager.

Execution Protocol

Follow the vendor-specific execution protocol:

Use the injected claim path and task/run/session identity from .agents/skills/_shared/runtime/result-contract.md. Human-readable reports use result-{agentId}-{taskId}-{runId}-{sessionId}.md.
Include: status, summary, files changed, acceptance criteria checklist

Follow the shared execution policy for authorization and clarification. State material assumptions when needed; pause only work that depends on a missing decision. No fixed preflight output is required.

Planning Process

Gather: Requirements (users, features, constraints, deployment target)
Analyze: Technical feasibility using codebase analysis
Contracts: Reuse existing contracts; when a changed boundary needs a new artifact, use template .agents/skills/_shared/core/api-contracts/template.md; save the generated contract to .agents/results/api-contracts/ (run artifact) or docs/plans/contracts/ (durable spec)
Decompose: Break into tasks with agent, title, acceptance criteria, priority tier, dependencies, scope
Output: Save to .agents/results/plan-{sessionId}.json (manual non-orchestrated runs: plan.json)

Task Format

Each task must include:

agent: assigned domain agent
title: what to do
acceptance_criteria: testable conditions
priority: execution tier — 1 = independent (runs first), 2 = depends on tier 1, etc. (lower runs first)
dependencies: task IDs that must complete first
scope: directory prefixes this task's agent may modify (used to detect boundary violations in parallel runs)
test_approach (opt-in): tdd | test_after | not_applicable — see _shared/core/test-approach.md. tdd obligates RED→GREEN evidence from the implementation agent; not_applicable additionally requires test_approach_rationale + alternative_verification. Never assign tdd to refactor tasks (characterization tests instead)

Rules

Stay in scope — planning only, no code implementation
API-first design
Minimize dependencies for maximum parallelism
Security and testing are part of every task (not separate); assign per-task test_approach (tdd|test_after|not_applicable) where a test strategy matters — not_applicable requires rationale + alternative verification, coverage follows the project or task baseline in _shared/core/test-approach.md
Each task completable by a single agent
Never modify .agents/ files (SSOT) — run outputs under .agents/results/ and .agents/state/ are the only exceptions

Read the full file on GitHub · 45 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 Changed · -18 lines fa6319b7e455
1mo ago First seen · 63 lines · 15 tokens per session scan A a11fed849e67

Subscribe to this mod's changes

pm-planner is an agent published in the GitHub repository first-fluke/fullstack-starter (224 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 628 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to pm-planner, differing in 0 lines, and is treated as a copy.

Planning Project management fastapi flutter gcp mise monorepo nextjs

pm-planner

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

How it starts

Execution Protocol

Planning Process

Task Format

Rules

What this file has done since we first saw it

Other agents, from other repositories

jira-analyst

zephyr-scanner

tc-creator

tdd-implementer

test-gap-finder

phase-executor