create-prd

create-prd is a skill for Claude Code from vshidlovsky/prd-agents-framework. It costs 49 tokens per session (11,146 once invoked), scanned A, original, MIT.

A product requirements document (PRD) workflow that researches an initiative, drafts its requirements, reviews them, and applies senior product-manager judgment. It includes human approval points between stages.

In plain words
What is it for?
Use it to create a PRD for a named initiative, with an optional technical-detail mode and brief supplied to the research stage.
Why use it?
It gives teams a structured way to turn an idea into reviewed product requirements instead of relying on one unreviewed draft.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; mentions subagents; mentions Claude Code.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 scripts/run-log.py append --log-file "$LOG_FILE" --entry-type terminated \.

Good fit Use it to create a PRD for a named initiative, with an optional technical-detail mode and brief supplied to the research stage.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/vshidlovsky/prd-agents-framework
agentmods
npx agentmods add skills/vshidlovsky/prd-agents-framework/create-prd

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.

agentmods badge for create-prd

README.md
[![agentmods](https://agentmods.dev/badge/skills/vshidlovsky/prd-agents-framework/create-prd/github.svg)](https://agentmods.dev/skills/vshidlovsky/prd-agents-framework/create-prd)
Your own site
<a href="https://agentmods.dev/skills/vshidlovsky/prd-agents-framework/create-prd"><img src="https://agentmods.dev/badge/skills/vshidlovsky/prd-agents-framework/create-prd/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 create-prd

Your own site · 80×15
<a href="https://agentmods.dev/skills/vshidlovsky/prd-agents-framework/create-prd"><img src="https://agentmods.dev/badge/skills/vshidlovsky/prd-agents-framework/create-prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 11,146 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.00049 $0.11146
Opus 5.5 $0.00020 $0.04458
Sonnet 5.5 $0.00010 $0.02229
Haiku 4.5 $0.00005 $0.01115

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

Security

Grade A, and why

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

skills/create-prd/SKILL.md · 598 lines

How it starts

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

PRD Creation Pipeline

Run the full PRD workflow for {argument}.

Arguments

{argument} is the initiative name, optionally followed by flags. Strip every flag before using {argument} as the initiative name — the initiative name is what remains, and it is what every file path, handoff name, and agent prompt uses.

Flag Values Effect
--tc slim | full Technical Contract mode for this run only. Overrides the project-context setting.

Anything else after the initiative name is initiative brief text, not a flag — pass it through to Phase 0.

Pre-flight

  1. Resolve the Technical Contract mode and store it as TC_MODE, with TC_MODE_SOURCE recording where it came from. Precedence, highest first:

    1. --tc slim / --tc full on this invocation → TC_MODE_SOURCE = run-override
    2. .claude/project-context.md → PRD Configuration → Technical Contract → Mode → TC_MODE_SOURCE = project-context
    3. slim → TC_MODE_SOURCE = default (also the answer for an older project-context.md that predates the setting)

    Reject any --tc value other than slim or full: STOP and tell the user the two valid values. Announce the resolution once, before Phase 0 — e.g. "Technical Contract mode: full (run override; project-context says slim)" — so the user can correct it before research burns tokens. Then pass TC_MODE explicitly to the writer, the reviewer, and the senior PM: the mode a document was written in is not re-derivable from the document, and an agent that re-resolves it from project-context.md silently loses the override.

  2. Read .claude/project-context.md — confirm it exists and is filled in. If it doesn't exist, STOP and tell the user: "You need to set up .claude/project-context.md first. Copy the template from the framework and fill it in for your project."

  3. Confirm the initiative directory exists or create it at the output path specified in project-context.md. Also create the _artifacts/ subdirectory:

    mkdir -p "{initiative_dir}/_artifacts"
    
  4. Read the Model Profile table from project-context.md. Extract the Model column for each agent row. Store as MODEL_MAP — a lookup from agent name to model (e.g., researcher → sonnet, prd-writer → opus, prd-senior-pm → fable). If the Model Profile section is missing, default all agents to opus — except prd-senior-pm, which defaults to fable. Pass every value through to the Agent spawn as-is: opus, sonnet, haiku, and fable are all valid tier names. Never rewrite fable to another tier because it looks unfamiliar.

  5. Check if Run Logs are enabled in project-context.md. If enabled:

    RUN_ID=$(date -u +%Y%m%d-%H%M%S)
    LOG_FILE=".claude/prd-run-log.jsonl"
    STATE_FILE="{initiative_dir}/_artifacts/.run-state.json"
    TIMING_FILE="{initiative_dir}/_artifacts/.run-timing.tmp"
    echo "pipeline_start=$(date +%s) $(date -u +%Y-%m-%dT%H:%M:%SZ)" > "$TIMING_FILE"
    

    Record the profile name (from the Profile field in Model Profile) for the run log.

Read the full file on GitHub · 598 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 · 598 lines · 49 tokens per session scan A 014bfad4b6a3

Subscribe to this mod's changes

create-prd is a skill published in the GitHub repository vshidlovsky/prd-agents-framework (4 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 11,146 once invoked, about $0.0002 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-08-31.

Related

Other skills, from other repositories

prd-taskmaster

Zero-config goal-to-tasks engine (the Atlas engine). Takes any goal (software, pentest, business, learning), runs adaptive discovery via brainstorming, generates a validated spec, parses into TaskMaster tasks, and hands off to execution. Use when user says "PRD", "product requirements", "I want to build", invokes…

anombyte93/prd-taskmaster · 80 tokens

handoff

Phase 3 of the prd-taskmaster pipeline: smart mode selection and user handoff. Detects installed capabilities (superpowers, ralph-loop, task-master-ai, playwright, research providers), recommends ONE execution mode (A/B/C) with reasoned justification, appends the task-execution workflow to CLAUDE.md, surfaces a…

anombyte93/prd-taskmaster · 158 tokens

generate

Phase 2 of the prd-taskmaster pipeline: spec generation and task parsing. Loads a template (comprehensive|minimal), fills it with DISCOVER-phase constraints and answers, validates the spec (placeholdersfound, grade thresholds), parses the PRD into tasks via task-master, runs TaskMaster's native complexity analysis…

anombyte93/prd-taskmaster · 91 tokens

discover

Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the…

anombyte93/prd-taskmaster · 92 tokens

execute-fleet

Phase execution skill for licensed Atlas Fleet runs. Use when HANDOFF has selected Atlas Fleet and the project should be executed across isolated launcher worktrees with inbox-based result collection, verified CDD cards, sequential integration merges, and one final PR.

anombyte93/prd-taskmaster · 52 tokens

customise-workflow

Customise the prd-taskmaster plugin workflow via curated brainstorm questions. The AI asks, the user answers in plain English, and the skill writes their preferences to .atlas-ai/config/atlas.json. Future runs of prd-taskmaster read that file and apply user preferences to phase gates, validation strictness, default…

anombyte93/prd-taskmaster · 137 tokens