Plan
codewhale-hq/Codewhale
Turn a sufficiently understood task into an ordered implementation plan with dependencies and verification.
Discover related plans for the current task: same feature folder full depth, other features active-only, general-plans active.
MITAuto-check passed
Install Vc Plan Discovery
$ npx skills add withkynam/vibecode-pro-max-kit --skill vc-plan-discovery -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install withkynam/vibecode-pro-max-kit vc-plan-discovery --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/withkynam/vibecode-pro-max-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/vc-plan-discovery .claude/skills/vc-plan-discovery && 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 "vc-plan-discovery" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-plan-discovery into .claude/skills/vc-plan-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-plan-discovery", 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/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-plan-discoveryType 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 withkynam/vibecode-pro-max-kit --skill vc-plan-discovery -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install withkynam/vibecode-pro-max-kit vc-plan-discovery --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/vc-plan-discovery .agents/skills/vc-plan-discovery && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vc-plan-discovery" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-plan-discovery into .agents/skills/vc-plan-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-plan-discovery", 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 withkynam/vibecode-pro-max-kit --skill vc-plan-discovery -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install withkynam/vibecode-pro-max-kit vc-plan-discovery --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/vc-plan-discovery .cursor/skills/vc-plan-discovery && 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 "vc-plan-discovery" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-plan-discovery into .cursor/skills/vc-plan-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-plan-discovery", 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/withkynam/vibecode-pro-max-kit.git --path .claude/skills/vc-plan-discovery--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 withkynam/vibecode-pro-max-kit --skill vc-plan-discovery -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install withkynam/vibecode-pro-max-kit vc-plan-discovery --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/vc-plan-discovery .gemini/skills/vc-plan-discovery && 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 "vc-plan-discovery" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-plan-discovery into .gemini/skills/vc-plan-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-plan-discovery", 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 withkynam/vibecode-pro-max-kit vc-plan-discoveryInstalls 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 withkynam/vibecode-pro-max-kit --skill vc-plan-discovery -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/vc-plan-discovery .github/skills/vc-plan-discovery && 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 "vc-plan-discovery" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-plan-discovery into .github/skills/vc-plan-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-plan-discovery", 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 withkynam/vibecode-pro-max-kit --skill vc-plan-discovery -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install withkynam/vibecode-pro-max-kit vc-plan-discovery --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/withkynam/vibecode-pro-max-kit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/vc-plan-discovery .opencode/skills/vc-plan-discovery && 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 "vc-plan-discovery" agent skill from https://github.com/withkynam/vibecode-pro-max-kit/tree/main/.claude/skills/vc-plan-discovery into .opencode/skills/vc-plan-discovery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vc-plan-discovery", 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
vc-plan-discovery- GitHub stars
- 1.1k
- Token cost
- ~959 tokens
- SKILL.md length
- 390 words
- Files
- 5 (incl. scripts)
- Skills in repo
- 32
- Repo updated
- First seen
- Licence
- MIT
At a glance
Discover related plans for the current task: same feature folder full depth, other features active-only, general-plans active.
- SKILL.md covers Invocation, Purpose, Scope Rules and Frontmatter Reading, plus 2 more sections
- Runs JavaScript scripts from its folder; calls node
What it does
Vc Plan Discovery is an agent skill from withkynam/vibecode-pro-max-kit. Discover related plans for the current task: same feature folder full depth, other features active-only, general-plans active. Like vc-context-discovery but for plan artifacts.
Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts (for example `scripts/fixtures/validate-plan-discovery-output/fail.md` and `scripts/fixtures/validate-plan-discovery-output/pass.md`).
The repository describes itself as: Your AI forgets. This remembers. Spec-driven coding harness for vibecoders, product owners, CEOs and real builders — self-improving context memory, 15 agents, 33 skills working…. The licence is MIT.
Example prompts
- “/vc-plan-discovery”
Requirements
- Node.js
What it can do on your machine
Read from SKILL.md and the folder at commit 3bcb2f9. 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
Ships 4 files in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
node
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
Vc Plan Discovery loads about 959 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 390 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); the scripts in this folder are not scanned.
SKILL.md
The full file from withkynam/vibecode-pro-max-kit at commit 3bcb2f9, republished under its MIT licence (© withkynam). 390 words, ~959 tokens.
Download SKILL.mdSave it as
.claude/skills/vc-plan-discovery/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- vc-plan-discovery
- description
- Discover related plans for the current task: same feature folder full depth, other features active-only, general-plans active. Like vc-context-discovery but for plan artifacts.
- argument-hint
- [feature folder name or task description]
- trigger_keywords
- related plans, what was tried, plan history, feature backlog, plan discovery
- layer
- contract
- metadata.author
- vibecode-pro-max-kit
- metadata.version
- 1.1.0
vc-plan-discovery
Output style: Follow
process/development-protocols/communication-standards.md— answer-first, plain language, no unexplained jargon, TL;DR on long responses.
Invocation
Primary method — run the auto-discovery script. It applies the Scope Rules below
(same-feature full depth; other features active-only; general-plans active always) and
extracts ONLY the leading YAML frontmatter block of each .md file (no whole-file reads):
node .claude/skills/vc-plan-discovery/scripts/discover-plans.mjs [--feature <name>] [--json]It groups output into Active Plans / Backlog / Completed / Reports / References (each line:
- [name]: description (path)) and prints a trailing Found N active, N backlog, N completed, N reports, N references line. It never throws on a missing root and exits 0
unless given a bad flag. Use --json for a machine-readable object. Prefer this over the
manual scan below — it is deterministic and avoids loading huge files into context.
Per task-folder artefact colocation, the script scans one level into each
{slug}_{date}/ task folder and surfaces co-located _PLAN_/_REPORT_/_REF_ artefacts;
the sibling reports//references/ dirs are deprecated and only hold legacy artefacts.
The manual scan in Scope Rules below is the FALLBACK for when the script fails.
Purpose
Surface all plans relevant to the current task so agents have full plan context — what was tried, what is in progress, what is deferred, and what reports and references exist — before doing any phase work.
Show full SKILL.md (188 more words)Show less
Scope Rules
- Same feature folder (from task context or argument): read ALL of
active/,backlog/,completed/, plus any legacy siblingreports/,references/— surface every file with frontmatter - Other feature folders: read
active/only — surface plans whose frontmatterdescriptionorfeaturefield matches the task domain general-plans/active/: always scangeneral-plans/completed/, legacyreports/,references/: scan only when same-feature folder is not identified
Per task-folder artefact colocation, expect every current artefact (plan, spec, reports, references) INSIDE its {slug}_{date}/ task folder — scan one level into each task folder. The sibling reports//references/ dirs are deprecated and only hold legacy artefacts.
Frontmatter Reading
Read frontmatter fields: name, description, type, feature, phase
Route by description field for relevance matching (same approach as vc-context-discovery).
Skip files without frontmatter or with incomplete frontmatter — log as "no frontmatter, skipped".
Output: grouped list by folder — Active Plans / Backlog / Completed / Reports / References — with name + description per file.
When To Invoke
- First action alongside
vc-context-discoveryat the start of every loop step (research / validate / execute / update-process) - Any time an agent needs to know: what plans exist for this feature, what was tried before, what is deferred, what references exist
Output Format
### Active Plans
- [name]: description (path)
### Backlog
- [name]: description (path)
### Completed
- [name]: description (path)
### Reports
- [name]: description (path)
### References
- [name]: description (path)
Found N active, N backlog, N completed, N reports, N references© withkynam, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (scripts) in .claude/skills/vc-plan-discovery of withkynam/vibecode-pro-max-kit.
- SKILL.md
- scripts/discover-plans.mjs
- scripts/fixtures/validate-plan-discovery-output/fail.md
- scripts/fixtures/validate-plan-discovery-output/pass.md
- scripts/validate-plan-discovery-output.mjs
Open the folder on GitHubat commit 3bcb2f9
Compare with similar skills
Vc Plan Discovery 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 |
|---|---|---|---|---|---|---|
| Vc Plan Discovery this skillwithkynam/vibecode-pro-max-kit | 1.1k | — | ~959 | Automated safety check: Pass | MIT | |
| Plancodewhale-hq/Codewhale | 41k | — | ~213 | Automated safety check: Pass | MIT | |
| Planningn8n-io/n8n | 207k | — | ~2.5k | Automated safety check: Pass | Custom licence | |
| Planasgeirtj/system_prompts_leaks | 69k | — | ~5.1k | Automated safety check: Pass | CC0-1.0 | |
| Review Planpenpot/penpot | 61k | — | ~841 | Automated safety check: Pass | MPL-2.0 | |
| Make A Planpenpot/penpot | 61k | — | ~1.6k | Automated safety check: Pass | MPL-2.0 |
Similar skills
- Official
Planning
n8n-io/n8n
ONLY for coordinated multi-artifact work: multiple workflows with dependencies, shared data-table schema/migration across tasks, or the user explicitly asked to review a plan first.
Plan
asgeirtj/system_prompts_leaks
On an explicit planning request, always call readskill for this skill before answering.
Review Plan
penpot/penpot
Plan review flow — evaluate an implementation plan before it is executed, delegating the review to a subagent that follows the plan-review-criteria skill.
Make A Plan
penpot/penpot
Planning flow — research the subject of this session, produce an implementation plan with the planner skill, resolve open questions with the user in plain language, and save the final plan to…
Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
More from withkynam/vibecode-pro-max-kit
All 32 skills in this repoLibrary Documentation Seeker
withkynam/vibecode-pro-max-kit
Looks up library and framework documentation through Context7 first, with bundled Node scripts as a fallback that fetch and analyze llms.txt files.
Vc Sequential Thinking
withkynam/vibecode-pro-max-kit
Apply step-by-step analysis for complex problems with revision capability.
Agent Browser Automation
withkynam/vibecode-pro-max-kit
Drives a browser through the agent-browser CLI, using compact snapshots with element refs to keep context small in long sessions, plus video recording and cloud browsers.
Context Routing Audit
withkynam/vibecode-pro-max-kit
Audits a project's context routing, skill discoverability and skill wiring by running a chain of validator scripts and fixing whatever they report.
Active Plan Audit
withkynam/vibecode-pro-max-kit
Reviews a codebase's active plan files for staleness and completion, then archives only the ones confirmed done or obsolete against the real code.
Systematic Debugging and Investigation
withkynam/vibecode-pro-max-kit
Forces root-cause investigation before any fix, combining a four-phase debugging method with log, CI and performance investigation techniques and a rule against unverified completion claims.
Questions about Vc Plan Discovery
What does Vc Plan Discovery do?
Discover related plans for the current task: same feature folder full depth, other features active-only, general-plans active. Vc Plan Discovery is an agent skill from withkynam/vibecode-pro-max-kit. Discover related plans for the current task: same feature folder full depth, other features active-only, general-plans active.
How do I install Vc Plan Discovery in Claude Code?
Run `npx skills add withkynam/vibecode-pro-max-kit --skill vc-plan-discovery -a claude-code`. Or copy the skill folder (.claude/skills/vc-plan-discovery in withkynam/vibecode-pro-max-kit) into .claude/skills/vc-plan-discovery in your project. Claude Code loads it when a task matches its description.
How do I install Vc Plan Discovery in Codex?
Run `npx skills add withkynam/vibecode-pro-max-kit --skill vc-plan-discovery -a codex`. Or copy the skill folder (.claude/skills/vc-plan-discovery in withkynam/vibecode-pro-max-kit) into .agents/skills/vc-plan-discovery in your project. Codex loads it when a task matches its description.
Can I use Vc Plan Discovery 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 withkynam/vibecode-pro-max-kit --skill vc-plan-discovery -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vc-plan-discovery, .gemini/skills/vc-plan-discovery, .github/skills/vc-plan-discovery and .opencode/skills/vc-plan-discovery in your project.
What does Vc Plan Discovery need to run?
Going by SKILL.md and its folder, Vc Plan Discovery needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node). Our summary lists: Node.js.
Does Vc Plan Discovery 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 Vc Plan Discovery 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Vc Plan Discovery use?
Vc Plan Discovery 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 Vc Plan Discovery use?
About 959 tokens (SKILL.md is roughly 3.8k 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 Vc Plan Discovery?
Skills that share tags, products or a category with Vc Plan Discovery: Plan (codewhale-hq/Codewhale, 41k stars), Planning (n8n-io/n8n, 207k stars), Plan (asgeirtj/system_prompts_leaks, 69k stars) and Review Plan (penpot/penpot, 61k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vc Plan Discovery?
withkynam (a GitHub user) maintains it in withkynam/vibecode-pro-max-kit, which has 1,145 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on June 21, 2026.
Source: withkynam/vibecode-pro-max-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.