agentmods.dev

prd

A command that turns a feature idea into a PRD and a GitHub Issue. It can use existing product and competitor notes, check for similar issues, and include requirements, user stories, acceptance criteria, edge cases, and scope.

In plain words
What is it for?
Use it when planning a new feature, documenting its expected behavior, and creating a trackable GitHub task for implementation.
Why use it?
It reduces the work of turning an informal idea into a clear request that developers can build and review. The duplicate check helps avoid filing the same request twice.

Command

483 1mo ago A scan 8 tokens original MIT
View the source file ooiyeefei/ccc
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/ooiyeefei/ccc/prd
Clone the repo
git clone --depth 1 https://github.com/ooiyeefei/ccc
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 498 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.

ModelPer sessionOnce invoked
Fable 5 $0.00008 $0.00498
Opus 5 $0.00004 $0.00249
Sonnet 5 $0.00002 $0.00100
Haiku 4.5 $0.00001 $0.00050

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

Security

Grade A, and why

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

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/product-management/commands/prd.md · 76 lines

What it actually says

PRD Generation

Generate Product Requirements Document for $ARGUMENTS and create GitHub Issue.

Prerequisites

  1. Check GitHub CLI:

    gh auth status

  2. Check for existing context in:

    • .pm/gaps/*.md (for WINNING score)
    • .pm/competitors/*.md (for competitive evidence)

Process

Use the prd-generator agent for comprehensive PRD:

  1. Gather Context

    • Load gap analysis data for $ARGUMENTS if exists
    • Load competitor implementations
    • Ask user for additional requirements if needed

  2. Deduplication Check

    gh issue list --search "$ARGUMENTS" --label "pm:feature-request" --json number,title

    If similar issue exists (>70% match):

    • Show existing issue
    • Ask: "Update existing or create new?"

  3. Generate PRD with sections:

    • Problem Statement
    • User Stories
    • Competitive Analysis
    • Requirements (Functional, Non-Functional)
    • Acceptance Criteria (P0/P1/P2)
    • Edge Cases
    • Out of Scope
    • Technical Considerations
    • Success Metrics

  4. Save PRD

    • Create .pm/prds/ directory if not exists
    • Save to .pm/prds/[feature-slug].md

  5. Create GitHub Issue

    gh issue create \
  --title "Feature: $ARGUMENTS" \
  --body "$(cat .pm/prds/[feature-slug].md)" \
  --label "pm:feature-request" \
  --label "[winning-label]" \
  --label "[priority-label]"

  6. Update Tracking

    • Save issue reference to .pm/requests/[issue-number].md
    • Update .pm/cache/last-updated.json

  7. Return Results

    • PRD file location
    • GitHub Issue URL
    • Next steps: /speckit.specify #[issue-number]

If gh CLI Unavailable

Output PRD formatted for manual GitHub issue creation.

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 · 76 lines · 8 tokens per session scan A 3b810f504956

Subscribe to this mod's changes

prd is a command published in the GitHub repository ooiyeefei/ccc (483 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 498 once invoked, about $0.0000 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.

PlanningProductivity
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

constitution

Create or update the project constitution from interactive or provided principle inputs.

github/spec-kit · 13 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens