agentmods.dev

create-prd-feature

create-prd-feature is a skill for Claude Code from jpoutrin/product-forge. It costs 18 tokens per session (1,460 once invoked), scanned A, original, MIT.

An interactive wizard for creating a Feature Requirements Document (FRD), a detailed description of one feature and how it should work. It gathers implementation details, priorities, and acceptance requirements.

In plain words
What is it for?
Use it to document a feature’s behaviour, technical context, priority, and implementation tasks.
Why use it?
It helps turn a feature idea into clearer instructions that developers and business stakeholders can review.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions Claude Code.

Part of the product-design plugin — 43 skills, 8 agents shipped together

not rated 16repo 7mo ago A scan 18 tokens original MIT

Good fit Use it to document a feature’s behaviour, technical context, priority, and implementation tasks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jpoutrin/product-forge/create-prd-feature
View source ↗ jpoutrin/product-forge
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.

Any agent
npx skills add jpoutrin/product-forge --skill create-prd-feature
Clone the repo
git clone --depth 1 https://github.com/jpoutrin/product-forge

Made for: Claude Code.

Or install product-design, the plugin that ships this one along with the rest of its 43 skills, 8 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.

agentmods badge for create-prd-feature

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/jpoutrin/product-forge/create-prd-feature"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/create-prd-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,460 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.00018 $0.01460
Opus 5.5 $0.00007 $0.00584
Sonnet 5.5 $0.00004 $0.00292
Haiku 4.5 $0.00002 $0.00146

Measured 1mo ago against content hash 7f26099c817c, 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-feature 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/product-design/skills/create-prd-feature/SKILL.md · 188 lines

How it starts

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

create-prd-feature

Category: Product & Strategy

Usage

create-prd-feature <feature-name>

Arguments

  • <feature-name>: Required - The name of the feature (will be used for filename and document title)

Execution Instructions for Claude Code

When this command is run, Claude Code should:

  1. Read the FRD template from plugins/product-design/templates/frd-template.md
  2. Start an interactive session optimized for feature-level requirements
  3. Focus on gathering technical details needed for implementation
  4. Generate actionable tasks and clear specifications
  5. Create deliverables for business conversations
  6. Save the document as <feature-name>-frd.md

Interactive Session Flow

The session is designed to extract maximum technical detail for implementation:

1. Initial Context [Section 1 of 12]

  • "Feature name confirmation:"
  • "Which product/system does this feature belong to?"
  • "Feature ID or ticket number (if exists):"
  • "Epic or parent initiative link:"
  • "Your name (author):"
  • "Priority level (P0-Critical, P1-High, P2-Medium, P3-Low):"

2. Executive Summary [Section 2 of 12]

  • "Describe this feature in one sentence:"
  • "What business value does it provide? (2-3 bullet points):"
  • "Estimated effort (XS/S/M/L/XL or story points):"
  • "Risk level (Low/Medium/High) and why:"

3. Problem & Context [Section 3 of 12]

  • "Describe the current state/problem (what's happening now):"
  • "What specific problem does this feature solve?"
  • "What happens if we don't implement this feature?"
  • "Are there any workarounds users currently employ?"

4. Objectives & Success [Section 4 of 12]

  • "List 3-5 specific, measurable objectives:"

  • "How will we measure success? (provide specific metrics):"

  • "Write detailed acceptance criteria (use Given/When/Then format):"

    Example:

    Given: User is on the dashboard
When: They click the export button
Then: A CSV file with all visible data is downloaded

5. User Stories & Scenarios [Section 5 of 12]

  • "Primary user story (As a... I want to... So that...):"
  • "List 3-5 key usage scenarios (step by step):"
  • "Identify edge cases and error scenarios:"
  • "Any special permissions or roles involved?"

Read the full file on GitHub · 188 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 · 188 lines · 18 tokens per session scan A 7f26099c817c

Subscribe to this mod's changes

create-prd-feature is a skill published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 1,460 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-03.

DocumentsPlanning
Related

Other skills, from other repositories

orbit-notion

Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…

nexu-io/open-design · 117 tokens

instrument-data-to-allotrope

Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…

anthropics/knowledge-work-plugins · 123 tokens

legal-hold

Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.

anthropics/claude-for-legal · 68 tokens

baoyu-youtube-transcript

A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.

JimLiu/baoyu-skills · 107 tokens

feishu

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

Hmbown/CodeWhale · 33 tokens

read

Fetches URLs and PDFs, then summarizes or returns clean Markdown; can also search the web through DeepSeek when built-in search is thin. Use when asked to read, fetch, quote, cite, convert, or save a URL or PDF. Not for local text files already in the repo.

tw93/Waza · 61 tokens