Agent skill

Prd

by YougLin-dev in YougLin-dev/Aha-Loop

Generates Product Requirements Documents (PRD) for new features.

MITAuto-check passedProduct & Project Management

Install Prd

skills CLI
$ npx skills add YougLin-dev/Aha-Loop --skill prd -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install YougLin-dev/Aha-Loop prd --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/YougLin-dev/Aha-Loop.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/prd .claude/skills/prd && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
prd
GitHub stars
181
Token cost
~2.3k tokens
SKILL.md length
581 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
MIT

At a glance

Generates Product Requirements Documents (PRD) for new features.

  • Works in 2 steps: Clarifying Questions → PRD Structure
  • Planning features
  • SKILL.md covers Workspace Mode Note, The Job, Step 1: Clarifying Questions and Step 2: PRD Structure, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Prd is an agent skill from YougLin-dev/Aha-Loop. Generates Product Requirements Documents (PRD) for new features. Use when planning features or starting projects. Triggers on: create prd, write prd, plan feature, requirements, spec out.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering PRD writing. The repository describes itself as: [MVP] Aha Loop is a fully autonomous AI development system, extended from the core ideas of Ralph. It's not just an execution engine, but a complete AI development framework with… The licence is MIT.

When your agent uses it

  • Planning features
  • Starting projects

Example prompts

  • “Use the prd skill to generate Product Requirements Documents (PRD) for new features”
  • “/prd”

Workflow steps

2 steps, taken from the step headings in SKILL.md.

  1. Clarifying Questions
  2. PRD Structure

What it can do on your machine

Read from SKILL.md and the folder at commit 8d799b2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Prd loads about 2.3k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 581 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from YougLin-dev/Aha-Loop at commit 8d799b2, republished under its MIT licence (© YougLin-dev). 581 words, ~2,255 tokens.

Download SKILL.mdSave it as .claude/skills/prd/SKILL.md (or your agent's skills folder).
name
prd
description
Generates Product Requirements Documents (PRD) for new features. Use when planning features or starting projects. Triggers on: create prd, write prd, plan feature, requirements, spec out.

PRD Generator

Create detailed Product Requirements Documents that are clear, actionable, and suitable for implementation.

Workspace Mode Note

When running in workspace mode, save PRDs to .aha-loop/tasks/ instead of tasks/. The orchestrator will provide the actual paths in the prompt context.


The Job

  1. Receive a feature description from the user
  2. Ask 3-5 essential clarifying questions (with lettered options)
  3. Generate a structured PRD based on answers
  4. Save to tasks/prd-[feature-name].md

Important: Do NOT start implementing. Just create the PRD.


Step 1: Clarifying Questions

Ask only critical questions where the initial prompt is ambiguous. Focus on:

  • Problem/Goal: What problem does this solve?
  • Core Functionality: What are the key actions?
  • Scope/Boundaries: What should it NOT do?
  • Success Criteria: How do we know it's done?
Format Questions Like This:
1. What is the primary goal of this feature?
   A. Improve user onboarding experience
   B. Increase user retention
   C. Reduce support burden
   D. Other: [please specify]

2. Who is the target user?
   A. New users only
   B. Existing users only
   C. All users
   D. Admin users only

3. What is the scope?
   A. Minimal viable version
   B. Full-featured implementation
   C. Just the backend/API
   D. Just the UI

This lets users respond with "1A, 2C, 3B" for quick iteration.


Step 2: PRD Structure

Generate the PRD with these sections:

1. Introduction/Overview

Brief description of the feature and the problem it solves.

2. Goals

Specific, measurable objectives (bullet list).

3. User Stories

Each story needs:

  • Title: Short descriptive name
  • Description: "As a [user], I want [feature] so that [benefit]"
  • Acceptance Criteria: Verifiable checklist of what "done" means
  • Research Topics: Questions to investigate before implementation (for complex stories)

Each story should be small enough to implement in one focused session.

Format:

markdown
### US-001: [Title]
**Description:** As a [user], I want [feature] so that [benefit].

**Research Topics:** (optional, for complex stories)
- [ ] Question about technology choice or best practice
- [ ] Question about existing patterns in codebase
- [ ] Question about third-party library usage

**Acceptance Criteria:**
- [ ] Specific verifiable criterion
- [ ] Another criterion
- [ ] Typecheck/lint passes
- [ ] **[UI stories only]** Verify in browser using dev-browser skill

Important:

  • Acceptance criteria must be verifiable, not vague. "Works correctly" is bad. "Button shows confirmation dialog before deleting" is good.
  • For any story with UI changes: Always include "Verify in browser using dev-browser skill" as acceptance criteria. This ensures visual verification of frontend work.
  • Research Topics help the research phase focus on the right questions. Include them when:
    • Using an unfamiliar third-party library
    • Multiple implementation approaches exist
    • Performance or scalability concerns
    • Complex integration with existing systems
4. Functional Requirements

Numbered list of specific functionalities:

  • "FR-1: The system must allow users to..."
  • "FR-2: When a user clicks X, the system must..."

Be explicit and unambiguous.

5. Non-Goals (Out of Scope)

What this feature will NOT include. Critical for managing scope.

6. Design Considerations (Optional)
  • UI/UX requirements
  • Link to mockups if available
  • Relevant existing components to reuse
Show full SKILL.md (227 more words)Show less
7. Technical Considerations (Optional)
  • Known constraints or dependencies
  • Integration points with existing systems
  • Performance requirements
8. Success Metrics

How will success be measured?

  • "Reduce time to complete X by 50%"
  • "Increase conversion rate by 10%"
9. Open Questions

Remaining questions or areas needing clarification.


Writing for Junior Developers

The PRD reader may be a junior developer or AI agent. Therefore:

  • Be explicit and unambiguous
  • Avoid jargon or explain it
  • Provide enough detail to understand purpose and core logic
  • Number requirements for easy reference
  • Use concrete examples where helpful

Output

  • Format: Markdown (.md)
  • Location: tasks/
  • Filename: prd-[feature-name].md (kebab-case)

Example PRD

markdown
# PRD: Task Priority System

## Introduction

Add priority levels to tasks so users can focus on what matters most. Tasks can be marked as high, medium, or low priority, with visual indicators and filtering to help users manage their workload effectively.

## Goals

- Allow assigning priority (high/medium/low) to any task
- Provide clear visual differentiation between priority levels
- Enable filtering and sorting by priority
- Default new tasks to medium priority

## User Stories

### US-001: Add priority field to database
**Description:** As a developer, I need to store task priority so it persists across sessions.

**Research Topics:**
- [ ] Best practices for database enum fields in this stack
- [ ] Migration rollback strategies for schema changes

**Acceptance Criteria:**
- [ ] Add priority column to tasks table: 'high' | 'medium' | 'low' (default 'medium')
- [ ] Generate and run migration successfully
- [ ] Typecheck passes

### US-002: Display priority indicator on task cards
**Description:** As a user, I want to see task priority at a glance so I know what needs attention first.

**Research Topics:**
- [ ] Accessible color schemes for priority indicators (WCAG compliance)
- [ ] Existing badge/tag components in codebase to reuse

**Acceptance Criteria:**
- [ ] Each task card shows colored priority badge (red=high, yellow=medium, gray=low)
- [ ] Priority visible without hovering or clicking
- [ ] Typecheck passes
- [ ] Verify in browser using dev-browser skill

### US-003: Add priority selector to task edit
**Description:** As a user, I want to change a task's priority when editing it.

**Acceptance Criteria:**
- [ ] Priority dropdown in task edit modal
- [ ] Shows current priority as selected
- [ ] Saves immediately on selection change
- [ ] Typecheck passes
- [ ] Verify in browser using dev-browser skill

### US-004: Filter tasks by priority
**Description:** As a user, I want to filter the task list to see only high-priority items when I'm focused.

**Research Topics:**
- [ ] URL state management patterns in this codebase
- [ ] Existing filter implementations to follow as pattern

**Acceptance Criteria:**
- [ ] Filter dropdown with options: All | High | Medium | Low
- [ ] Filter persists in URL params
- [ ] Empty state message when no tasks match filter
- [ ] Typecheck passes
- [ ] Verify in browser using dev-browser skill

## Functional Requirements

- FR-1: Add `priority` field to tasks table ('high' | 'medium' | 'low', default 'medium')
- FR-2: Display colored priority badge on each task card
- FR-3: Include priority selector in task edit modal
- FR-4: Add priority filter dropdown to task list header
- FR-5: Sort by priority within each status column (high to medium to low)

## Non-Goals

- No priority-based notifications or reminders
- No automatic priority assignment based on due date
- No priority inheritance for subtasks

## Technical Considerations

- Reuse existing badge component with color variants
- Filter state managed via URL search params
- Priority stored in database, not computed

## Success Metrics

- Users can change priority in under 2 clicks
- High-priority tasks immediately visible at top of lists
- No regression in task list performance

## Open Questions

- Should priority affect task ordering within a column?
- Should we add keyboard shortcuts for priority changes?

Checklist

Before saving the PRD:

  • Asked clarifying questions with lettered options
  • Incorporated user's answers
  • User stories are small and specific
  • Complex stories have research topics defined
  • Functional requirements are numbered and unambiguous
  • Non-goals section defines clear boundaries
  • Saved to tasks/prd-[feature-name].md

Research Topics Guidelines

When adding research topics, consider:

Good research topics:

  • "How does library X handle Y?" (specific, answerable)
  • "What existing patterns does this codebase use for Z?"
  • "Performance implications of approach A vs B"
  • "Best practices for implementing feature X"

Bad research topics:

  • "How to code this" (too vague)
  • "Make it work" (not a question)
  • "Everything about library X" (too broad)

When to include research topics:

  • First time using a library in this project
  • Multiple valid approaches exist
  • Performance-sensitive implementation
  • Security-sensitive implementation
  • Complex integration with external systems

© YougLin-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/prd of YougLin-dev/Aha-Loop.

Open the folder on GitHubat commit 8d799b2

Compare with similar skills

Prd next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Prd compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Prd this skillYougLin-dev/Aha-Loop181—~2.3kAutomated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Ralph Tui Create Beadssubsy/ralph-tui2.5k1 repos~2.6kAutomated safety check: PassMIT
Trellis Brainstormanjiemo/SunnyBeach1787 repos~4kAutomated safety check: PassApache-2.0
Adversarial Speczscole/adversarial-spec5561 repos~8.3kAutomated safety check: NotesMIT
Ralph Tui Create Beads Rustsubsy/ralph-tui2.5k1 repos~2.8kAutomated safety check: PassMIT

Similar skills

  • Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed
  • Ralph Tui Create Beads

    subsy/ralph-tui

    Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.

    2.5k GitHub starsUsed in 1 repo~2.6k tokens
    Product & Project ManagementAuto-check passed
  • Trellis Brainstorm

    anjiemo/SunnyBeach

    Guides collaborative requirements discovery before implementation.

    178 GitHub starsUsed in 7 repos~4k tokens
    Product & Project ManagementAuto-check passed
  • Adversarial Spec

    zscole/adversarial-spec

    Iteratively refine a product spec by debating with multiple LLMs (GPT, Gemini, Grok, etc.) until all models agree.

    556 GitHub starsUsed in 1 repo~8.3k tokens
    Product & Project ManagementAuto-check: notes
  • Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).

    2.5k GitHub starsUsed in 1 repo~2.8k tokens
    Product & Project ManagementAuto-check passed
  • To Issues

    ywwynm/EverythingDone

    Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

    144 GitHub starsUsed in 12 repos~893 tokens
    Product & Project ManagementAuto-check passed

More from YougLin-dev/Aha-Loop

All 15 skills in this repo
  • God Member

    YougLin-dev/Aha-Loop

    Defines God Committee member behavior and responsibilities with oversight authority.

    181 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed
  • Architect

    YougLin-dev/Aha-Loop

    Designs system architecture and selects technology stack based on vision analysis.

    181 GitHub stars~2.2k tokensUpdated 8 mo ago
    Auto-check passed
  • Doc Review

    YougLin-dev/Aha-Loop

    Reviews and cleans up outdated documentation. An agent skill from YougLin-dev/Aha-Loop.

    181 GitHub stars~1.5k tokensUpdated 8 mo ago
    Auto-check passed
  • God Consensus

    YougLin-dev/Aha-Loop

    Guides God Committee members through consensus-building for collective decisions.

    181 GitHub stars~2k tokensUpdated 8 mo ago
    Auto-check passed
  • God Intervention

    YougLin-dev/Aha-Loop

    Guides God Committee members through executing interventions.

    181 GitHub stars~2.3k tokensUpdated 8 mo ago
    Auto-check passed
  • Parallel Explore

    YougLin-dev/Aha-Loop

    Guides parallel exploration of multiple implementation approaches using git worktrees.

    181 GitHub stars~1.9k tokensUpdated 8 mo ago
    Auto-check passed

Questions about Prd

What does Prd do?

Generates Product Requirements Documents (PRD) for new features. Prd is an agent skill from YougLin-dev/Aha-Loop. Generates Product Requirements Documents (PRD) for new features.

When should I use Prd?

Prd fits situations like: planning features; starting projects.

How do I install Prd in Claude Code?

Run `npx skills add YougLin-dev/Aha-Loop --skill prd -a claude-code`. Or copy the skill folder (.agents/skills/prd in YougLin-dev/Aha-Loop) into .claude/skills/prd in your project. Claude Code loads it when a task matches its description.

How do I install Prd in Codex?

Run `npx skills add YougLin-dev/Aha-Loop --skill prd -a codex`. Or copy the skill folder (.agents/skills/prd in YougLin-dev/Aha-Loop) into .agents/skills/prd in your project. Codex loads it when a task matches its description.

Can I use Prd in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add YougLin-dev/Aha-Loop --skill prd -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prd, .gemini/skills/prd, .github/skills/prd and .opencode/skills/prd in your project.

What does Prd need to run?

SKILL.md names no scripts, command-line tools or credentials: Prd is instructions for the agent only.

Does Prd access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Prd safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Prd use?

Prd is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Prd use?

About 2.3k tokens (SKILL.md is roughly 9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Prd?

Skills that share tags, products or a category with Prd: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Trellis Brainstorm (anjiemo/SunnyBeach, 178 stars) and Adversarial Spec (zscole/adversarial-spec, 556 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Prd?

YougLin-dev (a GitHub user) maintains it in YougLin-dev/Aha-Loop, which has 181 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on February 3, 2026.

Source: YougLin-dev/Aha-Loop on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.