plans-management_skill

This skill helps you manage Plans.md tasks and markers, updating statuses and archiving consistently to keep planning synchronized with work.
  • Shell

212

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill chachamaru127/claude-code-harness --skill plans-management

  • SKILL.md5.8 KB

Overview

This skill manages Tasks and marker operations inside Plans.md. It provides consistent edits for adding tasks, changing task status, marking completion, and archiving completed items. Use it only for Plans.md task operations, not for implementation code, reviews, or other files.

How this skill works

When triggered by task-related phrases, the skill parses Plans.md structure, applies marker formatting rules, updates timestamps and the updater field, and preserves section order. It can add tasks, convert markers between states, append completion dates, and move aged completed tasks to the archive section. The skill enforces formatting (backticks for markers, no extra spaces) and keeps empty section headers intact.

When to use it

  • Add a new task to Plans.md (e.g., 'add a task').
  • Change a task state between TODO, WIP, completed, or blocked.
  • Mark a task as complete and append the completion date.
  • Archive completed tasks that are older than seven days.
  • Update the Plans.md header last-updated timestamp and updater field.

Best practices

  • Always edit only Plans.md for task operations; avoid touching implementation or review files.
  • Use backticks for markers and avoid spaces inside markers (e.g., cc:WIP).
  • Keep section order: In-progress → Not started → Done → Archive.
  • Update the header timestamp and updater on every change.
  • Leave empty section headers in place to preserve structure.

Example use cases

  • Add a new TODO task with optional details and related file paths.
  • Transition a task from cc:TODO to cc:WIP when work starts.
  • Mark a WIP task complete and add the completion date (YYYY-MM-DD).
  • Move tasks older than seven days in 'Done' to the 'Archive' section with a month grouping.
  • Mark a task as blocked and add block reason, owner, and deadline.

FAQ

No. It is strictly designed for Plans.md task and marker operations.

How are completion dates formatted?

Use YYYY-MM-DD appended to the completed task line, e.g., - [x] Task cc:完了 (2024-01-15).

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
plans-management skill by chachamaru127/claude-code-harness | VeilStrat