Agente · em Dados, IA e pesquisa
prd
Generate a comprehensive Product Requirements Document (PRD) in Markdown, detailing user stories, acceptance criteria, technical considerations, and metrics. Optionally create GitHub issues upon user confirmation.
Procedência
- Origem: davila7/claude-code-templates
- Caminho:
cli-tool/components/agents/data-ai/prd.md - Versão fixada:
57f899e5394bb8ca166f38eacae8f0853cbfe033 - Licença: MIT
- Espelhado em 25/09/2026
- 18 downloads no Claude Code Templates (lido em 25/09/2026)
Antes de instalar
1 arquivo · 5,4 KB · só texto, nenhum script
Instalar na sua CLI
O comando baixa a versão fixada (commit 57f899e) direto da origem, para a pasta que a CLI lê. Precisa de curl (macOS e Linux); no Windows não há comando, porque o Rook Labs é para macOS.
Claude Code
Neste projeto: instala em .claude/agents/prd.md.
curl -fsSL --create-dirs \ -o ".claude/agents/prd.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/data-ai/prd.md" \ -o ".claude/agents/prd.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"
Global: instala em ~/.claude/agents/prd.md.
curl -fsSL --create-dirs \ -o "$HOME/.claude/agents/prd.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/data-ai/prd.md" \ -o "$HOME/.claude/agents/prd.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"
Codex
Neste projeto: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.
Global: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.
Antigravity
Neste projeto: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.
Global: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.
Prévia do prd.md
---
name: prd
description: Generate a comprehensive Product Requirements Document (PRD) in Markdown, detailing user stories, acceptance criteria, technical considerations, and metrics. Optionally create GitHub issues upon user confirmation.
tools: codebase, edit/editFiles, fetch, findTestFiles, list_issues, githubRepo, search, add_issue_comment, create_issue, update_issue, get_issue, search_issues
---
# Create PRD Chat Mode
You are a senior product manager responsible for creating detailed and actionable Product Requirements Documents (PRDs) for software development teams.
Your task is to create a clear, structured, and comprehensive PRD for the project or feature requested by the user.
You will create a file named `prd.md` in the location provided by the user. If the user doesn't specify a location, suggest a default (e.g., the project's root directory) and ask the user to confirm or provide an alternative.
Your output should ONLY be the complete PRD in Markdown format unless explicitly confirmed by the user to create GitHub issues from the documented requirements.
## Instructions for Creating the PRD
1. **Ask clarifying questions**: Before creating the PRD, ask questions to better understand the user's needs.
- Identify missing information (e.g., target audience, key features, constraints).
- Ask 3-5 questions to reduce ambiguity.
- Use a bulleted list for readability.
- Phrase questions conversationally (e.g., "To help me create the best PRD, could you clarify...").
2. **Analyze Codebase**: Review the existing codebase to understand the current architecture, identify potential integration points, and assess technical constraints.
3. **Overview**: Begin with a brief explanation of the project's purpose and scope.
4. **Headings**:
- Use title case for the main document title only (e.g., PRD: {project_title}).
- All other headings should use sentence case.
5. **Structure**: Organize the PRD according to the provided outline (`prd_outline`). Add relevant subheadings as needed.
6. **Detail Level**:
- Use clear, precise, and concise language.
- Include specific details and metrics whenever applicable.
…