close-plan

Archive completed plans and coordinate safe git commits and pushes.

19|3|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/changoo89/claude-pilot --skill close-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: close-plan
Source: https://github.com/changoo89/claude-pilot/tree/main/.claude/skills/close-plan
Command: npx skills add https://github.com/changoo89/claude-pilot --skill close-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the end-to-end plan closure process by archiving completed plans, validating top-level TODOs, and coordinating a safe git workflow.

Core Features & Use Cases

  • Plan archival to done/, optional documentation sync, and a verified git commit with attribution.
  • TODO gating and evidence verification to ensure all success criteria are satisfied before closing.
  • Optional worktree merge and push retries for resilient collaboration.

Quick Start

Invoke the close-plan workflow with /03_close [RUN_ID|plan_path] [no-commit] [no-push] [--force] to archive the plan and push final updates.

Frequently Asked Questions about close-plan

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

FAQPage Schema
How do I automate git commit and push after archiving completed plan workflows?

Automate plan closure by archiving completed plans, validating TODOs, and coordinating git commits with safe pushes. The workflow enforces step order, uses exponential backoff for pushes, and cleans up worktrees when merging changes.

What is the best way to validate TODOs and success criteria before a git push?

Validate TODOs through built-in gating and evidence verification to ensure all success criteria are satisfied before closing. This enforces step order and blocks closure until criteria are met, with an optional --force bypass for unresolved TODOs.

Can I skip unresolved TODOs when archiving plans and pushing final updates?

Yes, you can skip unresolved TODOs using the --force bypass flag when invoking the plan closure workflow. This overrides the standard TODO gating and evidence verification to allow archiving and pushing despite outstanding items.

How does worktree cleanup work when merging changes during plan closure?

Worktree cleanup is handled automatically when merging changes during the plan closure workflow. It coordinates optional worktree merges alongside git push retries using exponential backoff for resilient collaboration.

Do I need to manually sync documentation after archiving a plan?

No, manual documentation sync is not required. The plan closure workflow automates optional documentation synchronization alongside archiving completed plans to the done directory and committing verified updates.

What command invokes the plan archival and safe push workflow?

Invoke the workflow with /03_close [RUN_ID|plan_path] [no-commit] [no-push] [--force] to archive the plan and push final updates. This command handles everything from TODO verification to archival and optional documentation synchronization.