abort-playbook

Abort a playbook workflow and archive it with aborted status.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/M2AI-jp/thanks4claudecode-fresh --skill abort-playbook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: abort-playbook
Source: https://github.com/M2AI-jp/thanks4claudecode-fresh/tree/main/.claude/skills/abort-playbook
Command: npx skills add https://github.com/M2AI-jp/thanks4claudecode-fresh --skill abort-playbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides a controlled abort flow that moves the playbook to an aborted state, updates state.md, and guides branch handling without archiving.

Core Features & Use Cases

  • Abort flow: Transition to aborted status and move file to plan/archive with metadata.
  • State synchronization: Reset playbook.active and branch to null in state.md.
  • Branch guidance: Guide users on cleaning up or keeping the branch.

Quick Start

Run abort.sh with an optional playbook path to perform an abort sequence.

Frequently Asked Questions about abort-playbook

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

FAQPage Schema
How do I abort a playbook workflow safely without creating a PR?

Abort a playbook by running abort.sh with the target playbook path. This transitions the playbook to aborted status, moves it to plan/archive with metadata, resets state.md fields (active and branch to null), and provides guidance on branch cleanup—all without triggering PR creation or merge.

What happens to state.md when I abort a playbook?

Aborting a playbook updates state.md by setting active and branch fields to null, synchronizing metadata to reflect the terminated workflow state while preserving audit history in the archived playbook.

Can I abort a playbook to switch tasks or clean up orphaned workflows?

Yes. Abort is designed to interrupt in-progress playbooks, switch contexts, or discard orphaned playbooks by archiving them with aborted status and timestamp, then guiding branch retention or deletion decisions.

What's the difference between aborting a playbook and letting it complete?

Aborting explicitly terminates a playbook, archives it with aborted status, updates state.md to null, and prevents PR creation. Completion follows the normal workflow. Abort is for controlled interruption and cleanup.

Do I need to manually delete the branch after aborting a playbook?

Abort provides guidance on branch handling but does not delete the branch automatically. You can retain or manually delete it based on the cleanup recommendation provided after abort completes.