awesome-claude-copilot: Skill for Claude Code

.claude/skills/prd/SKILL.md

prd is a skill for Claude Code from RorroRojas3/awesome-claude-copilot. It costs 63 tokens per session (916 once invoked), scanned A, original, MIT.

A skill for writing Product Requirements Documents (PRDs) and breaking product ideas into epics and user stories. A PRD describes what to build, why it matters, and how success will be measured.

In plain words
What is it for?
Use it to define products or features, set requirements, create backlogs, and prepare implementation-ready GitHub issues.
Why use it?
It turns vague requests into a shared, testable scope with priorities, acceptance criteria, dependencies, and success measures.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is RorroRojas3/awesome-claude-copilot's own configuration. It tells Claude Code how to work on awesome-claude-copilot itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything awesome-claude-copilot configures →

Reuse

Borrowing it

Nothing to install: this file belongs to RorroRojas3/awesome-claude-copilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/RorroRojas3/awesome-claude-copilot/main/.claude/skills/prd/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/RorroRojas3/awesome-claude-copilot

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 prd

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/rorrorojas3/awesome-claude-copilot/prd"><img src="https://agentmods.dev/badge/skills/rorrorojas3/awesome-claude-copilot/prd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 916 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.00063 $0.00916
Opus 5 $0.00032 $0.00458
Sonnet 5 $0.00013 $0.00183
Haiku 4.5 $0.00006 $0.00092

Measured 7d ago against content hash 35f75e04c551, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 7d 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.

.claude/skills/prd/SKILL.md · 79 lines

How it starts

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

Product Requirements Document (PRD)

Overview

Produce production-grade PRDs that bridge business vision and technical execution: a clear problem statement, measurable success criteria, and a feature broken down into epics and user stories a team can actually pick up.

When to use

  • Starting a new product or feature development cycle
  • Translating a vague idea into a concrete, testable specification
  • Breaking a feature into epics and user stories with acceptance criteria
  • Building a backlog or creating GitHub issues from requirements
  • Stakeholders need a unified "source of truth" for project scope

Not for implementation plans. A PRD says what to build and why. How to build it — file-level steps, architecture choices, task sequencing — belongs to the planning flow (plan mode, Planner Expert), which should reference the PRD's story IDs.

Workflow

1. Discover

Identify what you don't know before writing anything. The seven gaps that matter:

  1. Problem & why now — what pain, and what makes it urgent?
  2. Users — who is this for; which roles or personas?
  3. Scope boundary — what is explicitly in and out?
  4. Success metrics — how will anyone know it worked?
  5. Constraints — stack, budget, deadline, compliance?
  6. Auth model — are there protected resources; who can do what?
  7. Existing code touchpoints — what does this integrate with or replace?

Close the gaps per your operating mode: an interactive session asks the user directly (3–5 questions, bulleted, conversational); an autonomous agent returns the questions to its caller or proceeds and records each guess in the PRD's Assumptions & open questions section. Never silently invent an answer.

2. Analyze

Ground the PRD in the real codebase before drafting. Find the current architecture, similar existing features, the auth mechanism, and telemetry conventions — the Technical considerations and Epics & user stories sections must name real integration points, not hypothetical ones.

Read the full file on GitHub · 79 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 7d ago First seen · 79 lines · 63 tokens per session scan A 35f75e04c551

Subscribe to this mod's changes

prd is a skill published in the GitHub repository RorroRojas3/awesome-claude-copilot (0 stars, last pushed 12d ago), licensed MIT. It adds 63 tokens to every session and 916 once invoked, about $0.0003 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-09-01.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens