Skip to main content

generating-prd

Generates a Product Requirements Document (PRD) for software projects. To be used when analyzing a project to create a PRD.

Ir para a instalação

Informações da origem

Repositório
tomevault-io/skills-registry
Última atividade na origem
28 de abril de 2026 às 22:53
Idioma detectado do SKILL.md
inglês
Estrelas
1
Forks
0

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos
2 arquivos

Exibindo SKILL.md

SKILL.md
Instruções da origem · Visualização somente leitura
name
generating-prd
description
Generates a Product Requirements Document (PRD) for software projects. To be used when analyzing a project to create a PRD.
metadata
{"author":"albertobasalo"}
# Generating a PRD Understand the project idea, stakeholders, target users, and business objectives. ## Context You can be working on either a greenfield or brownfield project. ### Greenfield scenario Starting a new project from scratch. Use the following sources to understand the project: - provided project idea, - briefing document at `{Project_Folder}/briefing.md`, - read me `{Root_Folder}/README.md` file. ### Brownfield scenario Working on a legacy or existing project. Use the current project files to analyze the existing product. Pay special attention to: - `{Root_Folder}/README.md` - `{Root_Folder}/CHANGELOG.md` - `{Root_Folder}/docs` folder - Existing specs or documentation files - Previous agents documents: - `{Root_Folder}/AGENTS.md`, - `{Project_Folder}/PRD.md`, - `{Project_Folder}/ADD.md`, etc. - Any documentation in the codebase ### PRD output template Read and follow any specific [PRD template](PRD.template.md) to generate the document. ## Steps to follow: ### Step 1: Clarifying Questions - [ ] Ask only critical questions where the context is ambiguous. - Focus on: - Goal: What problem does this solve? - Target: Who will use this product? - Scope: What won't it do? - Core: What are the key features? - Solution: What is expected? ### Step 2: Drafting the PRD - [ ] Draft the PRD following the [PRD template](PRD.template.md) - Do not write more than necessary, keep it concise and to the point. - Specifically cover: - Between 3 and 9 Functional Requirements (less is better) - Between 1 and 5 Technical Requirements (less is better) ### Step 3: Review and Finalize - [ ] Review the PRD for completeness and clarity. - [ ] Ensure all sections of the PRD template are filled out appropriately. - [ ] On brownfield projects, update PRD feature status. - Mark existing features as Implemented. - New features should be marked as NotStarted. - [ ] Write the final PRD at `{Project_Folder}/PRD.md`. ## Output Checklist - [ ] A comprehensive P.R.D. at `{Project_Folder}/PRD.md`. --- > Converted and distributed by [TomeVault](https://tomevault.io/claim/albertobasalo) — claim your Tome and manage your conversions. <!-- tomevault:4.0:skill_md:2026-04-14 -->
Ver no GitHub