Create detailed PRDs from problem descriptions, codebase exploration, and structured interviews.
npx skills add https://github.com/mappa-ai/skills --skill write-a-prd-mappa-ai
Please help me install this Agent Skill. Skill: write-a-prd Source: https://github.com/mappa-ai/skills/tree/main/utils-skills/write-a-prd Command: npx skills add https://github.com/mappa-ai/skills --skill write-a-prd-mappa-ai
Create a durable PRD by combining problem discovery, repo context, and relentless structured interviews to align teams before implementation.
Ask for a detailed problem description, explore the repository to ground assertions, interview until alignment, then write plans/prd-name.md using the PRD template
High-intent search queries and answers about installing and using this skill.
To write a PRD grounded in your codebase, provide a problem description for repository exploration. The skill conducts structured interviews to extract user stories and implementation decisions, then outputs a durable PRD markdown file.
Aligning teams on product requirements requires relentless structured interviews to capture scope and acceptance criteria. Combining problem discovery with codebase context ensures the generated PRD reflects actual project state and decisions.
Generating user stories and scope for a platform improvement PRD involves guided problem discovery through interviews. The skill explores your repo to ground assertions, capturing extensive user stories, implementation decisions, and notes in a fixed template.
The PRD generation process uses a fixed template and writes the output directly to a markdown file named plans/prd-name.md. This ensures the problem, solution, user stories, implementation decisions, scope, and notes follow a consistent format.
Yes, you can draft requirements for features across existing software projects. The skill explores your repository to ground assertions in the current project state before guiding problem statements and writing the final PRD.
A limitation of creating a PRD through automated repo exploration is dependency on the accuracy of your initial problem description. The skill requires continuous interview interaction until alignment is reached before writing the final markdown output.
apocohqGenerate a structured PRD as a GitHub issue from stakeholder interviews and repo exploration.
busboom-software-studioConvert architecture-update.md and usecases.md into sequenced tickets with dependencies.
telum-aiExtract story specifications and acceptance criteria from code implementations.
christopher-bussGenerate a Product Requirements Document from conversation context and codebase understanding.
