rpi

The rpi skill is an orchestrator for implementing features from Jira tickets, PRDs, and user requirements using a structured Research-Plan-Implement workflow. Its purpose is to guide feature work through a defined sequence of stages so implementation is grounded in source requirements rather than guesswork. It addresses common delivery risks by introducing explicit quality gates that check for hallucination, overengineering, and underengineering before work proceeds to the next stage.

Its main capabilities include coordinating multiple individual skills in sequence, creating a session for tracking work, generating research and planning artifacts, auditing those artifacts against defined thresholds, and moving approved work into implementation and code review. The documented workflow includes research output, audit gates for confidence, hallucination, traceability, and balance, a user approval step before implementation, and a final review stage that reports findings using P0, P1, and P2 severity levels. It also includes compatibility guidance for different environments, including output directory conventions, differences between Claude Code and Codex CLI invocation patterns, and alternatives for task tracking tools.

This skill is suited for developers and technical teams who need a disciplined workflow for turning requirements into code changes. It is especially relevant when the input is a Jira issue key, a Confluence PRD URL, or a direct feature request such as "implement" or "build." Target users include engineers working in Claude Code or Codex CLI environments who want a repeatable process with checkpoints, documented intermediate outputs, and an explicit approval gate before implementation begins.