reversa-resume

Swap the active entry in active-requirements.json with a selected paused-features entry.

1.5k|383|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/sandeco/reversa --skill reversa-resume-sandeco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-resume
Source: https://github.com/sandeco/reversa/tree/main/agents/reversa-resume
Command: npx skills add https://github.com/sandeco/reversa --skill reversa-resume-sandeco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of getting an AI agent workflow back on track when a legacy specification feature was paused mid-progress and the user needs to resume the exact saved work safely.

Core Features & Use Cases

  • Resume paused features: Lists all entries in paused-features, detects whether each corresponding feature directory exists, and shows its physical stage before proceeding.
  • Safe swap of active feature: Replaces the currently active feature in active-requirements.json with the user-selected paused feature, preserving the paused feature work.
  • Robust state handling: Detects the current physical stage (vazio, requirements, plan, coding-em-progresso, done) and either pauses, discards, or prompts for cleanup when an entry is orphaned.
  • Use Case: If your system has a feature in coding-em-progresso (actions marked as completed/in-progress), use this skill to resume that exact feature after you switch contexts, without creating a new one.

Quick Start

Run /reversa-resume and type the number of the paused feature you want to retomar when you are prompted.

Frequently Asked Questions about reversa-resume

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

FAQPage Schema
How do I resume a paused AI agent workflow without losing my feature coding progress?

To resume a paused AI agent workflow without losing progress, you swap the current active entry in active-requirements.json with a user-selected paused-features entry, safely restoring the exact saved work.

What happens to orphaned paused features when resuming a legacy specification workflow?

When resuming a legacy specification workflow, the system detects orphaned paused entries by validating physical stages and prompts for cleanup or removal after user confirmation to maintain state integrity.

Can I detect the physical stage of a paused feature before switching active requirements?

Yes, you can detect the physical stage of a paused feature before switching active requirements by reading .reversa/state.json for folder routing and checking each feature directory for requirements, plan, or coding-em-progresso stages.

How do I perform an atomic update to active-requirements.json when swapping legacy features?

Performing an atomic update to active-requirements.json when swapping legacy features involves validating the paused-features entry and replacing the currently active feature data in a single transaction to prevent workflow corruption.

Do I need a state.json file to route folder paths for paused feature resumption?

Yes, you need to read .reversa/state.json for folder routing to validate paused-features and detect physical stages from each feature directory before performing the resume swap operation.