Codex

create-prd

Create a Product Requirements Document (PRD) for a product feature

104 stars

Best use case

create-prd is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

It is a strong fit for teams already working in Codex.

Create a Product Requirements Document (PRD) for a product feature

Teams using create-prd should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/create-prd/SKILL.md --create-dirs "https://raw.githubusercontent.com/jmagly/aiwg/main/.agents/skills/create-prd/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/create-prd/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How create-prd Compares

Feature / Agentcreate-prdStandard Approach
Platform SupportCodexLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Create a Product Requirements Document (PRD) for a product feature

Which AI agents support this skill?

This skill is designed for Codex.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

Create a comprehensive Product Requirements Document (PRD) based on the feature description provided.

## Instructions:
1. Parse the arguments:
   - First argument: Feature description (required)
   - Second argument: Output path (optional, defaults to `PRD.md` in current directory)

2. Create a well-structured PRD that includes:
   - **Executive Summary**: Brief overview of the feature
   - **Problem Statement**: What problem does this solve?
   - **Objectives**: Clear, measurable goals
   - **User Stories**: Who are the users and what are their needs?
   - **Functional Requirements**: What the feature must do
   - **Non-Functional Requirements**: Performance, security, usability standards
   - **Success Metrics**: How will we measure success?
   - **Assumptions & Constraints**: Any limitations or dependencies
   - **Out of Scope**: What this PRD does NOT cover

3. Focus on:
   - User needs and business value (not technical implementation)
   - Clear, measurable objectives
   - Specific acceptance criteria
   - User personas and their journey

4. Use the TodoWrite tool to track PRD sections as you complete them

## Example usage:
- `/create-prd "Add dark mode toggle to settings"`
- `/create-prd "Implement user authentication with SSO" auth-PRD.md`

Feature description: $ARGUMENTS

## References

- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/instruction-comprehension.md — Fully parse the feature description before drafting; track all multi-part requirements
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/human-authorization.md — Confirm scope and output location before writing; PRD commits product direction
- @$AIWG_ROOT/agentic/code/frameworks/sdlc-complete/skills/intake-start/SKILL.md — Intake validation skill that feeds the requirements context a PRD builds on
- @$AIWG_ROOT/agentic/code/frameworks/sdlc-complete/skills/project-status/SKILL.md — Use to orient within the SDLC phase before generating PRD artifacts