reversa-resume

To resume a paused feature, invoke the resume command with the feature's short-name. The Skill reads active-requirements.json, validates the paused feature's state, atomically swaps it into the active slot, and moves the current active feature to paused-features.

When you reactivate a paused feature, the Skill automatically moves the currently active feature into the paused-features list within active-requirements.json. This ensures a safe swap without creating new features or losing track of previous work.

The workflow validates the chosen paused feature by checking for the existence of its folder and detecting its physical stage, such as empty, requirements, plan, coding-em-progress, or done, before performing the atomic state update.

Yes, this Skill specifically reactivates previously paused features without creating new entries. It performs a deterministic swap by reading state files, validating the target feature, and writing an atomic update to active-requirements.json.

The active-requirements.json file stores the current active feature and the paused-features list. The Skill reads this file to identify the target paused feature and atomically writes the updated state back to it after swapping features.

Yes, after atomically writing the updated active-requirements.json and completing the feature swap, the Skill triggers standard after-resume hooks to execute downstream workflow actions.