plan-complete

Move completed plans from plans/active to plans/complete with git commits.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/brmatola/gremlins --skill plan-complete
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-complete
Source: https://github.com/brmatola/gremlins/tree/main/skills/plan-complete
Command: npx skills add https://github.com/brmatola/gremlins --skill plan-complete

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams finalize work by moving a completed plan from active to complete and recording what was accomplished for future reference.

Core Features & Use Cases

  • Move a completed plan from plans/active/{plan-name} to plans/complete/{plan-name} to reflect its shipped status.
  • Create optional Completion Notes to capture summary, date, and key references.
  • Commit the change and provide a clear audit trail for verification and handoff.

Quick Start

Step-by-step commands to verify completion, add notes, and finalize the plan:

  • Verify completion: ls plans/active/{plan-name}/
  • Check status: git status
  • Add completion notes (optional): create plans/active/{plan-name}/completion.md with a simple header and fields
  • Move to complete: mv plans/active/{plan-name} plans/complete/{plan-name}
  • Commit: git add -A; git commit -m "docs: mark {plan-name} plan as complete"
  • Report: Plan '{plan-name}' marked complete. Location: plans/complete/{plan-name}/

Frequently Asked Questions about plan-complete

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

FAQPage Schema
How do I move a completed plan to a complete directory in git?

To move a completed plan, you move it from plans/active to plans/complete using shell commands, add optional completion notes, and commit the directory change via git to maintain an auditable trace.

What is the best way to maintain an audit trail for finished project plans?

Maintaining an audit trail for finished plans involves moving the plan directory to plans/complete, creating a completion.md file with summaries and key references, and committing the changes to git for a verifiable historical record.

How do I create completion notes for a software project handoff?

You create completion notes for a handoff by adding a completion.md file inside the active plan directory, capturing the completion summary, date, and key references before moving the plan and committing it to git.

Can I use standard shell commands to finalize and track planning workflows?

Yes, you can use standard shell commands like ls and mv to verify and move plan directories, combined with git operations to commit the finalized workflow, ensuring the handoff is tracked directly in your repository.

Do I need to add completion notes before moving a plan to complete?

No, creating completion notes with a summary and date is optional, but adding a completion.md file before moving the directory to plans/complete and committing provides a better historical reference for future verification.