reversa-resume

Swap a paused feature into active status and restore workflow progress.

1|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-resume-rdinda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-resume
Source: https://github.com/Rdinda/FMA_Pontos/tree/main/.agents/skills/reversa-resume
Command: npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-resume-rdinda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reativa uma feature pausada de um projeto sem causar perda do trabalho já feito, permitindo que você continue exatamente de onde parou.

Core Features & Use Cases

  • Retomar a feature correta: lista todas as entries em paused-features e pede que o usuário escolha a desejada.
  • Preservar contexto do progresso: detecta o estágio físico da feature (requirements, plan, coding-em-progresso, done) para orientar a troca e o relatório final.
  • Tratar entradas órfãs com segurança: se a pasta da feature foi apagada, impede o swap e oferece a opção de remover apenas essa entry.
  • Fallback para schemas antigos: quando faltam campos como started-at e current-stage, usa o estágio físico detectado e registra a decisão ao usuário.

Quick Start

Digite /reversa-resume e selecione o número da feature pausada que você quer retomar.

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 a workflow without losing progress?

To resume a paused feature without losing progress, the skill swaps the currently active feature with a selected paused feature by validating physical stages in requirements.md and performing an atomic write to active-requirements.json.

How do I restore a paused workflow state from a JSON file?

Restoring a paused workflow state from JSON requires reading .reversa/state.json, validating paused-features entries against roadmap.md, and updating paused-at and paused-from-stage fields to resume the workflow.

What happens to orphaned paused feature entries when resuming a workflow?

When resuming a workflow, orphaned paused feature entries are handled safely by preventing the swap if the physical folder was deleted, offering the option to remove only that specific entry instead.

Can I resume a paused feature if the active-requirements JSON schema is missing fields?

You can resume a paused feature even if the active-requirements JSON schema lacks fields like started-at and current-stage, as the system falls back to the physically detected stage and logs the decision.

Does feature management workflow resumption require atomic updates?

Feature management workflow resumption requires atomic updates to active-requirements.json to ensure the currently active feature is swapped safely without corrupting the paused-features list or losing progress.

What are the limitations of resuming a paused feature if the project folder was deleted?

Resuming a paused feature is blocked if the project folder was deleted, because the skill cannot validate the physical stage from requirements.md and will only offer to remove the orphaned paused entry.