app-prd

Convert unstructured product concepts into section-numbered PRD.md files and submit pull requests.

45|7|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/richkuo/rk-skills --skill app-prd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-prd
Source: https://github.com/richkuo/rk-skills/tree/main/skills/app-prd
Command: npx skills add https://github.com/richkuo/rk-skills --skill app-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the ambiguity and manual effort involved in drafting product requirements, ensuring that raw ideas are transformed into structured, implementable documentation that serves as a single source of truth for development teams.

Core Features & Use Cases

  • Automated PRD Generation: Converts messy idea dumps into section-numbered, professional PRD.md files.
  • Workflow Integration: Handles repository bootstrapping, worktree management, and PR creation automatically.
  • Use Case: When you have a rough concept for a new feature or app, use this skill to generate a complete specification including goals, platform requirements, pricing, and open questions, ready for team review.

Quick Start

Use the app-prd skill to turn the current idea dump into a formal product requirements document committed to the repository.

Frequently Asked Questions about app-prd

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

FAQPage Schema
How do I turn raw product ideas into a structured PRD?

To turn raw product ideas into a structured PRD, you can use workflow automation to transform unstructured concepts into formal, section-numbered Product Requirements Documents. This process ensures raw idea dumps become implementable specifications ready for team review.

What is the best way to manage product requirements documentation in version control?

Managing product requirements documentation in version control is best handled by automating repository bootstrapping, worktree branch creation, and pull request submission. This ensures your PRD is committed directly to the repository as a single source of truth.

How do I handle ambiguous requirements when generating product documentation?

To handle ambiguous requirements when generating product documentation, the system transcribes your inputs verbatim while strictly flagging any uncertainties. These ambiguities are then automatically routed to an open questions section for later resolution.

Can I automate the entire PRD workflow from idea generation to pull request?

Yes, you can automate the entire PRD workflow from idea generation to pull request. The system manages the end-to-end lifecycle, automatically creating a worktree branch, generating the PRD.md file, and submitting the pull request for you.

Does automated PRD generation work without manual formatting?

Yes, automated PRD generation works without manual formatting by directly converting messy idea dumps into professional, section-numbered PRD.md files. It structures goals, platform requirements, pricing, and open questions automatically.

What should I not expect when using automated product requirements generation?

When using automated product requirements generation, you should not expect the system to silently alter or interpret your ambiguous inputs. It strictly enforces data integrity by transcribing requirements verbatim and flagging uncertainties instead of guessing intent.