Skip to content

bestdeejay-design/agent-skills / skills/docs-product

docs-product

Verified

Product documentation branch — the 'why' and 'what' of a project: VISION.md, PRD.md, ROADMAP.md, FEATURES.md. Written from an idea forward, before engineering docs. Order: VISION -> PRD -> ROADMAP -> FEATURES. Full catalog + checklist in references/product-docs.md, templates in templates/. Triggers: 'продуктовая документация', 'vision', 'prd', 'роадмап', 'roadmap', 'фичи документация', 'product docs', 'требования к продукту', 'документация продукта'.

FileKindSize
SKILL.mdskill md4.8 KB
readme.ru.mdmarkdown1.1 KB
references/product-docs.mdmarkdown3.6 KB
skill.jsonconfig1.5 KB
templates/FEATURES.tmplother1.6 KB
templates/PRD.tmplother2.7 KB
templates/ROADMAP.tmplother2.0 KB
templates/VISION.tmplother2.1 KB

templates/VISION.tmpl

View on GitHub
# VISION — Product vision

> **Purpose:** the product's "why" — who it's for, what problem it solves, what it
> deliberately does NOT do. One page, stable for the product's lifetime.
> Written early (phase 1), revisited only on strategic change.

> **RU:** видение продукта — «зачем»: для кого, какую проблему решаем, чего
> сознательно НЕ делаем. Одна страница, живёт весь жизненный цикл.

## Vision statement
<!-- 1–2 sentences: the product in its final form. Example:
     "A documentation system that lets one agent order a whole repo's docs
      from an idea — nothing forgotten, everything linked." -->

## Problem statement
<!-- 2–4 sentences: who suffers, what pain, what happens today without the product.
     RU: чья боль, что происходит сейчас без продукта. -->

## Target audience
<!-- Primary + secondary segments. For each: who, context, main need. -->

## Value proposition / differentiation
<!-- Why this product wins: unique capability, price, simplicity, speed, ecosystem.
     vs: what alternatives exist and what they lack. -->

## Product principles
<!-- 3–5 durable principles that guide every feature decision.
     Example: "The map comes last", "Machine truth before code". -->

## Scope
| In scope | Out of scope (explicitly) |
|----------|---------------------------|
| `...`    | `...`                     |

> Out-of-scope list is as important as features — it prevents requirement creep.
> **RU:** список «не делаем» так же важен, как функции — он защищает от расползания требований.

## Long-term success criteria
<!-- The tests that prove the vision was right, measured in quarters/years:
     adoption, retention, revenue, time-to-value. -->

---
> **Rule:** if the vision paragraph is unclear — the project is not ready for
> requirement docs. Clarify the vision first, then write PRD.
> **RU:** не ясно видение → не пишем дальше; сначала уточняем, потом PRD.
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall