Product Requirements Document Creation

VerifiedCaution

Generates product requirements documents (PRDs) tailored for AG4ONE's autonomous development cycles. Structures user stories with acceptance criteria and priorities, outputting a JSON file ready for integration with the Ralph loop.

Sby Skills Guide Bot
DevelopmentBeginner
6/2/2026
Claude Code
#product-requirements#prd#user-stories#ag4one#requirements-management

Recommended for

Automated summary

This skill helps create a structured Product Requirements Document (PRD) in JSON format, suitable for AG4ONE autonomous development cycles.

Strengths

  • Provides a structured format for user stories and acceptance criteria
  • Integrates with the AG4ONE Ralph loop for automated implementation
  • Helps clarify requirements through interactive questions
  • Outputs a standardized JSON file ready for use

Limitations

  • Requires familiarity with AG4ONE workflow
  • May not cover all edge cases without manual refinement
  • Output is specific to AG4ONE format
When to use it

Use this when starting a new feature that will be developed using the AG4ONE autonomous development system.

When not to use it

Do not use this if you are not following the AG4ONE methodology or need a more flexible documentation format.

Security analysis

Caution
Quality score80/100

The skill requires Bash access, and while the intended use is to save a JSON file, it could potentially be directed to execute arbitrary shell commands, posing a risk of system modification.

Findings
  • •Allows Bash execution, which could be used for destructive actions if misused
How this analysis is made

Examples

Task priority system
Load ag4one PRD skill and create PRD for a task priority system with database schema, UI for setting priority, and sorting by priority.
User authentication
Load ag4one PRD skill and create PRD for user authentication feature including login, registration, and password reset.
Data export functionality
Load ag4one PRD skill and create PRD for exporting project data to CSV and PDF formats.

name: prd description: Create comprehensive Product Requirements Documents (PRDs) allowed-tools:

  • Read
  • Write
  • Bash
  • Glob

AG4ONE PRD Skill

Overview

This skill helps create comprehensive Product Requirements Documents (PRDs) for AG4ONE autonomous development cycles.

Usage

Load this skill and create a PRD for your feature:

Load ag4one PRD skill and create PRD for [your feature description]

What it does

  1. Gathers requirements through clarifying questions
  2. Structures user stories in AG4ONE-compatible JSON format
  3. Defines acceptance criteria with testing requirements
  4. Sets priorities for implementation order
  5. Saves output to prd-[feature-name].json ready for Ralph loop

PRD Structure

The generated PRD includes:

  • Project metadata (name, branch, description)
  • User stories with IDs, titles, descriptions
  • Acceptance criteria for each story
  • Priority levels for implementation order
  • AG4ONE integration considerations

Best Practices

  • Small, focused stories - Each story should fit in one iteration
  • Clear acceptance criteria - Testable and verifiable outcomes
  • Priority ordering - Dependencies and importance considered
  • AG4ONE compliance - Works with Ralph loop system

Integration

After creating PRD:

  1. Copy to scripts/ag4one/prd.json
  2. Run ./scripts/ag4one/ag4one-loop.sh
  3. AG4ONE Ralph loop will implement stories automatically

Example Output

{
  "project": "TaskPriority",
  "branchName": "ag4one/task-priority", 
  "description": "Task priority system with AG4ONE workflow",
  "userStories": [
    {
      "id": "US-001",
      "title": "Database schema",
      "description": "Add priority field to tasks table",
      "acceptanceCriteria": [
        "Migration runs successfully",
        "Typecheck passes"
      ],
      "priority": 1,
      "passes": false
    }
  ]
}

AG4ONE PRD Skill - Structured requirements for autonomous development.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/product-requirements-document-creation-mmbizjfp/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/product-requirements-document-creation-mmbizjfp' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/product-requirements-document-creation-mmbizjfp/download' --output '.skill-downloads/product-requirements-document-creation-mmbizjfp/SKILL.md.part' && mv '.skill-downloads/product-requirements-document-creation-mmbizjfp/SKILL.md.part' '.skill-downloads/product-requirements-document-creation-mmbizjfp/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/product-requirements-document-creation-mmbizjfp/SKILL.md' && test -s '.skill-downloads/product-requirements-document-creation-mmbizjfp/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/prd' && cp -R '.skill-downloads/product-requirements-document-creation-mmbizjfp' '.claude/skills/prd'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/product-requirements-document-creation-mmbizjfp'

openskills read 'product-requirements-document-creation-mmbizjfp'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/product-requirements-document-creation-mmbizjfp/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills