mcpbeat

Persistent Planning

vibeeval/persistent-planning

Persistent planning system with 3 markdown files (PLAN.md, PROGRESS.md, CONTEXT.md). Use when starting large features, multi-session work, or complex refactoring. Auto-tracks commits in PROGRESS.md.

414 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
521
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/vibeeval/vibecosystem --skill persistent-planning

The instruction itself

7 sections, as written by the author

Persistent Planning System

Overview

Use 3 persistent markdown files to track plans across sessions:

  • thoughts/PLAN.md - Active plan
  • thoughts/PROGRESS.md - Auto-tracked progress (commits)
  • thoughts/CONTEXT.md - Project context and constraints

When to Create Plans

  • Multi-file features (3+ files)
  • Multi-session work
  • Complex refactoring
  • Architectural changes

PLAN.md Format

# Plan: [Feature Name]

## Goal
What we're building and why.

## Steps
1. [ ] Step one
2. [ ] Step two
3. [ ] Step three

## Constraints
- Must be backward compatible
- Must pass existing tests

## Status
IN PROGRESS | COMPLETED | BLOCKED

CONTEXT.md Format

# Project Context

## Architecture Decisions
- Using X because Y
- Chose A over B because C

## Key Files
- src/auth.ts - Authentication logic
- src/api/ - API endpoints

## Known Issues
- Rate limiting not implemented yet

How It Works

  • Session start: If thoughts/PLAN.md exists, it's injected into context
  • After commits: thoughts/PROGRESS.md is auto-updated with commit hash and message
  • Plan completion: Update PLAN.md status to COMPLETED

Notes

  • Plans are project-local (in the project's thoughts/ directory)
  • PROGRESS.md is append-only (never loses history)
  • Add thoughts/ to .gitignore if you don't want plans in version control

How to use it

Copy the folder

Take vibeeval/persistent-planning from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.