What is document-feature-product?

A set of instructions for documenting a software feature from the user’s point of view: what it does, who it helps, and how people use it.

Use it after implementing or changing a feature to update its user-facing product documentation and the feature index, usually alongside separate technical documentation.

It explains the feature’s practical value without requiring readers to understand its implementation. Keeping this information current makes the product easier to understand and use.

document-feature-product — Skill for Claude Code by rafaelszago

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/rafaelszago/doc-everything

agentmods

npx agentmods add skills/rafaelszago/doc-everything/document-feature-product

Made for: Claude Code.

Or install doc-everything, the plugin that ships this one along with the rest of its 3 skills, 1 hook.

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/rafaelszago/doc-everything/document-feature-product.svg)](https://agentmods.dev/skills/rafaelszago/doc-everything/document-feature-product)

Your own site

<a href="https://agentmods.dev/skills/rafaelszago/doc-everything/document-feature-product"><img src="https://agentmods.dev/badge/skills/rafaelszago/doc-everything/document-feature-product.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 917 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.00134	$0.00917
Opus 5	$0.00067	$0.00458
Sonnet 5	$0.00027	$0.00183
Haiku 4.5	$0.00013	$0.00092

Measured 7d ago against content hash 000a45fe6f64, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

document-feature-product 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.

skills/document-feature-product/SKILL.md · 99 lines

How it starts

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

Document a feature — product

Record the user-facing view of a feature: what it does, who it's for, and how a person moves through it. This is the companion to [[document-feature-technical]] (the engineering view). Describe the experience and the value to the user, not the implementation.

Where it goes

docs/features/<feature>/product.md       ← this skill
docs/features/README.md                  ← index — this skill owns it
docs/features/<feature>/technical.md     ← document-feature-technical skill

<feature> is a kebab-case slug — the same slug used by the matching technical.md.
If this project pins the docs directory elsewhere (via .claude/doc-everything.json docsPath, or the plugin's DOC_EVERYTHING_DOCS_PATH env var), use that path instead of docs/features/.
One file per feature — update product.md in place as behavior changes.

How to write it

Describe what ships, not the roadmap. If a feature is scaffolded/stubbed, say so plainly in the journey.
Fill the template. Skip a section in one line if it doesn't apply.
Always update docs/features/README.md — add/refresh the one-line entry for this feature so the index stays a complete map of the product.
Cross-link the matching technical.md.
If the product has copy/localization or a visual/design language worth noting (tone, terminology, colors that carry meaning), capture it — see the optional sections in the template.

Template

# <Feature> — product

> Technical view: ./technical.md

## What it is
One line: the feature in user terms, and who it's for.

## Why it exists
The problem it solves and the value it delivers.

## Where the user finds it
Entry points the user actually reaches (route/screen, nav item, trigger).

## User journey
Numbered steps of what the user sees and does, start to finish. Quote key UI
copy where it matters.

## States & edge cases
Loading, empty, error, success — and any gating (signed-out, incomplete setup,
plan-locked). What the user sees in each.

## Copy & localization
(Optional) Primary language and any translations; where the copy lives. Note if
copy is centralized (content files) vs hardcoded.

## Visual language
(Optional) Design tokens / accent meaning / iconography this feature relies on,
and any conventions it must respect.

## Out of scope / future
What this feature deliberately does not do yet.

Read the full file on GitHub · 99 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.

7d ago First seen · 99 lines · 134 tokens per session scan A 000a45fe6f64

Subscribe to this mod's changes

document-feature-product is a skill published in the GitHub repository rafaelszago/doc-everything (2 stars, last pushed 1mo ago), licensed MIT. It adds 134 tokens to every session and 917 once invoked, about $0.0007 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-08-31.

Writing and docs

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

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens