create-prd

Generate a lightweight strategic PRD defining vision, problem, metrics, and scope.

157|28|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/Fr-e-d/GAAI-framework --skill create-prd-fr-e-d
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-prd
Source: https://github.com/Fr-e-d/GAAI-framework/tree/main/.gaai/core/skills/discovery/create-prd
Command: npx skills add https://github.com/Fr-e-d/GAAI-framework --skill create-prd-fr-e-d

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of starting new products or initiatives without clear strategic direction, ensuring alignment on product vision, user problems, and scope before development begins.

Core Features & Use Cases

  • Strategic Alignment: Produces a lightweight Product Requirements Document (PRD) to define the core product vision.
  • Problem Definition: Clearly articulates the user problem and target audience.
  • Scope Management: Establishes clear boundaries for what is in and out of scope for the initiative.
  • Use Case: When launching a new mobile app, use this Skill to define its core purpose, identify the primary user base, and set initial success metrics before any feature development starts.

Quick Start

Use the create-prd skill to produce a lightweight strategic PRD for a new customer feedback portal.

Frequently Asked Questions about create-prd

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

FAQPage Schema
How do I define product vision and scope for a new initiative?

To define product vision and scope, you need a lightweight strategic Product Requirements Document (PRD) that clearly articulates the user problem, target audience, value hypothesis, and success metrics before development starts.

What is a PRD and when do I need to create one?

A PRD is a strategic document that establishes product vision and scope boundaries. You need to create one when starting a new product, launching a major initiative, or facing strategic uncertainty to ensure alignment.

What's the best way to structure product requirements for a new mobile app?

The best way to structure product requirements is by generating a lightweight PRD that defines the core purpose, identifies the primary user base, and sets initial success metrics before any feature development starts.

What inputs are required to generate a product requirements document?

Generating a product requirements document requires inputs for human intent, the core user problem, and target users. You can also provide optional known constraints to help establish clear scope boundaries.

Can I use a lightweight PRD for managing scope boundaries during strategic uncertainty?

Yes, a lightweight PRD is explicitly designed to manage scope boundaries and define what is in and out of scope. It is highly effective for resolving strategic uncertainty and aligning teams before development.