New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Persistent Planning

by vibeeval in vibeeval/vibecosystem

Persistent planning system with 3 markdown files (PLAN.md, PROGRESS.md, CONTEXT.md).

MITAuto-check passedDevelopment

Install Persistent Planning

skills CLI
$ npx skills add vibeeval/vibecosystem --skill persistent-planning -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vibeeval/vibecosystem persistent-planning --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/persistent-planning .claude/skills/persistent-planning && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
persistent-planning
GitHub stars
531
Token cost
~415 tokens
SKILL.md length
103 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Persistent planning system with 3 markdown files (PLAN.md, PROGRESS.md, CONTEXT.md).

  • Works in 3 steps: thoughts/PLAN.md - Active plan → thoughts/PROGRESS.md - Auto-tracked… → thoughts/CONTEXT.md - Project context…
  • Starting large features
  • SKILL.md covers Overview, When to Create Plans, PLAN.md Format and CONTEXT.md Format, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Persistent Planning is an agent skill from vibeeval/vibecosystem. 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.

Its SKILL.md is about 420 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Refactoring. The repository describes itself as: AI software team for Claude Code - 138 agents, 295 skills, 73 hooks. Self-learning, multi-agent swarm, autonomous skill evolution. The licence is MIT.

When your agent uses it

  • Starting large features
  • Multi-session work
  • Complex refactoring

Example prompts

  • “/persistent-planning”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

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

What it can do on your machine

Read from SKILL.md and the folder at commit 3b763b1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Persistent Planning loads about 415 tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 103 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~55
When it runs · the whole SKILL.md, loaded when a task matches
~415

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vibeeval/vibecosystem at commit 3b763b1, republished under its MIT licence (© vibeeval). 103 words, ~415 tokens.

Download SKILL.mdSave it as .claude/skills/persistent-planning/SKILL.md (or your agent's skills folder).
name
persistent-planning
description
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.
user-invocable
false

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 (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

© vibeeval, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/persistent-planning of vibeeval/vibecosystem.

Open the folder on GitHubat commit 3b763b1

Compare with similar skills

Persistent Planning next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Persistent Planning compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Persistent Planning this skillvibeeval/vibecosystem531—~415Automated safety check: PassMIT
Guidelinesakash-network/node1.1k22 repos~577Automated safety check: PassMIT
Component Refactoringlangflow-ai/langflow156k—~3.5kAutomated safety check: PassMIT
Migrate Core Code to Submodulestinyhumansai/openhuman42k—~2.6kAutomated safety check: PassGPL-3.0
Systematic Code Refactoringluongnv89/claude-howto42k—~3kAutomated safety check: PassMIT
Codexskills-directory/skill-codex1.5k3 repos~1.8kAutomated safety check: PassMIT

Similar skills

  • Guidelines

    akash-network/node

    Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.

    1.1k GitHub starsUsed in 22 repos~577 tokens
    DevelopmentAuto-check passed

  • Component Refactoring

    langflow-ai/langflow

    Refactor high-complexity React components in Langflow frontend.

    156k GitHub stars~3.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Migrate Core Code to Submodules

    tinyhumansai/openhuman

    Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.

    42k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Systematic Code Refactoring

    luongnv89/claude-howto

    Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.

    42k GitHub stars~3k tokensUpdated 7 days ago
    DevelopmentAuto-check passed

  • Codex

    skills-directory/skill-codex

    A skill your agent uses when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing

    1.5k GitHub starsUsed in 3 repos~1.8k tokens
    DevelopmentAuto-check passed

  • Ponytail

    DavidObando/gsharp

    Forces the laziest solution that actually works, simplest, shortest, most minimal.

    565 GitHub starsUsed in 8 repos~1.7k tokens
    DevelopmentAuto-check passed

More from vibeeval/vibecosystem

All 12 skills in this repo

  • Agent Benchmark

    vibeeval/vibecosystem

    Framework for measuring and tracking agent response quality over time.

    531 GitHub stars~2.9k tokensUpdated 2 mo ago
    Auto-check passed

  • Differential Review

    vibeeval/vibecosystem

    Security-focused differential code review with blast radius analysis, risk-adaptive depth (DEEP/FOCUSED/SURGICAL), git history correlation, and structured finding format.

    531 GitHub stars~1.6k tokensUpdated 2 mo ago
    Auto-check passed

  • Factcheck Guard

    vibeeval/vibecosystem

    A skill your agent uses when making any factual claim about the codebase — existence, absence, or behavior.

    531 GitHub stars~2.2k tokensUpdated 2 mo ago
    Auto-check passed

  • Fp Check

    vibeeval/vibecosystem

    Systematic false positive verification for security findings.

    531 GitHub stars~1.6k tokensUpdated 2 mo ago
    Auto-check passed

  • N8n Workflows

    vibeeval/vibecosystem

    n8n otomasyon workflow'lari. An agent skill from vibeeval/vibecosystem.

    531 GitHub stars~3.3k tokensUpdated 2 mo ago
    Auto-check passed

  • Notepad System

    vibeeval/vibecosystem

    A skill your agent uses when context compression is imminent, when resuming a session, or when preserving critical decisions across long tasks.

    531 GitHub stars~1.7k tokensUpdated 2 mo ago
    Auto-check passed

Categories

Questions about Persistent Planning

What does Persistent Planning do?

Persistent planning system with 3 markdown files (PLAN.md, PROGRESS.md, CONTEXT.md). Persistent Planning is an agent skill from vibeeval/vibecosystem.md).

When should I use Persistent Planning?

Persistent Planning fits situations like: starting large features; multi-session work; complex refactoring.

How do I install Persistent Planning in Claude Code?

Run `npx skills add vibeeval/vibecosystem --skill persistent-planning -a claude-code`. Or copy the skill folder (skills/persistent-planning in vibeeval/vibecosystem) into .claude/skills/persistent-planning in your project. Claude Code loads it when a task matches its description.

How do I install Persistent Planning in Codex?

Run `npx skills add vibeeval/vibecosystem --skill persistent-planning -a codex`. Or copy the skill folder (skills/persistent-planning in vibeeval/vibecosystem) into .agents/skills/persistent-planning in your project. Codex loads it when a task matches its description.

Can I use Persistent Planning in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vibeeval/vibecosystem --skill persistent-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/persistent-planning, .gemini/skills/persistent-planning, .github/skills/persistent-planning and .opencode/skills/persistent-planning in your project.

What does Persistent Planning need to run?

SKILL.md names no scripts, command-line tools or credentials: Persistent Planning is instructions for the agent only.

Does Persistent Planning access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Persistent Planning safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Persistent Planning use?

Persistent Planning is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Persistent Planning use?

About 415 tokens (SKILL.md is roughly 1.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Persistent Planning?

Skills that share tags, products or a category with Persistent Planning: Guidelines (akash-network/node, 1.1k stars), Component Refactoring (langflow-ai/langflow, 156k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars) and Systematic Code Refactoring (luongnv89/claude-howto, 42k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Persistent Planning?

vibeeval (a GitHub user) maintains it in vibeeval/vibecosystem, which has 531 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on August 8, 2026.

Source: vibeeval/vibecosystem on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.