Write prd
Skills for automate workflows, assist in daily tasks, and enhance overall productivity.
npx -y skills add allanbian1017/skills --skill write_prdAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Product Manager-mode requirement review that interactively drafts and iterates on product requirements with user approval.
SKILL.md
2.7 KB, as published. Nobody here has run it
π― Purpose
To turn raw user ideas into rigorous, well-structured requirement documents, acting as a Product Manager. The skill utilizes an inversion pattern to actively pause execution, request user approval, and iteratively process feedback before finalizing the document.
πͺ Gating & Trigger Conditions
- When to invoke: The user requests to plan a new feature, write a product requirement document (PRD), or explicitly asks to flesh out a raw project idea.
- When NOT to invoke: The user is asking for code generation, system debugging, or general Q&A unrelated to feature planning and requirements gathering.
π₯ Input Specifications
- User Idea: Raw text description of the desired feature or product.
- Feedback Loop: User's natural language feedback or inline comments added to the generated markdown file.
βοΈ Execution Instructions (Workflow)
- Analyze: Deeply analyze the user's initial idea or feature request.
- Clarify (Inversion): If the request is ambiguous, lacks core detail, or missing fundamental functional constraints, pause and ask targeted clarifying questions to gather necessary information before drafting.
- Draft: Construct the requirement document. The document MUST include:
- Context: A brief, high-level overview of the feature.
- What Problem it Solves: Describe the core problem addressed by the feature.
- Requirements: Detailed functional and non-functional requirements.
- Persist Artifact: Save the drafted document to
docs/prds/prd_<feature_name>.md. - Halt & Prompt (Approval Gate): Stop execution and explicitly output the following message to the user: "Do you approve of this requirement? You can safely open
prd_<feature_name>.mdand add comments or modifications if you want me to rework anything!" - Iterative Rework (Fallback/Loop): Wait for the user's response.
- If the user replies "Yes" (or equivalent approval), conclude the skill successfully.
- If the user provides chat feedback or indicates they left comments in the document, apply the requested changes, and repeat Steps 4 and 5.
π€ Output Specifications
- File Output: A rigorously formatted Markdown document located at
docs/prds/prd_<feature_name>.md. - Chat Output: A conversational pause strictly requesting user approval or further iterations.
π References & Directory Structure
docs/prds/prd_<feature_name>.md: The target location for the requirement artifact and the source file for reading user inline feedback.