plan-close

Automate closure of planning items with status updates and notes.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/mikersays/mikersays-plugins --skill plan-close-mikersays
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-close
Source: https://github.com/mikersays/mikersays-plugins/tree/main/plugins/plan/skills/plan-close
Command: npx skills add https://github.com/mikersays/mikersays-plugins --skill plan-close-mikersays

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of marking planning items as completed, eliminating the need for manual updates and ensuring that the status is accurately reflected.

Core Features & Use Cases

  • Automatic Status Update: Quickly mark items as done with minimal input.
  • Closing Notes: Attach optional reasons for closure to maintain a record.
  • History Preservation: Retains closed items for historical reference without removal.

Quick Start

Close a planning item by typing /plan-close [item id] followed by an optional reason, like "I fixed the bug".

Frequently Asked Questions about plan-close

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

FAQPage Schema
How do I mark markdown planning items as completed automatically?

To automate planning item closure, issue a simple command with the item ID and an optional reason; the system then handles status updates, date stamping, and note appending automatically.

Can I add closing notes to issue tracking items in a markdown file?

Yes, you can attach optional closing notes to issue tracking items during plan closure, appending reasons for completion directly into your markdown documentation to maintain an accurate record.

Does this markdown planning automation permanently delete closed tasks?

No, this markdown planning automation preserves closed items rather than deleting them, retaining historical reference within your project documentation to maintain an accurate record of completed tasks.

What's the best way to automate plan closure for project management in markdown?

The best way to automate plan closure is by issuing a single command with the target item ID and an optional reason, eliminating manual updates while ensuring accurate status reflection in project documentation.

Do I need any external dependencies to use this markdown tracking tool?

No external dependencies are required to use this markdown tracking tool; it operates independently through internal scripts to handle status updates, date stamping, and note appending for project documentation.