structured-rpi

Included with Lifetime

$97 forever

Enhanced Research-Plan-Implement workflow with structured phase gates. Use when tackling complex tasks that benefit from a phased approach with user checkpoints.

General

What this skill does


# Structured RPI (Research-Plan-Implement)

A 6-phase workflow that decomposes complex tasks into gated stages, each producing a markdown artifact the user approves before advancing.

## Quick Start

```text
Use structured RPI to refactor the authentication module.
```

The workflow walks through six phases sequentially. Each phase produces a concise markdown artifact. You must get user approval before moving to the next phase.

## Phases

| #   | Phase              | Artifact                    | Purpose                              |
| --- | ------------------ | --------------------------- | ------------------------------------ |
| 1   | **Questions**      | Clarifying questions list   | Surface unknowns and ambiguity       |
| 2   | **Research**       | Findings summary            | Gather context from code and docs    |
| 3   | **Design Discussion** | Design options + tradeoffs | Explore approaches with the user     |
| 4   | **Structure Outline** | Component/file outline     | Agree on shape before details        |
| 5   | **Plan**           | Implementation plan (Plan tool) | Concrete steps with acceptance criteria |
| 6   | **Implement**      | Working code + verification | Execute the plan                     |

## How It Works

1. **Announce the phase** — State which phase you're entering and what it produces
2. **Do the work** — Research, analyze, design, or implement as appropriate
3. **Present the artifact** — Output a markdown artifact with a clear heading
4. **Gate** — Ask the user to approve, request changes, or skip ahead
5. **Advance** — Only move to the next phase after explicit user approval

### Phase Gate Format

After each artifact, present:

```text
Phase N complete. Ready to proceed to Phase N+1 (Name)?
Options: [approve] [request changes] [skip to phase N+X] [abort]
```

## Key Rules

- **Always gate** — Never advance without user approval
- **Phase 5 uses the Plan tool** — Create a structured plan, not just prose
- **Artifacts are markdown** — Clean, scannable, no JSON blobs
- **Keep artifacts concise** — Prefer bullet points and tables over walls of text
- **Self-contained** — This workflow runs in a single session, no delegation

## When to Use

| Situation | Use Structured RPI? |
| --- | --- |
| Complex refactor spanning multiple files | Yes |
| New feature with unclear requirements | Yes |
| Bug fix with known cause | No — just fix it |
| One-file change | No — overkill |
| User says "plan this out" or "let's think through this" | Yes |

## When to Skip Phases

- **User already provided requirements** — Skip Phase 1 (Questions)
- **Small scope, well-understood** — Skip Phase 2 (Research)
- **Single obvious approach** — Compress Phase 3 (Design) into Phase 4 (Outline)
- **User says "just do it"** — Jump to Phase 6 with a lightweight plan

## References

- [phase-details.md](references/phase-details.md) - Detailed phase descriptions, inputs/outputs, done criteria
- [structured-outputs.md](references/structured-outputs.md) - Artifact templates for each phase
- [exit-conditions.md](references/exit-conditions.md) - When to skip, go back, or exit the workflow

Files: 4

Size: 11.8 KB

Complexity: 27/100

Category: General

Source: https://github.com/spences10/claude-code-toolkit/tree/main/plugins/claude-workflow/skills/structured-rpi

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts