Gsd Phase
open-gsd/gsd-core
Multi-phase management — add, insert, remove, or edit phases in ROADMAP.md (roadmap phase CRUD)
Structured plan file generation for large tasks -- phased planning, completion tracking, and decision documentation
MITAuto-check passed
Install Plan Documentation
$ npx skills add vibeeval/vibecosystem --skill plan-documentation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vibeeval/vibecosystem plan-documentation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/plan-documentation .claude/skills/plan-documentation && rm -rf skills-srcUse ~/.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/
Install the "plan-documentation" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/plan-documentation into .claude/skills/plan-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-documentation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vibeeval/vibecosystem/tree/main/skills/plan-documentationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vibeeval/vibecosystem --skill plan-documentation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vibeeval/vibecosystem plan-documentation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/plan-documentation .agents/skills/plan-documentation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "plan-documentation" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/plan-documentation into .agents/skills/plan-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-documentation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vibeeval/vibecosystem --skill plan-documentation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vibeeval/vibecosystem plan-documentation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/plan-documentation .cursor/skills/plan-documentation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "plan-documentation" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/plan-documentation into .cursor/skills/plan-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-documentation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vibeeval/vibecosystem.git --path skills/plan-documentation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vibeeval/vibecosystem --skill plan-documentation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vibeeval/vibecosystem plan-documentation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/plan-documentation .gemini/skills/plan-documentation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "plan-documentation" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/plan-documentation into .gemini/skills/plan-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-documentation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vibeeval/vibecosystem plan-documentationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vibeeval/vibecosystem --skill plan-documentation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/plan-documentation .github/skills/plan-documentation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "plan-documentation" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/plan-documentation into .github/skills/plan-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-documentation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vibeeval/vibecosystem --skill plan-documentation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vibeeval/vibecosystem plan-documentation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vibeeval/vibecosystem.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/plan-documentation .opencode/skills/plan-documentation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "plan-documentation" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/plan-documentation into .opencode/skills/plan-documentation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-documentation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
plan-documentation- GitHub stars
- 531
- Token cost
- ~1.2k tokens
- SKILL.md length
- 262 words
- Files
- 1
- Skills in repo
- 144
- Repo updated
- First seen
- Licence
- MIT
At a glance
Structured plan file generation for large tasks -- phased planning, completion tracking, and decision documentation
- SKILL.md covers When to Generate Plan Files, Plan Document Template, Phase Completion Template and Final Completion Template, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Plan Documentation is an agent skill from vibeeval/vibecosystem. Structured plan file generation for large tasks -- phased planning, completion tracking, and decision documentation
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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.
Example prompts
- “/plan-documentation”
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
Plan Documentation loads about 1.2k tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 262 words of instructions outside code blocks.
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). 262 words, ~1,151 tokens.
Download SKILL.mdSave it as
.claude/skills/plan-documentation/SKILL.md (or your agent's skills folder).- name
- plan-documentation
- description
- Structured plan file generation for large tasks -- phased planning, completion tracking, and decision documentation
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.
# 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 done>
- <Measurable or verifiable condition>
### Phase 2: <Phase Title>
- [ ] Step 1 description
- [ ] Step 2 description
**Acceptance Criteria:**
- <Condition>
### Phase N: <Phase Title>
...
## Open Questions
1. <Question about approach or requirement> -- Suggested: <Option A> vs <Option B>
2. <Question about scope> -- Suggested: <Option A> vs <Option B>
3. <Question about dependency or risk> -- Suggested: <Option A>
Keep open questions between 1-5. Each should have suggested options so they can be resolved quickly. Remove questions as they get answered -- move the decision to the relevant phase.
## Dependencies
- <External system, API, library, or team dependency>
- <Prerequisite work that must finish first>
## Risks
- <What could go wrong and how likely it is>
- <Mitigation strategy if applicable>Phase Completion Template
After finishing each phase, create plans/<task-slug>-phase-N-complete.md:
# Phase N Complete: <Phase Title>
Completed: <ISO date>
Plan: <task-slug>-plan.md
## Phase N Summary
<1-2 sentences on what was accomplished.>
## What Changed
| File | Change |
|------|--------|
| `path/to/file.ts` | Added validation logic for user input |
| `path/to/test.ts` | 6 new unit tests for validation edge cases |
## What Was Tested
- <Test suite or manual verification performed>
- <Edge cases covered>
- <What was NOT tested and why>
## Decisions Made
- <Decision>: <Why this option was chosen over alternatives>
## Next Phase Preview
Phase N+1 will focus on <brief description>. Prerequisites met: <yes/no>.Final Completion Template
When all phases are done, create plans/<task-slug>-complete.md:
# Complete: <Task Title>
Completed: <ISO date>
Plan: <task-slug>-plan.md
Duration: <how long the work took>
## Task Summary
<2-3 sentences on the full scope of work completed.>
## All Phases
| Phase | Title | Status |
|-------|-------|--------|
| 1 | <Title> | COMPLETE |
| 2 | <Title> | COMPLETE |
| N | <Title> | COMPLETE |
## Total Changes
- Files modified: <count>
- Files created: <count>
- Tests added: <count>
- Lines changed: <approximate>
## Lessons Learned
- <Insight that would help someone doing similar work>
- <Unexpected challenge and how it was resolved>
- <Pattern discovered that should be reused>File Naming Convention
All plan files go in the plans/ directory at the project root.
| File | Purpose |
|---|---|
<task-slug>-plan.md | Initial plan with phases and acceptance criteria |
<task-slug>-phase-N-complete.md | Completion record for phase N |
<task-slug>-complete.md | Final completion summary |
The <task-slug> should be a short, lowercase, hyphenated description of the task (e.g., auth-refactor, search-api-v2, dashboard-redesign).
Rules
- Write the plan BEFORE starting implementation
- Update phase status in the plan file as work progresses
- Do not skip phase completion docs -- they are the audit trail
- Keep summaries concise -- if it takes more than 3 sentences, it is too long
- Open questions should block work until resolved, not be ignored
- If the plan changes significantly mid-work, update the plan file and note what changed and why
© 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/plan-documentation of vibeeval/vibecosystem.
Open the folder on GitHubat commit 3b763b1
Compare with similar skills
Plan Documentation 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Plan Documentation this skillvibeeval/vibecosystem | 531 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Gsd Phaseopen-gsd/gsd-core | 10k | 1 repos | ~603 | Automated safety check: Notes | MIT | |
| Bio Phasing Imputation Haplotype PhasingGPTomics/bioSkills | 1.2k | 1 repos | ~4.2k | Automated safety check: Pass | MIT | |
| Large Class Stylesgl-project/sglang | 37k | 2 repos | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Gsd Execute Phaseopen-gsd/gsd-core | 10k | 1 repos | ~801 | Automated safety check: Notes | MIT | |
| Gsd Spec Phaseopen-gsd/gsd-core | 10k | 1 repos | ~658 | Automated safety check: Notes | MIT |
Similar skills
Bio Phasing Imputation Haplotype Phasing
GPTomics/bioSkills
Estimates haplotype phase from population linkage disequilibrium with SHAPEIT5, SHAPEIT4, Eagle2, or Beagle - turning unphased genotypes (0/1) into phased haplotypes (0|1) for imputation input…
Large Class Style
sgl-project/sglang
Code style for SGLang large classes Scheduler, TokenizerManager, and ModelRunner: frozen-code conventions and init orchestration style.
Gsd Execute Phase
open-gsd/gsd-core
SDD phase execution — execute all plans in a phase with dependency-aware wave parallelization
Gsd Spec Phase
open-gsd/gsd-core
Clarify WHAT a phase delivers with ambiguity scoring; produces a SPEC.md before discuss-phase.
Gsd Mvp Phase
open-gsd/gsd-core
Plan a phase as a vertical MVP slice — user story, SPIDR splitting, then plan-phase
More from vibeeval/vibecosystem
All 144 skills in this repoAgent Benchmark
vibeeval/vibecosystem
Framework for measuring and tracking agent response quality over time.
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.
Factcheck Guard
vibeeval/vibecosystem
A skill your agent uses when making any factual claim about the codebase — existence, absence, or behavior.
Fp Check
vibeeval/vibecosystem
Systematic false positive verification for security findings.
N8n Workflows
vibeeval/vibecosystem
n8n otomasyon workflow'lari. An agent skill from vibeeval/vibecosystem.
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.
Questions about Plan Documentation
What does Plan Documentation do?
Structured plan file generation for large tasks -- phased planning, completion tracking, and decision documentation. Plan Documentation is an agent skill from vibeeval/vibecosystem.
How do I install Plan Documentation in Claude Code?
Run `npx skills add vibeeval/vibecosystem --skill plan-documentation -a claude-code`. Or copy the skill folder (skills/plan-documentation in vibeeval/vibecosystem) into .claude/skills/plan-documentation in your project. Claude Code loads it when a task matches its description.
How do I install Plan Documentation in Codex?
Run `npx skills add vibeeval/vibecosystem --skill plan-documentation -a codex`. Or copy the skill folder (skills/plan-documentation in vibeeval/vibecosystem) into .agents/skills/plan-documentation in your project. Codex loads it when a task matches its description.
Can I use Plan Documentation 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 plan-documentation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plan-documentation, .gemini/skills/plan-documentation, .github/skills/plan-documentation and .opencode/skills/plan-documentation in your project.
What does Plan Documentation need to run?
SKILL.md names no scripts, command-line tools or credentials: Plan Documentation is instructions for the agent only.
Does Plan Documentation 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 Plan Documentation 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 Plan Documentation use?
Plan Documentation 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 Plan Documentation use?
About 1.2k tokens (SKILL.md is roughly 4.6k 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 Plan Documentation?
Skills that share tags, products or a category with Plan Documentation: Gsd Phase (open-gsd/gsd-core, 10k stars), Bio Phasing Imputation Haplotype Phasing (GPTomics/bioSkills, 1.2k stars), Large Class Style (sgl-project/sglang, 37k stars) and Gsd Execute Phase (open-gsd/gsd-core, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Plan Documentation?
vibeeval (a GitHub user) maintains it in vibeeval/vibecosystem, which has 531 GitHub stars. The repository holds 144 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.