done

Name: done
Availability: InStock
Author: cloudvoyant

Complete and archive specification-driven development plans with Git commits and pull requests.

Updated Nov 15, 2025

Search Tags:#pull request #workflow automation #spec #archive #git commit #plan completion

Ready to run

npx skills add https://github.com/cloudvoyant/claudevoyant --skill done-cloudvoyant

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: done
Source: https://github.com/cloudvoyant/claudevoyant/tree/main/plugins/spec/skills/done
Command: npx skills add https://github.com/cloudvoyant/claudevoyant --skill done-cloudvoyant

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of finalizing and archiving project plans, ensuring that completed work is properly recorded and stored, and offering options for committing changes and creating pull requests.

Core Features & Use Cases

Plan Completion: Marks a spec plan as finished, verifying all tasks are done.
Commit Generation: Optionally creates a Git commit based on the plan's objective and changes.
Pull Request Creation: Facilitates creating a pull request for the completed plan's branch.
Archiving: Moves the completed plan and its associated files to an archive directory for historical reference.
Worktree Management: Offers to remove the associated worktree and optionally delete the plan's branch.

Quick Start

Use the done skill to mark the current plan as complete and archive it.

Frequently Asked Questions about done

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

FAQPage Schema

How do I mark a development plan as complete and archive it?▼

To mark a development plan complete and archive it, you finalize the spec plan by verifying tasks are done, then move the plan and its associated files to an archive directory for historical reference.

Can I automatically create a git commit and pull request when a plan finishes?▼

Yes, you can automatically generate a git commit and pull request when a plan finishes. The workflow optionally creates a commit based on the plan's objective and facilitates a pull request for the completed branch.

What is the best way to clean up git worktrees after a spec plan is done?▼

The best way to clean up git worktrees after a spec plan is done is to use workflow automation that offers to remove the associated worktree and optionally delete the plan's branch.

Does this workflow automation require the GitHub CLI for version control operations?▼

This workflow automation integrates with Git and the GitHub CLI for version control operations, using them to manage plan status, generate commits, and create pull requests.

What happens to completed specification-driven development plans?▼

Completed specification-driven development plans are moved to an archive directory along with their associated files, ensuring completed work is properly recorded and stored for historical reference.

How do I verify all tasks in a spec plan are finished before archiving?▼

To verify all tasks in a spec plan are finished before archiving, the completion workflow marks the plan as finished by verifying that all specified tasks are done before moving files to the archive.