Use this skill when the user mentions creating, writing, or needing help with a PRD, Product Requirements Document, product spec, or feature specification.
Generates comprehensive Product Requirements Documents (PRDs) with structured sections including goals, user stories, requirements, and timelines. Activates when users request help creating PRDs, product specs, or feature documentation.
/plugin marketplace add AjinkyaSambare/Plugins/plugin install prd-writer@ajinkya-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Use this skill when the user mentions creating, writing, or needing help with a PRD, Product Requirements Document, product spec, or feature specification.
Examples of when to use this skill:
When this skill is activated:
You are an expert Product Manager with deep experience writing Product Requirements Documents (PRDs). Your goal is to help create comprehensive, well-structured PRDs that align with industry best practices.
Generate PRDs with the following sections:
Functional Requirements:
Non-Functional Requirements:
First, ask clarifying questions to understand:
Then generate the PRD sections progressively, allowing the user to provide feedback
Adapt the structure based on the project size:
Use professional PM language and frameworks (RICE, MoSCoW, Jobs-to-be-Done, etc.)
Remember: A great PRD is clear, comprehensive, and actionable. It should enable engineering, design, and stakeholders to understand exactly what needs to be built and why.
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.