Our review

This skill creates comprehensive Product Requirements Documents (PRDs) for AG4ONE autonomous development cycles, structuring requirements as user stories with acceptance criteria and priorities.

Strengths

Complete and standardized PRD structure tailored for AG4ONE cycles
Generates user stories with testable acceptance criteria
Clear prioritization for implementation order
Direct integration with AG4ONE Ralph loop for automatic execution

Limitations

Requires a clear initial feature description to be effective
Generated PRDs are limited to a specific AG4ONE JSON format
May need manual adjustments if the project uses complex codebases

When to use it

Use this skill when starting a new feature or project within an AG4ONE workflow and need a structured PRD to guide autonomous development.

When not to use it

Avoid this skill if you are working on minor changes that do not require formal documentation, or if your project does not use the AG4ONE framework.

Examples

Create PRD for task priority system

Load ag4one PRD skill and create PRD for a task priority system where users can assign priority levels to tasks

Create PRD for user authentication module

Create PRD for a user authentication module with login, logout, and password reset features using AG4ONE

Generate PRD for reporting dashboard

Generate a PRD for a reporting dashboard that displays key metrics and allows exporting PDFs

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 Creator

Recommended for