park

Park active specs by updating spec.md with status and clarification notes.

1|Updated May 28, 2026

Search Tags:#workflow #governance #resume #spec #pause #blocker #park

Ready to run

npx skills add https://github.com/amoutiers/maxi-superpowers --skill park-amoutiers

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: park
Source: https://github.com/amoutiers/maxi-superpowers/tree/main/skills/park
Command: npx skills add https://github.com/amoutiers/maxi-superpowers --skill park-amoutiers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Freeze a spec in place to pause work without losing progress, enabling safe handling of blockers.

Core Features & Use Cases

Freeze an active spec to prevent edits while a blocker is resolved.
Require a non-empty reason and explicit confirmation before writing changes.
Resume later with /maxi:resume to continue from the parked state.

Quick Start

Use maxi:park to freeze the currently active spec when you encounter a blocker and provide a reason.

Frequently Asked Questions about park

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

FAQPage Schema

How do I safely pause a spec workflow when a feature is blocked?▼

To pause a spec workflow safely, you park the active spec to freeze it in place, preventing edits while a blocker is resolved. This requires a non-empty reason and explicit confirmation before applying changes.

What happens to the spec.md file when I park an active spec?▼

When you park an active spec, the spec.md file is updated with status: parked, parked_from: <current_status>, and updated: <today's ISO date>. A parked note is also appended to the Clarifications section.

Can I park multiple specs at the same time during governance blockers?▼

Yes, you can apply the park action across one or more specs simultaneously. Each spec requires a non-empty reason and explicit confirmation to ensure governance blockers are documented before pausing work.

How do I resume work on a parked spec after the blocker is resolved?▼

To resume work on a parked spec after the blocker is resolved, use the resume command. This action unfreezes the spec, allowing you to continue from the exact parked state without losing prior progress.

Why does pausing a spec require a non-empty reason and explicit confirmation?▼

Pausing a spec requires a non-empty reason and explicit confirmation to prevent accidental freezes and ensure work governance. This ensures every paused spec documents exactly why progress was halted before changes are written.