prd-writing

prd-writing is a skill for Codex from itseffi/agentic-os. It costs 23 tokens per session (658 once invoked), scanned A, original, MIT.

A structured product requirements document (PRD) for planning complex work before coding begins. It covers initiatives that involve high risk, several teams, or multiple development periods.

In plain words
What is it for?
Use it to plan large features, cross-team projects, or other high-risk initiatives before development.
Why use it?
It removes uncertainty about the problem, scope, and expected result before implementation starts. This helps teams align on work that would be costly to change later.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to plan large features, cross-team projects, or other high-risk initiatives before development.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/itseffi/agentic-os/prd-writing
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 itseffi/agentic-os --skill prd-writing
Clone the repo
git clone --depth 1 https://github.com/itseffi/agentic-os

Made for: Codex.

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-writing

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/itseffi/agentic-os/prd-writing"><img src="https://agentmods.dev/badge/skills/itseffi/agentic-os/prd-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 658 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.00023 $0.00658
Opus 5.5 $0.00009 $0.00263
Sonnet 5.5 $0.00005 $0.00132
Haiku 4.5 $0.00002 $0.00066

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

Security

Grade A, and why

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

.agents/skills/prd-writing/SKILL.md · 121 lines

How it starts

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

PRD Writing

Create clear, implementation-ready product requirements documents for initiatives that need alignment before coding.

The Process

Step 1: Confirm PRD is needed

Use PRD only if at least one is true:

  • cross-team dependency
  • multi-sprint scope
  • high-risk decision or expensive tradeoff
  • stakeholder alignment needed before build

If none apply, recommend execution-first flow (writing-plans -> tdd -> verification) instead.

Step 2: Gather required inputs

Collect:

  • product goal and target user
  • business context and constraints
  • known assumptions and risks
  • success criteria and timeline

State explicit assumptions when inputs are missing.

Step 3: Produce PRD in required format

Use this exact structure:

# [Product Name]

## About
[High-level overview of the product and goal.]

## Market Insights
[Market context, competitors, trends, and target users.]

## Problem
[Core user problem, pain points, and why existing solutions are insufficient.]

## Solution
[Proposed AI product solution and how it addresses the problem.]

## Feature Prioritization

| Feature | Reach | Impact | Confidence | Effort | RICE Score | Priority |
|---------|-------|--------|------------|--------|------------|----------|
|         |       |        |            |        |            |          |
|         |       |        |            |        |            |          |
|         |       |        |            |        |            |          |

## Requirements

**Functional Requirements:**
- FR1:
- FR2:
- FR3:

**AI/ML Model Requirements:**
- MR1:
- MR2:
- MR3:

**Non-Functional Requirements:**
- NFR1:
- NFR2:
- NFR3:

## Challenges
[Key product, technical, data, and go-to-market challenges.]

## Positioning

| Use Case | Target User | Key Benefit | Differentiator |
|----------|-------------|-------------|----------------|
|          |             |             |                |
|          |             |             |                |
|          |             |             |                |

## Metrics
[Success metrics and north star metric.]

## Rollout Plan

- **Stakeholders & Communication**
  - [Stakeholder groups and communication plan]

- **Roll-out Strategy**
  - [Launch phases, gating criteria, and post-GA plan]

Read the full file on GitHub · 121 lines

Files

What ships with it

1 file 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. 1mo ago First seen · 121 lines · 23 tokens per session scan A e42cd07a265f

Subscribe to this mod's changes

prd-writing is a skill published in the GitHub repository itseffi/agentic-os (117 stars, last pushed 14d ago), licensed MIT. It adds 23 tokens to every session and 658 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-08-30.

Related

Other skills, from other repositories

vague-requirement-unpacker

A planning aid for turning a vague business request into questions, a narrowed scenario, and an initial scope outline. It is meant for early alignment before a full PRD, or product requirements document, exists.

Chris1Wang3/Idea-on-Trial · 98 tokens

reviewcourt

A review tool for completed Tencent Meeting requirements or technical-plan meetings. It turns the meeting notes and transcript into a verdict, such as approved, conditionally approved, rejected, or lacking enough information.

Chris1Wang3/Idea-on-Trial · 150 tokens

competitive-product-research

A research workflow for comparing products and explaining how they differ. It examines user experience and business strategy, then produces a report in HTML or Markdown with traceable sources.

Chris1Wang3/Idea-on-Trial · 72 tokens

opc-board

A review skill for testing whether a one-person business, side project, or open-source idea is practical. Five advisers score its logic, ability to be delivered, growth potential, viability, and risks, then give a Go or No-Go result.

Chris1Wang3/Idea-on-Trial · 115 tokens

pm-requirement-review-simulator

A rehearsal for reviewing a product requirements document, or PRD—a written description of what a product or feature should do. Five cross-functional roles challenge the requirements before the real meeting.

Chris1Wang3/Idea-on-Trial · 78 tokens

ide-briefing-ppt

Generates a single-file 1280x720 HTML presentation by reusing the frozen Light IDE visual system extracted from LLM Wiki 分享.html. Use only when the user names ide-briefing-ppt, asks to reuse that deck's UI, or explicitly requests the combined light-gray canvas, white panels, amber accent, terminal, and file-tree…

Chris1Wang3/Idea-on-Trial · 99 tokens