How do I install the Write A Prd skill?

Run npx skillmds@latest add mappa-ai/write-a-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 A Prd safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Write A 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 A Prd free to use?

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

Who published Write A Prd?

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

Write A Prd by mappa-ai — Agent Skill

Name: Write A Prd
Author: mappa-ai

Write A Prd

Create a detailed PRD from problem exploration, codebase review, and structured interviews with the user. Use when the user wants to create a PRD, product requirements document, or feature spec before implementation.

mappa-ai 1ad1297 2 files · 4.1 KB Updated Sep 17, 2026

File contents

This skill will be invoked when the user wants to create a PRD. You should go through the steps below. You may skip steps if you don't consider them necessary.

Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.
Explore the repo to verify their assertions and understand the current state of the codebase.
Interview the user relentlessly about every aspect of this plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one.
Once you have a complete understanding of the problem and solution, use the template below to write the PRD. The PRD should be written in the plans/prd-name.md file.

Problem Statement

The problem that the user is facing, from the user's perspective.

Solution

The solution to the problem, from the user's perspective.

User Stories

A LONG, numbered list of user stories. Each user story should be in the format of:

As an , I want a , so that

This list of user stories should be extremely extensive and cover all aspects of the feature.

Implementation Decisions

A list of implementation decisions that were made. This can include:

The modules that will be built/modified
The interfaces of those modules that will be modified
Technical clarifications from the developer
Architectural decisions
Schema changes
API contracts
Specific interactions

Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.

Out of Scope

A description of the things that are out of scope for this PRD.

Further Notes

Any further notes about the feature.

---name: write-a-prddescription: Create a detailed PRD from problem exploration, codebase review, and structured interviews with the user. Use when the user wants to create a PRD, product requirements document, or feature spec before implementation.---This skill will be invoked when the user wants to create a PRD. You should go through the steps below. You may skip steps if you don't consider them necessary.1. Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.2. Explore the repo to verify their assertions and understand the current state of the codebase.3. Interview the user relentlessly about every aspect of this plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one.4. Once you have a complete understanding of the problem and solution, use the template below to write the PRD. The PRD should be written in the `plans/prd-name.md` file.<prd-template>## Problem StatementThe problem that the user is facing, from the user's perspective.## SolutionThe solution to the problem, from the user's perspective.## User StoriesA LONG, numbered list of user stories. Each user story should be in the format of:1. As an <actor>, I want a <feature>, so that <benefit><user-story-example>1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending</user-story-example>This list of user stories should be extremely extensive and cover all aspects of the feature.## Implementation DecisionsA list of implementation decisions that were made. This can include:- The modules that will be built/modified- The interfaces of those modules that will be modified- Technical clarifications from the developer- Architectural decisions- Schema changes- API contracts- Specific interactionsDo NOT include specific file paths or code snippets. They may end up being outdated very quickly.## Out of ScopeA description of the things that are out of scope for this PRD.## Further NotesAny further notes about the feature.</prd-template>

Frequently asked questions