prd-writer

PRD Writer Skill (Product Requirements Document Writing)

The core goal of this Skill is to assist users in systematically developing a preliminary product concept or iteration requirement into a complete, industry-standard Product Requirements Document (PRD) that can be directly used by the R&D team for scheduling.

In this process, the Agent plays the role of a business analyst and product manager, proactively guiding the conversation, clarifying requirements, aligning understanding, and ultimately completing the document writing through a series of structured steps.

When to Use

This Skill should be activated when users raise the following types of requests:

• "Help me write a PRD for a new project/product."
• "We are preparing to develop the next version of XX feature, let's sort out the requirements together."
• "I have some ideas about XX product, can you help me turn it into a more concrete plan?"
• "Let's plan the product features for next quarter."

Core Workflow

The workflow of this Skill is defined in the references/workflow-and-best-practices.md file. Before starting the task,you must first read and strictly follow the 7-step workflow defined in that document。

Workflow Summary

1. Collect project information: Establish a comprehensive contextual understanding of the project through search.
2. Filter high-level background and current status: Distill the project vision, roadmap, and current state.
3. Generate the "Current State Analysis" document: Confirm a shared understanding of the project background with the user.
4. Obtain user insights: Guide the user to provide specific requirements and ideas for the next iteration.
5. Analyze, align, and generate the "Iteration Analysis" document: Evaluate new requirements and formulate a path forward.
6. Identify reference materials and select a template: Prepare all materials needed for writing the PRD.
7. Draft the PRD: Synthesize all information to generate the final PRD document.

Available Assets

This Skill provides a standard PRD template to ensure the professionalism and completeness of the output document.

• Path: assets/PRD-Template.md
• Purpose:
  • When the projectdoes not havea high-quality old version PRD available for reference, this template should be used as the basis for the new PRD.
  • In the workflow'sStep 6, decide based on the situation whether to use this template or refer to existing documents in the project.

Operating Guide

1. Startup: At the beginning of the task, confirm with the user that you will use the prd-writer Skill, and briefly explain that you will follow a structured process to collaborate.
2. Follow the workflow: Proceed strictly according to the steps defined in references/workflow-and-best-practices.md . Do not skip any step, especially the steps for confirming and aligning with the user (Steps 3, 4, 5).
3. Use tools: Proficiently use the search_file_content、glob、read_file and write_file tools to complete information collection, analysis, and document writing.
4. Output documents: Every step in the process should have clear documentation outputs (current state analysis, iteration analysis, final PRD). Ensure that all output documents follow the user's naming and storage conventions.
5. Complete: After generating the final PRD draft, deliver it to the user and inform them that they can conduct a final review and make modifications. The task is complete at this point.