reversa-resume

Swap the active feature with a paused feature in active-requirements.json.

Updated Nov 4, 2025
One-click install
npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-resume-markson22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-resume
Source: https://github.com/Markson22/MKV-SYTEM/tree/main/.agents/skills/reversa-resume
Command: npx skills add https://github.com/Markson22/MKV-SYTEM --skill reversa-resume-markson22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retoma uma feature pausada (listada em paused-features de active-requirements.json) e a torna ativa. Use quando o usuário digitar "/reversa-resume", "reversa-resume", "retomar feature pausada" ou pedir para voltar a uma feature anterior. NÃO cria features novas, apenas troca a ativa pela escolhida e (quando faz sentido) move a ativa atual para paused-features.

Core Features & Use Cases

  • Troca a feature ativa com uma pausada para retomar o trabalho sem criar novas features.
  • Mantém o histórico e o estado de que a feature foi pausada, além de atualizar paused-features e active-requirements.json de forma atômica.
  • Usa a detecção de estágio físico (requirements, plan, coding-em-progresso, done) para determinar o destino adequado e a visibilidade de cada feature.

Quick Start

Digite '/reversa-resume' para iniciar a retomada de uma feature pausada.

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 my software development workflow?

To resume a paused feature, the workflow swaps the currently active feature with a paused one from paused-features, updating active-requirements.json atomically to reflect the new active state without creating new items.

What happens to my current active feature when I retomar feature pausada?

When resuming a paused feature, the currently active feature is moved to paused-features when it makes sense to do so, ensuring no work is lost and the state is updated atomically across both JSON files.

Does the feature management workflow support stage detection for paused features?

Yes, the workflow enforces physical stage detection including vazio, requirements, plan, coding-em-progresso, and done to determine the appropriate destination and visibility for each swapped feature.

Can I use atomic updates to swap active requirements without creating new feature items?

Yes, atomic updates write consistent JSON changes to both active-requirements.json and paused-features simultaneously, validating inputs to swap features securely without generating duplicate or new items.

What are the limitations when resuming a paused feature through active-requirements.json?

This process does not create new features; it only swaps the active feature with an existing paused feature. It relies on validating inputs and reading existing paused-features entries to ensure consistent state updates.