Product Requirements & User Story Writer Skill
Turn product ideas, feature requests, user problems, app concepts, and stakeholder notes into clear PRDs, user stories, acceptance criteria, feature specs, and implementation-ready requirements.
Product Requirements & User Story Writer Skill is a free, reviewed AI skill for business systems. Turn product ideas, feature requests, user problems, app concepts, and stakeholder notes into clear PRDs, user stories, acceptance criteria, feature specs, and implementation-ready requirements. It works with ChatGPT, Claude, Gemini and is ready to use out of the box.
- • The skill cannot create accurate requirements without enough context about users, goals, scope, constraints, and expected behavior.
- • It should not invent user research, stakeholder decisions, metrics, deadlines, pricing, technical constraints, or business rules.
- • Generated requirements should be reviewed by product, design, engineering, QA, or the responsible decision-maker before implementation.
About this skill
The Product Requirements & User Story Writer Skill helps product builders, founders, developers, designers, agencies, students, and AI coding users turn messy product ideas, feature requests, business notes, user feedback, app concepts, stakeholder discussions, and support patterns into structured product requirements. It produces PRDs, user stories, acceptance criteria, feature specifications, edge cases, non-functional requirements, release scope, out-of-scope items, and QA-ready acceptance checks, always separating confirmed information from assumptions rather than inventing business goals or research. This makes it useful before handing work to a development team, or before asking Lovable, Cursor, Codex, or Claude Code to implement it, since every requirement is scoped, testable, and clear enough for builders, designers, and testers to act on without needing to guess at missing details.
What it does
This skill helps convert product ideas, feature requests, and stakeholder notes into product requirement documents, feature specifications, user stories, and testable acceptance criteria, while separating must-have, should-have, later, and out-of-scope items, flagging edge cases and error states, noting non-functional and data requirements, and preparing engineering, design, and QA handoff materials including issue tickets and AI coding build prompts.
What is included
- SKILL.md — concise runtime instructions for the AI assistant
- workflow.md — step-by-step workflow for turning product ideas into build-ready requirements
- prd-framework.md — framework for product context, goals, scope, roles, functional requirements, non-functional requirements, data, UX, dependencies, risks, and done definition
- user-story-and-acceptance-criteria-guide.md — guide for writing user stories, Given/When/Then criteria, edge cases, ticket splitting, and ready-for-development checks
- requirements-quality-checklist.md — checklist for clarity, scope, testability, user value, technical readiness, safety, privacy, and handoff quality
- output-templates.md — reusable formats for PRDs, feature specs, user stories, acceptance criteria, issue tickets, AI build prompts, and requirements reviews
- examples.md — realistic input and output examples for product requirements and user story writing
How to use it
1. Download the ZIP file for this skill 2. Extract the files to a folder on your computer 3. Open the AI assistant, product planning tool, documentation tool, issue tracker, or coding assistant 4. Upload or paste the skill files if your tool supports file or context uploads 5. Share the product idea, feature request, user problem, stakeholder notes, app concept, or support pattern 6. Redact private data, confidential information, customer details, and credentials before sharing anything 7. Ask the assistant to apply the Product Requirements & User Story Writer Skill
Examples
I want PiSkill admins to upload piskill-admin-import.json to create a skill page. The JSON includes title, slug, category, descriptions, page_content_md, related skills, related articles, FAQ objects, SEO title, and meta description. FAQ must be an array of q/a objects. There should be no FAQ slugs. Only admins can publish skill pages.
Feature: Admin JSON import for PiSkill skill pages Problem statement: PiSkill admins need a faster and safer way to create skill pages because manually copying each field into the dashboard is slow and can cause formatting mistakes. User story: As a PiSkill admin, I want to upload a piskill-admin-import.json file, so that I can create a complete skill page from one validated file. Acceptance criteria: Given I am an authenticated admin, when I upload a valid piskill-admin-import.json file, then the system shows a preview of the skill page fields before publishing. Given the JSON includes faq as an array of q/a objects, when the import is validated, then the FAQ entries are accepted. Given the JSON contains faq_slugs, when the import is validated, then the system rejects the file with a clear error. Given I am not an admin, when I try to access the import feature, then I cannot upload or publish a skill page. Out of scope: Public user uploads, payment logic, MCP support, and automatic publishing without admin review.
Known limitations
- The skill cannot create accurate requirements without enough context about users, goals, scope, constraints, and expected behavior. - It should not invent user research, stakeholder decisions, metrics, deadlines, pricing, technical constraints, or business rules. - Generated requirements should be reviewed by product, design, engineering, QA, or the responsible decision-maker before implementation. - Complex legal, financial, healthcare, enterprise, security, or compliance-related features may require expert review. - Requirements can become outdated if the product direction changes and should be maintained over time.