prp-core
Complete PRP workflow automation - create, execute, commit, and PR commands with orchestration scripts
View on GitHubTable of content
Complete PRP workflow automation - create, execute, commit, and PR commands with orchestration scripts
Installation
npx claude-plugins install @Wirasm/prp-marketplace/prp-core
Contents
Folders: agents, commands, hooks, skills
Files: README.md
Documentation
Complete PRP (Product Requirement Prompt) workflow automation for Claude Code.
Overview
This plugin provides a comprehensive workflow for creating, executing, and shipping features using the PRP methodology - where PRP = PRD + curated codebase intelligence + agent/runbook designed to enable AI agents to ship production-ready code on the first pass.
Commands
Core Workflow
| Command | Description |
|---|---|
/prp-prd | Interactive PRD generator with implementation phases |
/prp-plan | Create implementation plan (from PRD or free-form input) |
/prp-implement | Execute a plan with validation loops |
Issue Workflow
| Command | Description |
|---|---|
/prp-issue-investigate | Analyze GitHub issue, create implementation plan |
/prp-issue-fix | Execute fix from investigation artifact |
Git & Review
| Command | Description |
|---|---|
/prp-commit | Smart commit with natural language file targeting |
/prp-pr | Create PR with template support |
/prp-review | Comprehensive PR code review |
/prp-review-agents | Multi-agent PR review (comments, tests, errors, types, code, docs, simplify) |
Agents
Specialized agents for code analysis and review workflows.
Codebase Analysis
| Agent | Description |
|---|---|
codebase-analyst | Documents HOW code works with file:line references |
codebase-explorer | Finds WHERE code lives AND extracts patterns |
web-researcher | Researches web for docs, APIs, best practices |
Review Workflow
| Agent | Description |
|---|---|
code-reviewer | Project guidelines, bugs, type/module checks |
comment-analyzer | Comment accuracy and maintainability |
pr-test-analyzer | Test coverage quality and gaps |
silent-failure-hunter | Error handling and silent failures |
type-design-analyzer | Type encapsulation and invariants |
code-simplifier | Clarity and maintainability improvements |
docs-impact-agent | Updates stale documentation |
Using Agents
Agents are invoked automatically by /prp-review-agents or manually via Task tool:
/prp-review-agents 123 # Full review of PR #123
/prp-review-agents 123 tests errors # Specific aspects only
Workflow
Large Features: PRD → Plan → Implement
/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
/prp-plan "add pagination to the API"
↓
/prp-implement .claude/PRPs/plans/add-pagination.plan.md
Bug Fixes: Issue Workflow
/prp-issue-investigate 123
↓
/prp-issue-fix 123
Installation
Option 1: From GitHub (Recommended)
# Add marketplace from GitHub
/plugin marketplace add Wirasm/PRPs-agentic-eng
# Install plugin
/plugin install prp-core@prp-marketplace
Option 2: Local Development/Testing
# Navigate to the repository root
cd /path/to/PRPs-agentic-eng
# Start Claude Code
claude
# Add local marketplace (use absolute path)
/plugin marketplace add /absolute/path/to/PRPs-agentic-eng
# Install plugin
/plugin install prp-core@prp-marketplace
# Restart Claude Code (required)
Option 3: Team Automatic Installation
Add to your project’s .claude/settings.json:
{
"extraKnownMarketplaces": {
"prp-marketplace": {
"source": "Wirasm/PRPs-agentic-eng"
}
},
"enabledPlugins": [
"prp-core@prp-marketplace"
]
}
Artifacts Structure
All artifacts are stored in .claude/PRPs/:
.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:
| # | 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 | - |
- Status:
pending→in-progress→complete - Parallel: Phases that can run concurrently
- Depends: Phases that must complete first
PRP Methodology
What is a PRP?
PRP = PRD + curated codebase intelligence + agent/runbook
A PRP is a comprehensive implementation document containing:
- Context - All necessar
…(truncated)
Included Skills
This plugin includes 1 skill definition:
prp-ralph-loop
“Autonomous iteration execution guide for PRP Ralph loops. Use when .claude/prp-ralph.state.md exists, when continuing Ralph iterations, or when executing plans autonomously until all validations pass. Provides iteration behavior, completion protocol, validation requirements, and progress logging.”
View skill definition
PRP Ralph Loop Execution Guide
This skill provides the knowledge needed to correctly execute Ralph loop iterations. Ralph is an autonomous loop system that executes PRP plans iteratively until all tasks are complete and all validations pass.
1. Context Detection
How to Know You’re in a Ralph Loop
Check for the state file: .claude/prp-ralph.state.md
If this file exists, you are in an active Ralph loop. Read it first to understand:
- Current iteration number
- Maximum iterations allowed
- Path to the plan being executed
- Progress from previous iterations
State File Location
.claude/prp-ralph.state.md
2. State File Format
The state file uses YAML frontmatter followed by a progress log:
---
iteration: 3
max_iterations: 10
plan_path: ".claude/PRPs/plans/add-feature.md"
started_at: "2024-01-12T10:00:00Z"
---
# Ralph Progress Log
## Codebase Patterns
[Consolidated learnings that apply across iterations]
## Iteration 1 - 2024-01-12T10:05:00Z
- Implemented X
- Files changed: a.ts, b.ts
- Learnings: Found that Y pattern is used for Z
- Still failing: type-check (3 errors)
## Iteration 2 - 2024-01-12T10:15:00Z
- Fixed type errors
- Added missing imports
- Learnings: Always import types from @/types
- Still failing: tests (1 failure in auth.test.ts)
---
Frontmatter Fields
| Field | Type | Description |
|---|---|---|
iteration | number | Current iteration (1-indexed) |
max_iterations | numbe |
…(truncated)