Документы требований: PRD, BRD, FRD
Работает в два этапа: сначала советует, какие документы с требованиями нужны проекту (PRD, BRD, FRD, MRD, SRD, TRD, QRD), затем пишет их по шаблонам.
Ставится на компьютере
С телефона скилл не поставить: Claude Code работает на Windows, macOS и Linux. Отправьте ссылку себе и откройте её на компьютере.
Способ установки
Откройте Терминал и вставьте команду:
curl -fsSL https:/ / claudeskills.ru/ install/ req-docs | bashСкилл ляжет в папку ~/.claude/skills/req-docs/. Если Claude Code уже открыт, а папки skills раньше не было, наберите в нём /reload-skills. Посмотреть скрипт
Карточка
req-docs- alenazaharovaux
- на английском, задачу ставите по-русски
- SKILL.md
- references/ · 13 файлов
Похожие скиллы
- РазработкаСовместное редактирование документов
Для авторов: совместное создание docs с этапами сбора контекста, структурирования и тестирования
doc-coauthoring· anthropics - РазработкаДопрос плана с документацией
Жёсткое интервью по плану или дизайну, по ходу которого Claude пишет глоссарий и ADR.
grill-with-docs· mattpocock - РазработкаДокументировщик кода
Документирует код, API и руководства по нужным стандартам.
code-documenter· Jeffallan - РазработкаКонвертация документов в Markdown
Преобразование файлов и документов в Markdown с помощью Claude Code. Поддержка PDF, DOCX, PPTX, XLSX, изображений (с OCR), аудио (с распознаванием речи).
markitdown· K-Dense-AI - ПродуктFrontend Архитектор
Для фронтенд-разработчиков: создаёт уникальные, запоминающиеся интерфейсы без шаблонности
frontend-design· anthropics - ПродуктСтруктура сайта
Планирует структуру сайта: иерархию страниц, навигацию, URL и перелинковку.
site-architecture· coreyhaines31
Статьи по теме
- Что такое Claude Skills и зачем они нужныClaude Skills — модульные навыки для ИИ-ассистента Claude. Узнайте, что это, как установить, создать свой skill и использовать в Claude Code. Примеры и инструкции.
- Настройка скиллов Claude: как устроен SKILL.md и где хранить скиллыНастройка скиллов Claude: из чего состоит SKILL.md, куда класть папку, как написать description и проверить, что скилл срабатывает. CLAUDE.md — отдельно.
- Claude Code в России: как пользоваться и работает ли в 2026Работает ли Claude Code в России: страны нет в списке Anthropic, оплата доступ не открывает. Как использовать Claude Code из поддерживаемой страны и где оплата.
Текст инструкции · SKILL.md
Оригинал инструкции (англ.)
Это оригинал автора на английском. Переводить его не нужно: Claude читает инструкцию сам, а задачу вы ставите ему по-русски.
A skill for determining which requirement documents a project needs and writing them. Works in two phases: advisor (recommend documents) → writer (create documents from templates).
Supports 7 document types: PRD, BRD, FRD, MRD, SRD, TRD, QRD with 13 template variations.
Phase Auto-Detection
Before starting, determine which phase to enter:
- Search for
**/req-docs-plan.mdin the project root anddocs/directory (exact name, no fuzzy matching) - If found and has
pendingdocuments → start Phase 2 (Writer), offer to write the next pending document - If not found → start Phase 1 (Advisor)
- If user explicitly names a document type ("write me a PRD") → confirm: "Are you sure you need specifically a PRD, or would you like me to help determine which documents your project needs?"
Phase 1: Advisor
Goal: determine which documents the project needs, in what order.
Step 1: Project Context
Read project files (README, package.json, CLAUDE.md, existing specs/docs). Understand what the product is, tech stack, stage, existing documents.
Existing documents detection: scan for files matching *PRD*.md, *BRD*.md, *FRD*.md, *MRD*.md, *SRD*.md, *TRD*.md, *QRD*.md, *requirements*.md, *-spec.md, *specification*.md. If found — read them, determine type and completeness. Report to user: "I found an existing PRD in docs/prd.md. I recommend complementing it with an FRD for the development team."
Step 2: Clarifying Questions
Ask questions one at a time. Skip questions whose answers are obvious from context. Every question includes "Not sure / Not defined yet" as a valid option.
For newcomers: include a brief explanation of why each question matters.
- What product? (skip if obvious from context)
- Stage? Idea / Discovery / MVP / Growth / Scale / Not sure yet
- Document audience? Investors / Product team / Developers / AI agent / Contractor / Not sure
- Methodology? Waterfall / Agile / Hybrid / No formal process / Not sure
- Team size? Solo / Startup (3-10) / Agile team (10-30) / Enterprise (50+) / Not sure
- Regulatory requirements? Fintech, healthcare, defense, government — or none / Not sure
- Budget estimate? Under $10K / $10K-100K / $100K-1M / Over $1M / Not defined yet
"Not sure" signals early stage → recommend lighter documents (MVP PRD, Lean BRD).
Search triggers: if the user names a specific domain (fintech, healthcare, defense, IoT) → offer to search for regulatory requirements that affect document structure. If competitors named → offer to search their approach. Use whatever search tools are available; if none, suggest specific things the user should research.
Step 3: Decision Matrix
| Situation | Recommended Documents |
|---|---|
| Idea + leadership audience | MRD |
| Investment justification | BRD |
| Product team, any scale | PRD |
| Technical spec for developers | FRD |
| Full system specification | SRD |
| Infrastructure/platform requirements | TRD |
| Formal quality standards | QRD |
| Regulated (fintech, healthcare) | PRD + FRD + SRD |
| Regulated + enterprise | BRD → PRD → FRD → SRD + TRD + QRD |
| Startup, quick validation | MVP PRD |
| AI agent (Cursor, Claude Code) | AI-Optimized PRD |
| Microservices / API product | PRD + API FRD |
| Infrastructure team documenting platform | TRD |
| Healthcare/regulated needing quality standards | QRD (alongside SRD) |
| Hardware product | PRD (Hardware) + TRD + QRD |
If PRD recommended → determine variation: Standard, One-Pager, MVP, Feature, Technical, AI-Optimized, Hardware, API, Agile.
Step 4: Recommendation
Present to user:
- Which documents are needed and why (for newcomers: one-sentence explanation of each type)
- Recommended writing order (dependency chain: MRD → BRD → PRD → FRD → SRD, TRD and QRD parallel to SRD)
- What already exists and how new documents complement it
- Confidence level: if answers were clear → confident. If many "not sure" → honest: "I recommend starting with MVP PRD. If the project grows, come back for FRD and SRD."
- Ask for confirmation before proceeding
Step 5: Save Plan
After confirmation, write docs/req-docs-plan.md:
# Required Documents — [Project Name]
## Context
- Product: [description from Step 1-2]
- Stage: [stage]
- Team: [size, methodology]
- Audience: [who the documents are for]
- Regulatory: [requirements or none]
- Save path: [to be set in Phase 2]
## Documents
1. **[TYPE]** ([Variation]) — pending
2. **[TYPE]** ([Variation]) — pending
## Order Rationale
[Why this order — dependency chain explanation]
## Existing Documents
- [path] — [type, completeness assessment]
Then transition to Phase 2 or ask if the user wants to continue later.
Phase 2: Writer
Goal: write documents one at a time using templates + project context.
Entry
- Read
docs/req-docs-plan.md - Re-read project files — context may have changed since Phase 1
- Find first document with status
pending - Offer: "Next document is [TYPE]. Start?" (user can pick a different one)
- On first document: ask save path. Default
docs/. If the project has a different convention, suggest that. Store path in plan file for subsequent documents.
Writing Process (per document)
Step 1: Load template. Read the corresponding template from references/templates/. Templates available:
| Template | File |
|---|---|
| PRD Standard | prd-standard-template.md |
| PRD MVP | prd-mvp-template.md |
| PRD AI-Optimized | prd-ai-optimized-template.md |
| BRD Standard | brd-standard-template.md |
| BRD Lean | brd-lean-template.md |
| FRD Standard | frd-standard-template.md |
| FRD API | frd-api-template.md |
| MRD Standard | mrd-standard-template.md |
| MRD Startup | mrd-startup-template.md |
| SRD Standard | srd-standard-template.md |
| SRD Agile | srd-agile-template.md |
| TRD Standard | trd-standard-template.md |
| QRD Standard | qrd-standard-template.md |
For PRD variations without a dedicated template (One-Pager, Feature, Technical, Hardware, API, Agile), adapt the Standard PRD template:
| Variation | Remove | Add |
|---|---|---|
| One-Pager | Wireframes, Technical Approach, Timeline | (condense to 1 page) |
| Feature | Market context | Feature dependencies, rollback plan |
| Technical | Market context, personas | Architecture, API specs, data models |
| Hardware | — | BOM, certifications, manufacturing |
| API | Personas, wireframes | Endpoints, schemas, rate limits (merge with API FRD) |
| Agile | Timeline, formal sign-off | Sprint mapping, story points |
Step 2: Fill with context. Use project context (freshly scanned) + advisor answers (from plan file).
Rules:
- Fill sections with real data from context where possible
- Where data is missing → write
[TBD]and add to Open Questions section - Never invent metrics, numbers, competitor names — only what is known
- Generate user stories independently but mark: "Requires validation with team"
- Prioritize requirements (P0/P1/P2) based on context but suggest review
- Add cross-references to already-written documents:
See [Type] §[Section] (path/to/file.md)
Step 3: Targeted questions. If key sections critically lack data → ask the user (max 3-4 questions). If user doesn't know → leave TBD, don't block the process.
Step 4: Self-check.
Generic checks:
- All required sections filled or marked TBD
- Problem Statement based on facts, not assumptions
- Scope contains both IN and OUT
- Success Metrics specific and measurable (or TBD)
- No duplication with existing project documents
- No invented data
- Cross-references correct
- Document length within range (MVP PRD: 2-4 pages, Standard PRD: 5-15, BRD: 5-20, FRD: 10-50, SRD: 10-50, TRD: 5-15, QRD: 5-10)
Type-specific checks:
| Type | Checks |
|---|---|
| PRD | User stories "As a [role]..." format, Scope has IN/OUT, SMART metrics |
| BRD | Problem cites data not opinions, cost-benefit present or TBD, ROI justified |
| FRD | Unique IDs (FR-001), "shall/should" language, error states described |
| MRD | TAM/SAM/SOM present or TBD, user segments specific |
| SRD | NFRs quantified (ms, %, count), architecture not empty, data model described |
| TRD | Software versions specified, licenses noted, capacity planning |
| QRD | Blocking/advisory split, each attribute has measurement method |
Step 5: Present to user. Write document to file, show, ask:
- What needs to change?
- Which TBDs can we fill now?
- Is the document ready?
Step 6: Update plan. Mark document as done in plan, record file path. Offer: "Next document is [TYPE]. Continue now or come back later?"
Error Handling
- Malformed plan file: offer to re-run Phase 1 and rebuild
- Pending document whose file already exists: ask overwrite or skip
- All documents done: congratulate, offer to review the full set or add new documents
- Stale context: on Phase 2 re-entry, if project files changed significantly since plan was created → warn user, offer to re-run advisor
Language
Determined by user's language. If unclear, ask. Templates are in English (industry standard for requirement documents). Content sections are written in the user's language. Section headers remain in English (e.g., "## Problem Statement") regardless of content language.
What This Skill Does NOT Do
- Does not replace user/market research
- Does not generate wireframes or mockups
- Does not make decisions for the user — proposes and explains
- Does not invent data — uses what is known, marks the rest as TBD