stop

Create a handoff document and pause project work.

Updated Dec 22, 2025

Search Tags:#workflow #project management #handoff #archive #pause

Ready to run

npx skills add https://github.com/royhenengel/Claude-Customizations --skill stop-royhenengel

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: stop
Source: https://github.com/royhenengel/Claude-Customizations/tree/main/skills/Planning/stop
Command: npx skills add https://github.com/royhenengel/Claude-Customizations --skill stop-royhenengel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured way to archive a completed workflow and cleanly pause ongoing work, ensuring all necessary documentation and state are preserved.

Core Features & Use Cases

Handoff Document Creation: Generates a document summarizing the current state and any necessary information for a smooth transition.
Work Pausing: Ensures that work is stopped in a controlled manner, preventing data loss or confusion.
Use Case: When a development sprint is ending or a project phase is complete, use this skill to create a final report and formally pause further development until the next phase begins.

Quick Start

Use the stop skill to create a handoff document and pause the current project.

Frequently Asked Questions about stop

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

FAQPage Schema

How do I archive a workflow and cleanly pause project development?▼

To archive a workflow and pause project development, you can generate a handoff document that summarizes the current state. This allows you to formally stop work in a controlled manner for team transitions or phase completion.

What is the best way to create a handoff document for a project transition?▼

Creating a handoff document for a project transition involves summarizing the current state and necessary information for a smooth handoff. This structured approach ensures all documentation is preserved when work is paused.

How do I pause ongoing work without losing project state or causing team confusion?▼

You can pause ongoing work without losing project state by creating a final report that captures the development sprint status. This controlled cessation prevents data loss and confusion during team transitions.

When should I formally archive a completed workflow instead of just stopping work?▼

You should formally archive a completed workflow when a development sprint is ending or a project phase is complete. This ensures a structured work cessation and generates a final report before pausing further development.

Do I need to manually review state files when pausing a project for archival?▼

Yes, you need to manually review the STATE.md file when pausing a project for archival. This manual review is required to ensure automatic state maintenance is correctly preserved during the build process.

Can I use this approach to manage work cessation for a completed development sprint?▼

Yes, you can use this approach to manage work cessation for a completed development sprint. It facilitates project archival by creating a handoff document and cleanly pausing further development until the next phase begins.