rsop

Organize software state and incidents into a problem-oriented registry with SOAP documentation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/iago-leal/skills --skill rsop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rsop
Source: https://github.com/iago-leal/skills/tree/main/mdcu-framework/rsop
Command: npx skills add https://github.com/iago-leal/skills --skill rsop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

RSOP provides a concise, problem-oriented registry for software projects, capturing system state, incidents, active problems, and long-term SOAP records to support traceability and informed decisions.

Core Features & Use Cases

  • Data base (Dados base) profile of a project including responsible parties, stack, and repository details.
  • Active problems list that feeds in CLAUDE prompts and persists per project SOAP.
  • SOAP per MDCU session to track demand, observations, assessments, and plans.
  • Passivos file for closed issues to avoid clutter in context, with reactivation rules.
  • Suitable for ongoing projects needing structured longitudinal documentation, incident logging, and risk tracking.

Quick Start

Activate RSOP with /rsop to initialize data, start a SOAP, and begin populating the active problem list.

Frequently Asked Questions about rsop

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

FAQPage Schema
How do I maintain a longitudinal record for software incidents and active problems?

You maintain a longitudinal record by organizing system state and incidents into a problem-oriented registry that tracks active issues and formal SOAP documentation per session. This ensures long-term traceability and supports informed decisions.

What is SOAP documentation for issue tracking in software engineering?

SOAP documentation for issue tracking is a structured format capturing demand, observations, assessments, and plans per session. It provides a standardized longitudinal record to trace problems and support decision-making in ongoing projects.

How do I start tracking active problems and logging incidents for a project?

You start tracking active problems and logging incidents by initializing a problem-centered registry with your project's base profile, responsible parties, and stack details. This populates an active problem list and begins your session-based SOAP records.

Does structured issue tracking work for managing closed issues without cluttering context?

Structured issue tracking manages closed issues without cluttering context by moving resolved items to a passivos repository. This repository applies reactivation rules to cleanly separate historical data from active problems.

When do I need formal SOAP documentation for risk management?

You need formal SOAP documentation for risk management when running ongoing projects that require structured longitudinal tracing, incident logging, and clear assessment records to support long-term traceability and informed decisions.

What is the best way to structure a software registry for ongoing projects?

The best way to structure a software registry for ongoing projects is to use a problem-oriented approach that captures base data, active problems, session SOAPs, and a passivos repository for closed items with reactivation rules.