Skip to content
Back to skills

Create Prd

ASecurity

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

  • 207 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 27, 2026
data-aigosecurityperformance

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add jmagly/aiwg --skill create-prd --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Create Prd?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Create Prd
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jmagly-create-prd/badge)](https://www.skillsdirectory.com/skills/jmagly-create-prd)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
namespace: aiwg
name: create-prd
platforms: [all]
description: Create a Product Requirements Document (PRD) for a product feature
commandHint:
  argumentHint: '<feature description> [output-path] [--interactive] [--guidance "text"]'
  allowedTools: 'Write, TodoWrite'
  category: project-task-management
---

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/addons/aiwg-utils/skills/project-status/SKILL.md — Use to orient within the SDLC phase before generating PRD artifacts

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…