bestdeejay-design/agent-skills / skills/docs-product
docs-product
VerifiedProduct 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', 'требования к продукту', 'документация продукта'.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.8 KB |
| readme.ru.md | markdown | 1.1 KB |
| references/product-docs.md | markdown | 3.6 KB |
| skill.json | config | 1.5 KB |
| templates/FEATURES.tmpl | other | 1.6 KB |
| templates/PRD.tmpl | other | 2.7 KB |
| templates/ROADMAP.tmpl | other | 2.0 KB |
| templates/VISION.tmpl | other | 2.1 KB |
templates/ROADMAP.tmpl
View on GitHub# ROADMAP — Product roadmap
> **Purpose:** the prioritized, time-boxed plan of what ships when, and what each
> milestone proves. Links features to their PRD requirements and backlog.
> Statuses must match `FEATURES.md` / `BACKLOG.md`.
>
> **RU:** дорожная карта — что и когда выходит, с привязкой к PRD и бэклогу.
> Статусы сверяются с FEATURES.md / BACKLOG.md.
## Current state
<!-- 2–3 sentences: where the product is now; last shipped milestone; what is
being worked on this sprint/cycle. -->
## Milestones / phases
<!-- Ordered by value, not by effort. Each: goal → key features → proof →
target date. Statuses: planned / in progress / shipped. -->
### M1 — `<name>` · target: `YYYY-MM-DD`
- **Goal:** `<one sentence — what the user can do after M1>`
- **Features:** `US-01…US-05` (link `FEATURES.md`) / `<PRD version>`
- **Proof:** `<success metric target, acceptance criteria ref>`
- **Status:** `📋 / 🚧 / ✅`
### M2 — `<name>`
- **Goal:** ...
- **Features:** ...
- **Status:** ...
## Now / Next / Later
<!-- Quick at-a-glance: what is being built now, up next, and parked. -->
| Now | Next | Later |
|-----|------|-------|
| `M1` | `M2` | `M3 — idea only` |
## Dependencies & risks
| Risk | Impact | Mitigation | Owner |
|------|--------|------------|-------|
| `...` | High/Med/Low | `...` | `...` |
## Review cadence
<!-- When and how the roadmap is reviewed: monthly? per-milestone? who decides
reprioritization. Empty cadence = roadmap dies. -->
- **Cadence:** `monthly`
- **Participants:** `product, eng lead`
- **Inputs:** `FEATURES.md` status, `IMPROVEMENTS.md`, metric dashboards
---
> **Rule:** a roadmap without metrics or dates is a wishlist. Every milestone
> must answer "how will we know it shipped and mattered?".
> **RU:** дорожная карта без дат и метрик — список пожеланий. Каждый майлстоун
> обязан отвечать «как поймём, что выкатили и что это важно?».Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Unverified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |