skills.rest
ForgePlan
ForgePlanOFFICIAL
Explore all skills by this author →
WebsiteGitHub

riper

Orchestrate the RIPER methodology for bug investigations with phase verification.

3|Updated Apr 3, 2026
Search Tags:#methodology#workflow automation#bug investigation#riper#scoped change
One-click install
npx skills add https://github.com/ForgePlan/marketplace --skill riper
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: riper
Source: https://github.com/ForgePlan/marketplace/tree/main/plugins/fpl-skills/skills/riper
Command: npx skills add https://github.com/ForgePlan/marketplace --skill riper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the RIPER methodology, ensuring a structured approach to bug investigations and scoped changes in existing systems.

Core Features & Use Cases

  • RIPER Methodology Execution: Guides through the five phases of Research, Innovate, Plan, Execute, and Review.
  • Phase Tracking: Provides clear progress tracking for each phase.
  • Integration with Existing Skills: Leverages existing fpl-skills for each phase, ensuring a cohesive workflow.
  • Use Case: For a team using the RIPER methodology, this Skill automates the process of conducting a thorough investigation and implementing a fix for a bug in an active system.

Quick Start

Run the /riper command to initiate the RIPER methodology for a bug investigation.

Frequently Asked Questions about riper

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

FAQPage Schema
How do I structure a bug investigation and scoped change in an existing system?▼

Structured bug investigation and scoped change is managed through the RIPER methodology, orchestrating Research, Innovate, Plan, Execute, and Review phases. It enforces independent verification at each step to ensure thorough system modifications.

What is the RIPER methodology for software engineering?▼

The RIPER methodology is a workflow automation process for software engineering consisting of five phases: Research, Innovate, Plan, Execute, and Review. It provides clear phase tracking and mandates independent verification before advancing through scoped changes.

How do I start a RIPER workflow for bug investigation?▼

To start a RIPER workflow for bug investigation, run the /riper command. This initiates the methodology orchestration, leveraging existing fpl-skills to execute each phase and integrating with ForgePlan for artifact management.

Does the RIPER workflow require integration with ForgePlan?▼

The RIPER workflow integrates with ForgePlan for artifact management during scoped changes. It also utilizes existing fpl-skills for phase execution to maintain a cohesive automation workflow throughout the bug investigation process.

When should I use a phased methodology over standard bug fixing?▼

A phased methodology like RIPER should be used for bug investigations in existing systems requiring scoped changes. It is necessary when you need structured phase tracking and mandatory independent verification to prevent regressions during execution.

Related Skills

Explore More Software Engineering Skills→
Synaptic-Labs-AISynaptic-Labs-AI
71

pact-prepare-research

Conduct structured research and documentation gathering for the PACT Prepare phase.

Official
Advanced
cosmixcosmix
53

before-after

Capture and compare system states before and after implementation.

Community
Advanced
ForgePlanForgePlan
3

do

Orchestrate multi-step task workflows with approval checkpoints via ForgePlan.

Official
Advanced
yocxy2yocxy2

gstack-openclaw-investigate

Trace software symptoms to architectural root causes via a five-phase diagnostic workflow.

Community
Advanced