reversa-resume

Swaps the active feature with a paused feature in reversa forward workflow state files.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/RLuf/fzagent --skill reversa-resume-rluf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-resume
Source: https://github.com/RLuf/fzagent/tree/main/.agents/skills/reversa-resume
Command: npx skills add https://github.com/RLuf/fzagent --skill reversa-resume-rluf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working with the reversa framework, developers often pause one feature to start another, then lose track of what was paused or in which stage each feature stopped. This Skill resumes a paused feature by safely swapping it with the currently active one, without losing progress on either side. ## Core Features & Use Cases - Paused feature listing: Reads active-requirements.json, detects the physical stage of each paused feature (requirements, plan, coding-in-progress, done) and shows progress counts like completed actions. - Safe swap with state preservation: Moves the currently active feature into paused-features (or discards it if done or empty) and promotes the chosen paused feature, writing the JSON atomically. - Orphan entry cleanup: Detects paused entries whose folders were manually deleted and offers to remove them from the state file. - Use Case: You paused a login feature at the plan stage to fix an urgent bug. After finishing the fix, run the resume flow to list paused features, pick the login feature, and have the bugfix feature automatically paused with its stage recorded. ## Quick Start Ask the agent to run /reversa-resume to list paused features and resume one of them as the active feature.

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 feature in the reversa workflow?▼

Run /reversa-resume and the skill lists all entries in the paused-features array of active-requirements.json with their detected stage. Pick the number of the feature you want, and it swaps that feature into the active slot while pausing or discarding the current one.

What happens to the currently active feature when I resume another one?▼

The active feature's physical stage is detected from its folder files. If it is in requirements, plan, or coding-in-progress, it is pushed into paused-features with a timestamp; if it is done or empty, it is discarded from the active slot without being paused.

Can I resume a feature if active-requirements.json does not exist?▼

No. The skill aborts with an error because it requires an active feature to perform the swap. You must first create a feature with /reversa-requirements before any resume operation is possible.

What if the paused feature folder was deleted manually?▼

The skill marks that entry as orphaned (ausente) in the listing. If you select it, it offers to remove just that stale entry from paused-features and writes the updated state file atomically without performing any swap.

How does the skill detect which stage a paused feature is in?▼

It inspects the feature directory: missing requirements.md means empty, requirements.md without roadmap.md means requirements, roadmap.md without actions.md means plan, and actions.md checkbox states indicate coding-in-progress or done.