How do I install the Write Prd skill?

Run npx skillmds@latest add tomevault-io/write-prd in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Write Prd safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Write Prd?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Write Prd free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Write Prd?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Write Prd by tomevault-io — Agent Skill

Name: Write Prd
Author: tomevault-io

File contents

Write a PRD

Trigger

User wants to create a product requirements document for a feature, with context from the current codebase.

Workflow

Ask the user what feature or change they want to spec out.
Explore the codebase to understand relevant context:
- Existing data models and schema
- Related components, routes, and API endpoints
- Current patterns and conventions
List the user's ChatPRD projects using list_projects and ask which project this PRD belongs to (or skip if none).
Pick the right template:
- List available templates using list_templates.
- Use the user's default template if they have one set.
- Otherwise use the default PRD template.
- If multiple templates could fit (e.g., a "Technical Spec" vs "Feature PRD"), ask the user which to use.
Draft an outline with sections tailored to the feature:
- Problem statement and goals
- User stories and acceptance criteria
- Technical context (from codebase analysis)
- Edge cases and error states
- Open questions
Create the document in ChatPRD using create_document with the outline and selected template.
Save a local copy of the PRD as a markdown file in the prd/ directory at the project root (create the directory if it doesn't exist). Name the file using the document title in kebab-case (e.g., prd/user-authentication.md). This gives the team local access to specs for reference during development.
Share the ChatPRD document link and local file path with the user.

Guardrails

Ground the PRD in actual codebase context, not generic boilerplate.
Include specific file paths and existing patterns when describing technical context.
Keep scope focused — one feature per PRD.
Flag unknowns as open questions rather than making assumptions.
The prd/ directory should be committed to the repo so the whole team has specs alongside the code.

Output

PRD created in ChatPRD with document link
Local copy saved to prd/ directory
Summary of what was included

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: write-prddescription: Create a product requirements document in ChatPRD from codebase context. Use when speccing a new feature, writing up requirements, or drafting a PRD. Use when this capability is needed.---# Write a PRD## TriggerUser wants to create a product requirements document for a feature, with context from the current codebase.## Workflow1. Ask the user what feature or change they want to spec out.2. Explore the codebase to understand relevant context: - Existing data models and schema - Related components, routes, and API endpoints - Current patterns and conventions3. List the user's ChatPRD projects using `list_projects` and ask which project this PRD belongs to (or skip if none).4. Pick the right template: - List available templates using `list_templates`. - Use the user's default template if they have one set. - Otherwise use the default PRD template. - If multiple templates could fit (e.g., a "Technical Spec" vs "Feature PRD"), ask the user which to use.5. Draft an outline with sections tailored to the feature: - Problem statement and goals - User stories and acceptance criteria - Technical context (from codebase analysis) - Edge cases and error states - Open questions6. Create the document in ChatPRD using `create_document` with the outline and selected template.7. Save a local copy of the PRD as a markdown file in the `prd/` directory at the project root (create the directory if it doesn't exist). Name the file using the document title in kebab-case (e.g., `prd/user-authentication.md`). This gives the team local access to specs for reference during development.8. Share the ChatPRD document link and local file path with the user.## Guardrails- Ground the PRD in actual codebase context, not generic boilerplate.- Include specific file paths and existing patterns when describing technical context.- Keep scope focused — one feature per PRD.- Flag unknowns as open questions rather than making assumptions.- The `prd/` directory should be committed to the repo so the whole team has specs alongside the code.## Output- PRD created in ChatPRD with document link- Local copy saved to `prd/` directory- Summary of what was included---> Converted and distributed by [TomeVault](https://tomevault.io/claim/chatprd) — claim your Tome and manage your conversions.

Frequently asked questions

Write Prd