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, run plan to PR, invokes /prp-issue, or when prp-orchestrate needs an end-to-end delivery engine.

Quality

98%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, highly actionable workflow skill: directive prose, named command invocations and modes, explicit validation gates, and clear correction/re-review feedback loops, all in a well-organized self-contained body. No padding and no missing checkpoints for the destructive/batch shipping operation it governs.

Dimension	Reasoning	Score
Conciseness	The body is dense and procedural with zero concept-over-explanation (no "what a PR/CI is" padding); every sentence is directive and assumes Claude's competence, so every token earns its place.	5 / 5
Actionability	Concrete and executable throughout: it names exact slash commands and modes (/prp-plan, /prp-implement review-correction/CI-correction mode, /prp-review --verify-corrections), specifies required artifacts, and provides a copy-paste-ready fresh-agent prompt in section 3.	5 / 5
Workflow Clarity	A clearly sequenced six-phase process with explicit validation checkpoints ("VALIDATION: GREEN", "complete canonical review report", "A pending check is not green", "Only after review and CI are green") and well-defined correction/re-review feedback loops for a batch shipping operation.	5 / 5
Progressive Disclosure	A self-contained, well-sectioned overview with no bundle files and no nested file references; the only references are sibling slash commands (one level deep), so structure is clean and easy to navigate.	5 / 5
	Total	20 / 20 Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description: third-person voice, concrete capability list, an explicit "Always use when" trigger clause, and a clear delivery niche. The only minor risk is overlap with the sibling prp-* skills it composes.

Suggestions

To reduce overlap with /prp-plan, /prp-implement, and /prp-review, add a one-clause boundary (e.g. "use /prp-plan directly for planning-only requests") so the orchestrator is not triggered for sub-tasks.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("planning, implementation, pull request, independent review, corrections, and green CI") and concrete input sources (issue, PRD, document, plan, request), giving comprehensive coverage rather than vague abstraction.	5 / 5
Completeness	It explicitly answers both what ("Autonomously owns one workstream... through planning, implementation, pull request, independent review, corrections, and green CI") and when ("Always use when...") with concrete trigger phrases, matching the score-5 anchor.	5 / 5
Trigger Term Quality	The explicit "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" clause covers natural phrases a user would say plus the literal invocation trigger, with good synonym coverage.	5 / 5
Distinctiveness Conflict Risk	It carves a clear end-to-end delivery niche and names /prp-issue and prp-orchestrate, but it composes sibling skills (/prp-plan, /prp-implement, /prp-review) that could overlap on related requests, so minor overlap risk remains.	4 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Wirasm/prp
Path: .claude/skills/prp-issue/SKILL.md
Commit: 9724799

Reviewed: ~13 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.