resume

Resume a parked spec to its previous active status in the Maxi workflow.

1|Updated May 28, 2026
One-click install
npx skills add https://github.com/amoutiers/maxi-superpowers --skill resume-amoutiers
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resume
Source: https://github.com/amoutiers/maxi-superpowers/tree/main/skills/resume
Command: npx skills add https://github.com/amoutiers/maxi-superpowers --skill resume-amoutiers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resuming a parked spec to its previous active status ensures work continuity without losing context or historical state, preventing stalled work and manual re-entry.

Core Features & Use Cases

  • Detects specs with status: parked and presents a safe way to restore them to their prior phase.
  • Restores the correct state by reading parked_from from the spec and clearing parked_from after resume.
  • Maintains audit trail by updating the timestamp and appending a note under ## Clarifications for traceability.

Quick Start

Instruct Maxi to resume a parked spec and confirm the restoration target to continue the workflow.

Frequently Asked Questions about resume

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

FAQPage Schema
How do I resume a parked spec to its previous workflow status?

To resume a parked spec, instruct the workflow to restore it, select the target from multiple parked specs, and it reverts to its prior active status by reading the parked_from flag.

What happens to the audit trail when I restore a parked spec pipeline?

Restoring a parked spec updates the timestamp and appends a Resumed note under Clarifications, ensuring the audit trail maintains traceability without losing historical context.

How do I disambiguate between multiple parked specs in the workflow?

When multiple parked specs exist, the system requires user selection to disambiguate, prompting you to confirm exactly which spec to restore before clearing the parked_from flag.

Does resuming a parked spec clear the prior workflow state?

No, resuming a parked spec reads the parked_from value to restore the correct state, then clears the parked_from flag and directs the next skill based on that restored status.

Why does my parked spec require confirmation before restoring its pipeline status?

Confirmation is required to disambiguate the target when multiple parked specs exist, preventing accidental restoration of the wrong spec and ensuring work continuity across the workflow.