Generates a Markdown PRD from feature descriptions via clarifying questions.
npx skills add https://github.com/kileroppo/AI-Coding-Guidance-Skills --skill prd-kileroppo
Please help me install this Agent Skill. Skill: prd Source: https://github.com/kileroppo/AI-Coding-Guidance-Skills/tree/main/skills/prd Command: npx skills add https://github.com/kileroppo/AI-Coding-Guidance-Skills --skill prd-kileroppo
A clear PRD prevents ambiguous requirements by converting a feature idea into structured, actionable plans that can be implemented without guesswork.
Generate a PRD for your new feature by asking the AI to create the product requirements document for a feature idea, including any key constraints and how you define success.
High-intent search queries and answers about installing and using this skill.
To generate a product requirements document, provide a feature description and answer 3-5 clarifying questions. The system translates your answers into structured goals, user stories, functional requirements, non-goals, and success metrics saved as a Markdown file.
A feature description for a complete PRD should include the core capability, key constraints, and how you define success. Providing these details upfront helps resolve ambiguity and ensures the generated document contains verifiable acceptance criteria.
Yes, you can spec out new projects without starting implementation. The process focuses exclusively on planning and explicitly avoids initiating any implementation work, producing a structured requirements document instead.
Yes, the generated PRD includes user stories with verifiable acceptance criteria. It structures the document to cover goals, functional requirements, non-goals, and success metrics to ensure implementation-ready planning.
The product requirements document is saved in Markdown format. The file is outputted under the tasks directory as prd-[feature-name].md, providing a structured and readable document for your feature planning.
The PRD generation process asks 3-5 critical clarifying questions before writing to prevent ambiguous requirements. Resolving ambiguity upfront converts a feature idea into structured, actionable plans that can be implemented without guesswork.
mseokDraft a structured PRD with goals, user stories, and success metrics.
chrislawcodesGenerate structured feature specification documents in Markdown format.
bearbinaryConverts Markdown PRDs into structured JSON task files with progress tracking.
alo-expGenerate a structured PRD from a vague problem statement.
