Our review

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.

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

Gathers requirements through clarifying questions
Structures user stories in AG4ONE-compatible JSON format
Defines acceptance criteria with testing requirements
Sets priorities for implementation order
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:

Copy to scripts/ag4one/prd.json
Run ./scripts/ag4one/ag4one-loop.sh
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.

Product Requirements Document Creation

Recommended for