plan-keeper

Enforce plan file placement, frontmatter integrity, and lifecycle transitions.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/ctxr-dev/agent-staff-engineer --skill plan-keeper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-keeper
Source: https://github.com/ctxr-dev/agent-staff-engineer/tree/main/skills/plan-keeper
Command: npx skills add https://github.com/ctxr-dev/agent-staff-engineer --skill plan-keeper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and enforces the correct plan-file lifecycle by ensuring every plan sits in the right folder, carries the required frontmatter, and updates status across states.

Core Features & Use Cases

  • Organizes plan files into the proper lifecycle folders (todo, in-progress, in-review, done) and validates frontmatter contracts.
  • Normalizes checkboxes and preserves the rest of the content while moving plans between states.
  • Guards against writes outside the configured plans_root and surfaces issues when conflicts or invalid frontmatter are detected.

Quick Start

Create a plan file under the configured plans_root and let plan-keeper auto-correct structure on save.

Frequently Asked Questions about plan-keeper

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

FAQPage Schema
How do I enforce frontmatter integrity for plan files in my project?

Plan-keeper enforces frontmatter integrity by validating the required schema across all plan files, detecting conflicts, and normalizing structure automatically during lifecycle transitions.

How do I automate plan file movement between lifecycle folders?

You automate plan file movement by letting plan-keeper transition files between lifecycle folders such as todo, in-progress, in-review, and done while preserving the underlying content safely.

How does plan lifecycle automation handle checkbox normalization?

Plan lifecycle automation normalizes checkboxes and preserves the rest of the content while moving plans between states, ensuring formatting consistency without altering body text.

Do I need existing paths configuration to manage my plan tree?

Yes, you need existing paths configuration including a defined plans_root directory, valid frontmatter schema, and read/write access to perform safe, idempotent operations on your plan tree.

What happens if I try to write plan files outside the configured plans_root?

Plan-keeper guards against writes outside the configured plans_root directory, blocking unauthorized modifications entirely and surfacing issues immediately when invalid operations are attempted.

What is the best way to structure a project plan tree for DevOps workflows?

The best way is organizing plan files into dedicated lifecycle folders under plans_root, letting plan-keeper auto-correct structure, validate frontmatter, and manage state transitions automatically on save.