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.
Profile →npx skills add vibeeval/vibecosystem --skill persistent-planning --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Persistent Planning System ## Overview Use 3 persistent markdown files to track plans across sessions: 1. **`thoughts/PLAN.md`** - Active plan 2. **`thoughts/PROGRESS.md`** - Auto-tracked progress (commits) 3. **`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 ```markdown # 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 ```markdown # 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 (i
- Overview
- When to Create Plans
- PLAN.md Format
- CONTEXT.md Format
- How It Works
- Notes
What does the persistent-planning skill do?
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.
How do I install it?
Run `npx skills add vibeeval/vibecosystem --skill persistent-planning --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From vibeeval/vibecosystem, a repository with 521 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.