GAAI-framework create-prd

Produce a lightweight strategic PRD that defines product vision, user problem, value hypothesis, success metrics, and scope boundaries. Activate only when starting a new product, launching a major initiative, or facing strategic uncertainty.

install

source · Clone the upstream repo

git clone https://github.com/Fr-e-d/GAAI-framework

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/Fr-e-d/GAAI-framework "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.gaai/core/skills/discovery/create-prd" ~/.claude/skills/fr-e-d-gaai-framework-create-prd && rm -rf "$T"

manifest: .gaai/core/skills/discovery/create-prd/SKILL.md

source content

Create PRD

Purpose / When to Activate

Activate when:

Starting a new product
Launching a major new initiative
Facing strategic uncertainty
Needing strong alignment before Epics begin

Skip when adding small features, tweaking existing flows, or implementing obvious improvements — go directly to Epics & Stories in those cases.

Process

Clarify the core user problem before any solution
Identify target users (primary and secondary)
Define the value hypothesis: if this succeeds, what changes for users?
State explicit success metrics
Define scope: what is IN and what is OUT
Document constraints and assumptions
Output a lean PRD using the canonical template

Output Format

Produces a file at

contexts/artefacts/prd/{name}.prd.md

using

contexts/artefacts/prd/_template.prd.md

Key sections:

Vision
User Problem
Target Users
Value Hypothesis
Success Metrics
Scope (in / out)
Constraints & Assumptions
Decomposition Path → Epics → Stories

Quality Checks

Problem is framed before solution
Value is explicit, not implied
Scope boundaries are clear
Success metrics are measurable
No technical design decisions included

Non-Goals

This skill must NOT:

Generate Epics or Stories (separate skills)
Make architectural decisions
Be invoked for small feature additions

Always ask WHY before WHAT.