idea-to-prd

Convert a one-line product idea into a complete PRD document.

12|2|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/haomingz/kimi-skills --skill idea-to-prd-haomingz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: idea-to-prd
Source: https://github.com/haomingz/kimi-skills/tree/main/skills/idea-to-prd
Command: npx skills add https://github.com/haomingz/kimi-skills --skill idea-to-prd-haomingz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill converts vague product ideas into a complete PRD, including user stories, feature lists, MoSCoW prioritization, and acceptance criteria, saving teams from scattered planning notes and incomplete documents.

Core Features & Use Cases

  • Structured PRD generation: converts a one-line idea into a full PRD with narrative, user stories, requirements, and success criteria.
  • Phase-aligned SOP workflow: supports Requirement Elicitation, Personas & User Stories, Functional & Non-functional Requirements, MoSCoW prioritization, and Acceptance Criteria.
  • Output-ready documentation: produces a PRD document with clear mappings between user stories and features for review and execution.

Quick Start

Provide a one-sentence product idea, and the Agent will generate a complete PRD following the SOP.

Frequently Asked Questions about idea-to-prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a product idea into a complete PRD with user stories and acceptance criteria?

The skill automates PRD generation by applying a phase-aligned SOP workflow covering requirement elicitation, personas, functional requirements, and MoSCoW prioritization to transform a one-line idea into structured, output-ready documentation.

What is MoSCoW prioritization and how does it apply to agile product management?

MoSCoW prioritization categorizes features into Must, Should, Could, and Won't tiers. This skill applies it during PRD generation to structure agile requirements, ensuring clear scope boundaries and prioritized execution across generated user stories.

Can I generate functional and non-functional requirements from a single vague idea?

Yes, the skill processes a vague idea through a phase-aligned SOP to generate both functional and non-functional requirements. It outputs a complete PRD with clear mappings between user stories and feature lists for review and execution.

Does this PRD generation workflow support early-stage agile planning with no prior documentation?

Yes, this PRD generation workflow supports early-stage agile planning from scratch. You provide a one-sentence product idea, and it enforces a defined frontmatter-guided workflow to produce complete requirement artifacts without needing prior documentation.

What is the best way to structure acceptance criteria for generated user stories?

The best way to structure acceptance criteria is using the built-in SOP workflow, which generates them alongside user stories and functional requirements. This ensures clear mappings between features and validation conditions within the final PRD document.