Wirasm/prp

---

name: prp-bro

description: Restates the previous response in plain language, with no jargon. Use when the user says "bro", asks to "say that plainly", says "explain it simply", or invokes /prp-bro.

---

name: prp-codebase-question

description: Research codebase questions using parallel agents - documents what exists, not what should change. Use when the user asks how the codebase works, where something lives, or invokes /prp-codebase-question.

---

name: prp-commit

description: Creates Git commits for completed work. Always use when committing changes, when the user explicitly asks to commit the work, when another PRP workflow reaches its commit step, or when the user invokes /prp-commit.

---

name: prp-companion

---

name: prp-debug

description: Diagnoses a bug, error, stack trace, regression, or unexplained behavior and publishes the evidence-backed root cause to GitHub. Use when the user says "debug this", "find the root cause", provides a bug report or stack trace, asks to investigate a GitHub issue, or invokes /prp-debug. Defaults to commenting on the matching open issue or creating one when none exists.

---

name: prp-deliver

description: This is an experimental skill. Never use it unless the user explicitly tells you to invoke /prp-deliver.

---

name: prp-implement

description: Implements and validates existing PRP plans and corrects reviewed or failing-CI pull requests. Always use when executing an implementation plan, implementing an issue that already has a local or published plan, correcting a PR from a PRP review report or CI failure, when another PRP workflow reaches its implementation or correction step, or when the user invokes /prp-implement.

---

name: prp-issue

description: Autonomously owns one workstream from an issue, PRD, document, existing plan, or free-form request through planning, implementation, pull request, independent review, corrections, and green CI. Always use when the user asks to implement or ship work end to end, take an issue or idea to a reviewed PR, run plan to PR, invokes /prp-issue, or when prp-orchestrate needs an end-to-end delivery engine.

---

name: prp-issue-contract

description: Creates GitHub issues from conversations, findings, or ideas and runs the precondition check before a planning-capable agent starts work. Use when the user asks to "create an issue from this", "turn this into an issue", "check whether issue #42 is agent-ready", "check this issue before automation", "audit this issue contract", "update this issue to make it agent-ready", or invokes /prp-issue-contract.

---

name: prp-loop

description: Runs the detached, resumable PRP pipeline in fresh headless CLI sessions, cycling plan, implementation, PR, review, and corrections with persisted state and safety bounds. Use only when the user explicitly asks to "run the full PRP loop", "run this detached", "continue across context windows", use headless autonomous execution, resume a saved loop, or invokes /prp-loop. Use prp-issue for ordinary end-to-end delivery.

---

name: prp-maintainer-triage

description: Quickly triages a contributor pull request or reported issue against repository policy and lightweight evidence without full review or root-cause analysis. Publishes the disposition to GitHub, and on a contributor pull request that links no issue it may open a tracking issue and close the pull request. Use when the user asks to "triage this contributor PR", "sanity-check this PR", "triage this issue", "reproduce this reported issue", "check whether this bug still exists", or invokes /prp-maintainer-triage.

---

name: prp-meta-skill

description: Authors, refactors, and consolidates Agent Skills PRP-style. Use when the user wants to "create a skill", "write a new skill", "trim a SKILL.md", "split a skill into references", "consolidate workflow skills", "replace duplicated skill logic with composition", redesign a skill workflow, or invokes /prp-meta-skill.

---

name: prp-orchestrate

description: Turns the current session into the operator's SDLC proxy for parallel PRP workstreams in isolated worktrees. It owns the combined outcome, steers autonomous deliveries, holds human and merge gates, verifies proof, and sequences merges. Use when the user wants to "spawn N agents in separate worktrees", "run prp-issue on these issues in parallel", "orchestrate these features", "act as my orchestrator", "coordinate agents through the PRP pipeline", "ship these issues in parallel", or invokes /prp-orchestrate.

---

name: prp-plan

description: Creates an implementation-ready plan for a feature, bug fix, refactor, or chore from a PRD, issue, document, or description using codebase evidence, first-principles reasoning, and conditional root-cause analysis, research, or spikes. Publishes issue-derived plans back to their source issue. Use when the user asks to "plan this feature", "plan this bug fix", "plan issue X", "create an implementation plan", "turn this PRD into a plan", investigate how a change should be built, link related plans, or invokes /prp-plan.

---

name: prp-pr

description: Creates and opens GitHub pull requests. Always use when creating a PR on GitHub, when the user explicitly asks to create or open a PR, when another PRP workflow reaches its PR-creation step, or when the user invokes /prp-pr.

---

name: prp-prd

description: Interactive PRD generator - problem-first, hypothesis-driven product spec. Use when the user wants to create a PRD, write a product or feature spec, scope a new product, or invokes /prp-prd.

---

name: prp-prd-update

description: Maintains PRD implementation-phase status and artifact links. Always use when a PRP workflow records a planned, implemented, or merged phase in its source PRD, when the user asks to update PRD progress, or when the user invokes /prp-prd-update.

---

name: prp-research-team

description: Design a dynamic research team and plan using agent teams -- analyzes question, composes team, creates executable research plan. Use when the user wants to plan multi-agent research on a question or topic, or invokes /prp-research-team.

---

name: prp-review

description: Reviews GitHub pull requests through specialist review agents, runs repository validation, verifies corrections, aggregates findings, and posts the result. Scales reviewers to risk by default (code review alone for small or mechanical changes; code, seam, and simplification review for contracts, state, and security); the operator can add scopes or explicitly request only selected scopes. Use when the operator asks to review a PR, re-review fixes, check whether a PR is ready to merge, run review agents, or invokes /prp-review.

---

name: prp-spike

description: Prove or disprove an idea by building the smallest throwaway artifact that could falsify it, in an isolated worktree, ending in a PROVEN / DISPROVEN / CONDITIONAL verdict backed by evidence - never a PR. Use when the user wants to "spike this", "build a proof of concept", "POC this", "prototype it to find out", asks "is this possible", "is this feasible", "does this fit our stack", or "would it be worth changing X to allow Y" and wants it settled by building rather than by analysis, wants to compare approaches on evidence before picking one, or invokes /prp-spike.

---

name: prp-technical-writing

description: Writes and edits developer documentation that is easy to act on and hard to misread. Use when writing or reviewing a README, RFC, tutorial, how-to guide, reference document, or technical explanation, when the operator says "write the docs", "improve this README", "edit this RFC", or invokes /prp-technical-writing.

---

name: prp-worklist

description: Render the open work of a repository as something worth looking at, so the maintainer can see what to take next. Deliberate invocation only — /prp-worklist.