prp-issue

Delivers a workstream from issue or PRD through planning, implementation, PR, review, and green CI.

2.2k|608|Updated Jun 21, 2025
One-click install
npx skills add https://github.com/Wirasm/PRPs-agentic-eng --skill prp-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prp-issue
Source: https://github.com/Wirasm/PRPs-agentic-eng/tree/main/plugins/prp-core/skills/prp-issue
Command: npx skills add https://github.com/Wirasm/PRPs-agentic-eng --skill prp-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shipping a feature end to end requires juggling planning, implementation, pull requests, independent review, corrections, and CI checks, and context or reasoning is often lost between these stages. This Skill owns one workstream autonomously across that entire lifecycle so nothing falls through the cracks.

Core Features & Use Cases

  • End-to-End Workstream Ownership: Accepts an issue, PRD, document, existing plan, or free-form request and drives it through planning, implementation, PR creation, review, and CI.
  • Independent Review Loop: Runs code review in a fresh context, dispositions every finding (fix, not-a-finding, follow-up, or declined), and re-verifies corrections until the verdict is READY TO MERGE.
  • CI Gate Enforcement: Waits for all required CI checks to pass and invokes correction cycles for PR-caused failures before returning proof of completion.
  • Use Case: Point it at a GitHub issue describing a new feature; it plans the work, implements it, opens a PR, gets it independently reviewed, fixes the findings, and returns only when review and CI are green.

Quick Start

Ask the agent to take this GitHub issue and ship it end to end as a reviewed pull request with green CI.

Frequently Asked Questions about prp-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I take a GitHub issue to a merged-ready pull request automatically?

Invoke the skill with the issue URL or number. It plans the work, implements it, opens a PR, runs an independent review in a fresh context, fixes valid findings, and waits for green CI before returning the PR URL and proof artifacts.

How does automated PR review and correction work in this workflow?

Review runs in a fresh agent context for independence and publishes a canonical report to GitHub. The implementation context then dispositions every finding, batches accepted corrections into one pass, and re-verifies with a focused review until the verdict is READY TO MERGE.

Can I use an existing plan or PRD instead of a GitHub issue?

Yes. The skill accepts an issue or tracker URL, a PRD, a document, an existing .plan.md file, a free-form request, or an already-reviewed PR, and resumes from the appropriate stage without repeating completed work.

Does the skill merge the pull request after review passes?

No. The skill explicitly does not merge; the caller or an outer orchestrator owns the merge gate. It stops after review is READY TO MERGE and all required CI checks are green.

When does the skill stop instead of completing the workstream?

It stops only for a product decision, a missing prerequisite primitive, an inaccessible dependency, a permission boundary, or a repeated no-progress failure that cannot be resolved within the current context.