A tool for creating product documents such as requirements documents, feature specifications, briefs, user stories, and decision records from templates and knowledge-base material. It can produce a first draft or guide you through writing it together.

Use it to draft or co-write requirements, specifications, briefs, user stories, and decision documents.

It reduces the work of starting product documents and helps keep drafts grounded in existing project information.

write-doc — Skill for Claude Code by samkawsarani/sams-product-plugins

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 samkawsarani/sams-product-plugins --skill write-doc

Clone the repo

git clone --depth 1 https://github.com/samkawsarani/sams-product-plugins

Made for: Claude Code.

Or install write-doc, the plugin that ships this one along with the rest of its 1 skill.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/samkawsarani/sams-product-plugins/write-doc/github.svg)](https://agentmods.dev/skills/samkawsarani/sams-product-plugins/write-doc)

Your own site

<a href="https://agentmods.dev/skills/samkawsarani/sams-product-plugins/write-doc"><img src="https://agentmods.dev/badge/skills/samkawsarani/sams-product-plugins/write-doc/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/samkawsarani/sams-product-plugins/write-doc"><img src="https://agentmods.dev/badge/skills/samkawsarani/sams-product-plugins/write-doc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 92 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,901 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.

Model	Per session	Once invoked
Fable 5.1	$0.00092	$0.01901
Opus 5.5	$0.00037	$0.00760
Sonnet 5.5	$0.00018	$0.00380
Haiku 4.5	$0.00009	$0.00190

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

Security

Grade A, and why

write-doc 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 2mo 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/write-doc/skills/write-doc/SKILL.md · 175 lines

How it starts

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

Dependency Check

Before starting, check optional dependencies:

qmd (optional): Run command -v qmd.
- If available: Use qmd query for semantic search across knowledge bases — this gives the best results.
- If missing: Fall back to Grep and Glob for keyword search. Note to the user that qmd would improve search quality, but proceed without it.

Product Documentation Generator

Generate comprehensive product documentation (PRDs, briefs, specs, user stories, decision docs) with full context from your knowledge base.

Modes

This skill supports two modes:

Auto-Generate Mode (default): Generates a complete first draft from templates and knowledge base context. Use when you want an immediate, comprehensive document.

Triggered by: /write-doc prd feature-name, /write-doc spec feature-name, or "generate a PRD for X"

Co-Authoring Mode: Guided, iterative document creation through structured conversation — context gathering, section-by-section refinement, and reader testing. Use when you want collaborative, high-quality writing.

Triggered by: /write-doc with collaborative intent, "co-author a doc", "help me write a spec", or "let's work on a PRD together"
See references/coauthoring-workflow.md for the full co-authoring workflow

How to choose:

Need a quick first draft? → Auto-generate
Want to iterate and refine together? → Co-authoring
Not sure? → Auto-generate first, then switch to co-authoring for refinement

Quick Start

Arguments: $ARGUMENTS

Parse $ARGUMENTS to determine:

Document type: prd, brief, spec, user-stories, decision
Subject name: The feature/project name
Mode hint: If user language suggests collaboration ("help me write", "let's co-author", "work together on"), use co-authoring mode

If document type is not specified, ask the user which type they need.

How it works (auto-generate):

Identify document type needed (or ask if ambiguous)
Gather context from knowledge base and existing files
Select appropriate template from assets/
Generate complete first draft
Present for review and iteration

Read the full file on GitHub · 175 lines

Files

What ships with it

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

2mo ago First seen · 175 lines · 92 tokens per session scan A 8b3a71374360

Subscribe to this mod's changes

write-doc is a skill published in the GitHub repository samkawsarani/sams-product-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 1,901 once invoked, about $0.0004 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.

Planning Writing and docs

write-doc next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
write-docsamkawsarani/sams-product-plugins	Skill	2	1mo ago	MIT	A	92	Claude Code
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	today	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	99k	today	Apache-2.0	A	19	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	4d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code
chat-pet-sprite-creationmicrosoft/vscode	Skill	195k	today	MIT	A	53	Claude Code, Codex