prp-issue-contract

Creates and audits GitHub issues against a readiness contract before agent automation starts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams running agentic workflows often hand AI agents vague, stale, or blocked GitHub issues, causing wasted automation runs and misdirected work. This Skill enforces a minimum issue contract and a precondition check so only well-formed, ready work reaches planning-capable agents.

Core Features & Use Cases

  • Issue Creation: Turns conversations, findings, or ideas into GitHub issues that follow the repository's own issue templates and contribution rules.
  • Readiness Audit: Evaluates an existing issue against four contract elements (problem, why, outcome, acceptance) and returns a verdict of READY, NEEDS_CONTRACT_WORK, BLOCKED, or NO_ACTION.
  • Precondition Checking: Inspects code and architecture to detect missing prerequisites or unlogged blockers before automation begins.
  • Use Case: Before triggering an autonomous coding agent on issue #42, run an audit to confirm the issue still reflects current direction, has clear acceptance criteria, and has no hidden prerequisite work.

Quick Start

Ask the agent to check whether issue #42 is agent-ready and audit its contract before starting automation.

Frequently Asked Questions about prp-issue-contract

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

FAQPage Schema
How do I check if a GitHub issue is ready for an AI agent?

Run an audit on the issue to verify it communicates the problem, why, desired outcome, and acceptance criteria. The Skill returns a verdict of READY, NEEDS_CONTRACT_WORK, BLOCKED, or NO_ACTION based on contract completeness and delivery preconditions.

How do I turn a conversation into a GitHub issue?

Provide the conversation or idea as input and request issue creation. The Skill infers the contract elements, applies the repository's issue template, checks for duplicates, and creates the issue using existing labels only.

Does this Skill design the implementation for an issue?

No. It deliberately stops before root cause analysis, solution design, and implementation planning. Those tasks belong to downstream planning workflows; this Skill only ensures the product intent and preconditions are sound.

What happens when an issue has a missing prerequisite?

The Skill inspects the relevant code to find unlogged prerequisites, then decides whether the work belongs inside the issue or as a separate blocking issue. It proposes a new prerequisite issue but only creates it when explicitly asked.

When should an issue be closed instead of automated?

An issue receives a NO_ACTION verdict when the work is already delivered, duplicated, obsolete, or explicitly out of current direction. In update mode the Skill applies a closing comment and existing labels, then closes the issue.