BeClaude

prp-core

2.2kCommunity RegistryGeneralby Wirasm

Complete PRP workflow automation - create, execute, commit, and PR commands with orchestration scripts

First seen 4/17/2026

Summary

PRP-core automates the entire PRP workflow—from creating and executing product requirement prompts to committing code and opening pull requests—using orchestration scripts.

  • It helps developers ship production-ready code faster by providing a structured, repeatable process for AI-assisted development.

Overview

A collection of prompts for AI-assisted development with Claude Code.

Video Walkthrough

https://www.youtube.com/watch?v=KVOZ9s1S9Gk&lc=UgzfwxvFjo6pKEyPo1R4AaABAg

Support This Work

Found value in these resources?

Buy me a coffee: https://coff.ee/wirasm

I spent a considerable amount of time creating these resources and prompts. If you find value in this project, please consider buying me a coffee to support my work.


Transform Your Team with AI Engineering Workshops

Ready to move beyond toy demos to production-ready AI systems?

Book a workshop: https://www.rasmuswiding.com/

What you'll get:

  • Put your team on a path to become AI power users
  • Learn the exact PRP methodology used by top engineering teams
  • Hands-on training with Claude Code, PRPs, and real codebases
  • From beginner to advanced AI engineering workshops for teams and individuals

Perfect for: Engineering teams, Product teams, and developers who want AI that actually works in production

Contact me directly at [email protected]


What is PRP?

Product Requirement Prompt (PRP) = PRD + curated codebase intelligence + agent/runbook

The minimum viable packet an AI needs to ship production-ready code on the first pass.

A PRP supplies an AI coding agent with everything it needs to deliver a vertical slice of working software—no more, no less.

How PRP Differs from Traditional PRD

A traditional PRD clarifies _what_ the product must do and _why_ customers need it, but deliberately avoids _how_ it will be built.

A PRP keeps the goal and justification sections of a PRD yet adds AI-critical layers:

  • Context: Precise file paths, library versions, code snippet examples
  • Patterns: Existing codebase conventions to follow
  • Validation: Executable commands the AI can run to verify its work

Quick Start

Option 1: Copy Commands to Your Project

bash
# From your project root
cp -r /path/to/PRPs-agentic-eng/.claude/commands/prp-core .claude/commands/

Option 2: Clone Repository

bash
git clone https://github.com/Wirasm/PRPs-agentic-eng.git
cd PRPs-agentic-eng

Commands

The .claude/commands/prp-core/ directory contains the core PRP workflow commands:

Core Workflow

CommandDescription
/prp-prdInteractive PRD generator with implementation phases
/prp-planCreate implementation plan (from PRD or free-form input)
/prp-implementExecute a plan with validation loops

Issue & Debug Workflow

CommandDescription
/prp-issue-investigateAnalyze GitHub issue, create implementation plan
/prp-issue-fixExecute fix from investigation artifact
/prp-debugDeep root cause analysis with 5 Whys methodology

Git & Review

CommandDescription
/prp-commitSmart commit with natural language file targeting
/prp-prCreate PR with template support
/prp-reviewComprehensive PR code review

Autonomous Loop

CommandDescription
/prp-ralphStart autonomous loop until all validations pass
/prp-ralph-cancelCancel active Ralph loop

Ralph Loop (Autonomous Execution)

Based on Geoffrey Huntley's Ralph Wiggum technique - a self-referential loop that keeps iterating until the job is actually done.

How It Works

code
/prp-ralph .claude/PRPs/plans/my-feature.plan.md --max-iterations 20
  1. Claude implements the plan tasks
  2. Runs all validation commands (type-check, lint, tests, build)
  3. If any validation fails → fixes and re-validates
  4. Loop continues until ALL validations pass
  5. Outputs <promise>COMPLETE</promise> and exits

Each iteration, Claude sees its previous work in files and git history. It's not starting fresh - it's debugging itself.

Setup

The stop hook must be configured in .claude/settings.local.json:

json
{
  "hooks": {
    "Stop": [
      {
        "hooks": [
          {
            "type": "command",
            "command": ".claude/hooks/prp-ralph-stop.sh"
          }
        ]
      }
    ]
  }
}

Usage

bash
# Create a plan
/prp-plan "add user authentication with JWT"

# Let Ralph loose
/prp-ralph .claude/PRPs/plans/add-user-auth.plan.md --max-iterations 20

# Cancel if needed
/prp-ralph-cancel

Tips

  • Always use --max-iterations (default: 20) to prevent infinite loops
  • Works best with plans that have clear, testable validation commands
  • State is tracked in .claude/prp-ralph.state.md
  • Progress and learnings are captured in the implementation report

Workflow Overview

Large Features: PRD → Plan → Implement

code
/prp-prd "user authentication system"
    ↓
Creates PRD with Implementation Phases table
    ↓
/prp-plan .claude/PRPs/prds/user-auth.prd.md
    ↓
Auto-selects next pending phase, creates plan
    ↓
/prp-implement .claude/PRPs/plans/user-auth-phase-1.plan.md
    ↓
Executes plan, updates PRD progress, archives plan
    ↓
Repeat /prp-plan for next phase

Medium Features: Direct to Plan

code
/prp-plan "add pagination to the API"
    ↓
Creates implementation plan from description
    ↓
/prp-implement .claude/PRPs/plans/add-pagination.plan.md

Bug Fixes: Issue Workflow

code
/prp-issue-investigate 123
    ↓
Analyzes issue, creates investigation artifact
    ↓
/prp-issue-fix 123
    ↓
Implements fix, creates PR

Artifacts Structure

All artifacts are stored in .claude/PRPs/:

code
.claude/PRPs/
├── prds/              # Product requirement documents
├── plans/             # Implementation plans
│   └── completed/     # Archived completed plans
├── reports/           # Implementation reports
├── issues/            # Issue investigation artifacts
│   └── completed/     # Archived completed investigations
└── reviews/           # PR review reports

PRD Phases

PRDs include an Implementation Phases table for tracking progress:

markdown
| #   | Phase | Description | Status      | Parallel | Depends | PRP Plan |
| --- | ----- | ----------- | ----------- | -------- | ------- | -------- |
| 1   | Auth  | User login  | complete    | -        | -       | [link]   |
| 2   | API   | Endpoints   | in-progress | -        | 1       | [link]   |
| 3   | UI    | Frontend    | pending     | with 4   | 2       | -        |
| 4   | Tests | Test suite  | pending     | with 3   | 2       | -        |
  • Status: pendingin-progresscomplete
  • Parallel: Phases that can run concurrently (in separate worktrees)
  • Depends: Phases that must complete first

PRP Best Practices

  1. Context is King: Include ALL necessary documentation, examples, and caveats
  2. Validation Loops: Provide executable tests/lints the AI can run and fix
  3. Information Dense: Use keywords and patterns from the codebase
  4. Bounded Scope: Each plan should be completable by an AI in one loop

Project Structure

code
your-project/
├── .claude/
│   ├── commands/prp-core/   # PRP commands
│   ├── PRPs/                # Generated artifacts
│   └── agents/              # Custom subagents
├── PRPs/
│   ├── templates/           # PRP templates
│   └── ai_docs/             # Library documentation
├── CLAUDE.md                # Project-specific guidelines
└── src/                     # Your source code

Parallel Development with Worktrees

When PRD phases can run in parallel:

bash
# Phase 3 and 4 can run concurrently
git worktree add -b phase-3-ui ../project-phase-3
git worktree add -b phase-4-tests ../project-phase-4

# Run Claude in each
cd ../project-phase-3 && claude
cd ../project-phase-4 && claude

Resources

Templates (PRPs/templates/)

  • prp_base.md - Comprehensive PRP template
  • prp_story_task.md - Story/task template
  • prp_planning.md - Planning template

AI Documentation (PRPs/ai_docs/)

Curated documentation for Claude Code context injection.

Legacy Commands

Previous command versions are preserved in old-prp-commands/ for reference.


License

MIT License


Support

I spent a considerable amount of time creating these resources and prompts. If you find value in this project, please consider buying me a coffee to support my work.

Buy me a coffee: https://coff.ee/wirasm


The goal is one-pass implementation success through comprehensive context.

Install & Usage

1
Create the agents directory
mkdir -p .claude/agents
2
Save the agent file

Add the configuration to .claude/agents/prp-core.md

3
Invoke with @agent-name
@prp-core

Use Cases

Automate the creation of a PRP from a product requirement document and codebase context.
Execute a PRP to generate a vertical slice of working code with a single command.
Commit generated code with standardized commit messages and push to a remote repository.
Open a pull request directly from the command line after PRP execution.
Orchestrate the full PRP lifecycle: create, execute, commit, and PR in one workflow.
Integrate PRP automation into CI/CD pipelines for consistent AI-assisted development.

Usage Examples

1

/prp-core create --prd 'Add user authentication' --context src/

2

/prp-core execute --prp-file ./prps/auth.prp

3

/prp-core commit-and-pr --message 'Implement OAuth2 login'

View source on GitHub

Security Audits

LicenseUnknownSourceWarnRepositoryPass

Frequently Asked Questions

What is prp-core?

PRP-core automates the entire PRP workflow—from creating and executing product requirement prompts to committing code and opening pull requests—using orchestration scripts. It helps developers ship production-ready code faster by providing a structured, repeatable process for AI-assisted development.

How to install prp-core?

To install prp-core: create the agents directory (mkdir -p .claude/agents), then add the config to .claude/agents/prp-core.md. Finally, @prp-core in Claude Code.

What is prp-core best for?

prp-core is a agent categorized under General. Created by Wirasm.

What can I use prp-core for?

prp-core is useful for: Automate the creation of a PRP from a product requirement document and codebase context.; Execute a PRP to generate a vertical slice of working code with a single command.; Commit generated code with standardized commit messages and push to a remote repository.; Open a pull request directly from the command line after PRP execution.; Orchestrate the full PRP lifecycle: create, execute, commit, and PR in one workflow.; Integrate PRP automation into CI/CD pipelines for consistent AI-assisted development..