prp-core

Plugin prp-core from marketplace prp-marketplace in Wirasm/prp. Commands read from the repo's manifest — 1 month ago.

Skills (22)

• prp-bro

  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.

• prp-codebase-question

  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.

• prp-commit

  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.

• prp-companion

  Writes the visual HTML companion of a PRP plan or review - one self-contained page beside the markdown that shows a plan's change diagram, steps and risks, or a review's verdict, findings and a diagram of what the PR changed, with every item carrying a stable id a mark can point at. In helm a review

• prp-debug

  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 co

• prp-deliver

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

• prp-implement

  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

• prp-issue-contract

  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",

• prp-issue

  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

• prp-loop

  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 h

• prp-maintainer-triage

  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 reque

• prp-meta-skill

  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-orchestrate

  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

• prp-plan

  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 whe

• prp-pr

  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.

• prp-prd-update

  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.

• prp-prd

  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.

• prp-research-team

  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.

• prp-review

  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, sta

• prp-spike

  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 t

• prp-technical-writing

  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-tec

• prp-worklist

  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.

Subagents (11)

• code-reviewer

  General-purpose code reviewer that checks whether a change is correct, sane, appropriately scoped, and consistent with its repository. Use after implementation, before commits, or during PR review. Follows the diff into surrounding code only as needed to understand concrete effects and reports usefu

• code-simplifier

  Reviews changed code for overengineering and premature structural decisions. Use after implementation or during PR review to find unnecessary code, weak data shapes, duplicated ownership, threaded signals, shared mutable state, scattered special cases, and machinery that an existing or smaller primi

• codebase-analyst

  Traces how a specific behavior works through control flow, data flow, state ownership, boundaries, and side effects with precise file:line evidence.

• codebase-explorer

  Locates where a concern lives and returns the concrete files, precedents, primitives, tests, and validation commands that describe the codebase as it exists.

• comment-analyzer

  Finds changed comments and docstrings that misstate behavior, preserve a false invariant, or create a concrete maintenance trap. Use when a PR adds or edits comments, API documentation, TODOs, examples, or operational notes. Verifies every finding against code and direct consumers; ignores harmless

• docs-impact-agent

  Finds repository documentation made false by a change and missing documentation required to use or operate a new public behavior. Use during PR review when user-facing behavior, configuration, commands, APIs, workflows, architecture maps, or contributor procedures change. Checks the documentation su

• pr-test-analyzer

  Finds meaningful changed behavior that lacks regression protection. Use when reviewing a PR or completed implementation for test completeness and quality. Maps outcomes and invariants to existing unit, integration, and end-to-end tests, then reports only gaps with a plausible faulty implementation t

• root-cause-analyzer

  Diagnoses bugs, errors, stack traces, regressions, and unexplained behavior by reproducing the symptom, testing competing hypotheses, and proving the smallest causal chain and fix boundary. Advisory only — does not modify files, commit, or publish findings.

• seam-analyzer

  Hunts for a missing type at a seam — structure flattened and rebuilt downstream, hand-maintained lists held together by KEEP IN SYNC comments, a phase that exists in the code but not in the type, a second route that skips the validator, an invariant carried by a comment or by a helper with a reachab

• silent-failure-hunter

  Finds changed failure paths that become indistinguishable from success or lose the evidence needed by the owner who can act. Use when a change adds catches, fallbacks, retries, optional operations, error translation, default values, or recovery behavior. Requires a reachable failure, a suppression p

• web-researcher

  Researches current external facts, APIs, platform behavior, and technical claims from primary sources, returning cited evidence, applicability, conflicts, and unresolved gaps.

Hooks (1)

• Stop

  ${CLAUDE_PLUGIN_ROOT}/hooks/prp-research-team-stop.sh