plan-documentation
Structured plan file generation for large tasks -- phased planning, completion tracking, and decision documentation
npx skills add vibeeval/vibecosystem --skill plan-documentation --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.
# Plan Documentation Generate structured plan files when starting large features, refactoring efforts, or multi-phase work. Plans create a paper trail that survives context resets and helps collaborators understand what was planned, what changed, and why. ## When to Generate Plan Files Create a plan document when: - The task spans more than 2 files or requires multiple coordinated changes - Work will take more than one session or phase - Multiple approaches exist and the chosen path should be documented - Other people (or future you) need to understand the sequence of work Do NOT create plan files for: - Single-file fixes or tweaks - Routine maintenance (dependency updates, formatting) - Tasks that can be completed in under 15 minutes ## Plan Document Template Create the plan at `plans/<task-slug>-plan.md` in the project root. ```markdown # Plan: <Task Title> Created: <ISO date> Status: IN_PROGRESS | COMPLETE | ABANDONED ## Summary <2-3 sentences explaining what this work accomplishes and why it matters.> ## Phases ### Phase 1: <Phase Title> - [ ] Step 1 description - [ ] Step 2 description - [ ] Step 3 description **Acceptance Criteria:** - <What must be true when this phase is do
- When to Generate Plan Files
- Plan Document Template
- Phase Completion Template
- Final Completion Template
- File Naming Convention
- Rules
What does the plan-documentation skill do?
Structured plan file generation for large tasks -- phased planning, completion tracking, and decision documentation
How do I install it?
Run `npx skills add vibeeval/vibecosystem --skill plan-documentation --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.