prd

Generate a structured PRD with goals, user stories, and acceptance criteria.

1.4k|162|Updated Sep 5, 2025
One-click install
npx skills add https://github.com/inkeep/agents --skill prd-inkeep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/inkeep/agents/tree/main/.agents/skills/prd
Command: npx skills add https://github.com/inkeep/agents --skill prd-inkeep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to align on project scope and acceptance criteria before building features. The PRD skill automates the creation of a formal Product Requirements Document from a concise idea, reducing miscommunication and rework.

Core Features & Use Cases

  • Structured PRD with sections for Goals, User Stories, Acceptance Criteria, Open Questions, Non-Goals
  • Workflow guidance: Draft, Iterate, Improve to match clarity and alignment needs
  • Auto-saves to tasks/prd-[feature-name].md for traceability and versioning
  • Examples: Create a PRD for a new onboarding flow, a performance optimization, or a new admin feature

Quick Start

Provide a feature name and desired workflow (Draft, Iterate, Improve). The skill will generate a complete PRD and save it to tasks/prd-[feature-name].md. You can then review and refine the document in subsequent iterations.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I create a product requirements document from a feature idea?

To create a product requirements document, provide a feature name and workflow to generate a structured PRD with Goals, User Stories, Acceptance Criteria, and Non-Goals. The document is saved to tasks/prd-[feature-name].md for versioning.

What sections should a PRD include for user stories and acceptance criteria?

A PRD should include Goals, User Stories, Acceptance Criteria, Non-Goals, and Open Questions to ensure alignment. This structure clarifies project scope and reduces miscommunication before feature development begins.

How do I write acceptance criteria for a new feature specification?

Writing acceptance criteria for a feature specification involves defining clear pass/fail conditions within a structured PRD. The skill automates this by generating criteria alongside user stories from your concise feature idea.

Can I iterate on an existing PRD to improve clarity and alignment?

Yes, you can iterate on an existing PRD by selecting the Iterate or Improve workflow. This refines the generated document, enhancing alignment on project scope and acceptance criteria across the team.

What is the best way to document non-goals and open questions for product planning?

The best way to document non-goals and open questions is within a formal PRD structure. This prevents scope creep and highlights unresolved decisions early, ensuring teams address potential blockers before development.

Does this PRD generator save files for traceability during product management?

Yes, the PRD generator saves files directly to tasks/prd-[feature-name].md. This provides traceability and versioning so teams can track changes throughout the product planning lifecycle.