Create Vibe Feature
mistralai/mistral-vibe
Guides feature work in the Mistral Vibe Python CLI so each change lands in the right module and matches the project's architecture decision records.
Maintain a structured planning document tree made of roadmap/status files, implementation status or handoff TODO files, topic notes, decision records, open questions, ideas/inspiration pools, and…
Install Plan Tree
$ npx skills add SeemSeam/claude_codex_bridge --skill plan-tree -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install SeemSeam/claude_codex_bridge plan-tree --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/SeemSeam/claude_codex_bridge.git skills-src && mkdir -p .claude/skills && cp -r skills-src/useful_tools/codex_skills/plan-tree .claude/skills/plan-tree && 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-tree" agent skill from https://github.com/SeemSeam/claude_codex_bridge/tree/main/useful_tools/codex_skills/plan-tree into .claude/skills/plan-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-tree", 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/SeemSeam/claude_codex_bridge/tree/main/useful_tools/codex_skills/plan-treeType 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 SeemSeam/claude_codex_bridge --skill plan-tree -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install SeemSeam/claude_codex_bridge plan-tree --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SeemSeam/claude_codex_bridge.git skills-src && mkdir -p .agents/skills && cp -r skills-src/useful_tools/codex_skills/plan-tree .agents/skills/plan-tree && 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-tree" agent skill from https://github.com/SeemSeam/claude_codex_bridge/tree/main/useful_tools/codex_skills/plan-tree into .agents/skills/plan-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-tree", 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 SeemSeam/claude_codex_bridge --skill plan-tree -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install SeemSeam/claude_codex_bridge plan-tree --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SeemSeam/claude_codex_bridge.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/useful_tools/codex_skills/plan-tree .cursor/skills/plan-tree && 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-tree" agent skill from https://github.com/SeemSeam/claude_codex_bridge/tree/main/useful_tools/codex_skills/plan-tree into .cursor/skills/plan-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-tree", 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/SeemSeam/claude_codex_bridge.git --path useful_tools/codex_skills/plan-tree--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 SeemSeam/claude_codex_bridge --skill plan-tree -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install SeemSeam/claude_codex_bridge plan-tree --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SeemSeam/claude_codex_bridge.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/useful_tools/codex_skills/plan-tree .gemini/skills/plan-tree && 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-tree" agent skill from https://github.com/SeemSeam/claude_codex_bridge/tree/main/useful_tools/codex_skills/plan-tree into .gemini/skills/plan-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-tree", 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 SeemSeam/claude_codex_bridge plan-treeInstalls 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 SeemSeam/claude_codex_bridge --skill plan-tree -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/SeemSeam/claude_codex_bridge.git skills-src && mkdir -p .github/skills && cp -r skills-src/useful_tools/codex_skills/plan-tree .github/skills/plan-tree && 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-tree" agent skill from https://github.com/SeemSeam/claude_codex_bridge/tree/main/useful_tools/codex_skills/plan-tree into .github/skills/plan-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-tree", 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 SeemSeam/claude_codex_bridge --skill plan-tree -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install SeemSeam/claude_codex_bridge plan-tree --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SeemSeam/claude_codex_bridge.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/useful_tools/codex_skills/plan-tree .opencode/skills/plan-tree && 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-tree" agent skill from https://github.com/SeemSeam/claude_codex_bridge/tree/main/useful_tools/codex_skills/plan-tree into .opencode/skills/plan-tree/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-tree", 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-tree- GitHub stars
- 3.5k
- Token cost
- ~6.3k tokens
- SKILL.md length
- 3,404 words
- Files
- 2
- Skills in repo
- 28
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Maintain a structured planning document tree made of roadmap/status files, implementation status or handoff TODO files, topic notes, decision records, open questions, ideas/inspiration pools, and…
- Works in 8 steps: Identify the plan root and user intent… → Read the root index plus only the… → Classify the request as an idea,… → …
- Codex needs to create
- SKILL.md covers Execution Contract, Intent Routing, Document Model and Root And Folder Governance, plus 12 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Plan Tree is an agent skill from SeemSeam/claude_codex_bridge. Maintain a structured planning document tree made of roadmap/status files, implementation status or handoff TODO files, topic notes, decision records, open questions, ideas/inspiration pools, and repository/file-structure hygiene plans. Use when Codex needs to create, reorganize, audit, or update a multi-file plan, design-doc folder, roadmap tree, active implementation-status file, repo cleanup/filesystem plan, ADR/decision log, ideas inbox, or linked planning knowledge base; reconcile Done/In Progress/Next…
Its SKILL.md is about 6.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Development, covering Architecture decision records, Session handoff and Email management. The repository describes itself as: Visible multi-agent CLI workspace for mixing Codex, Claude, Gemini, Kimi, Qwen, Cursor, Copilot, Pi, OpenCode, and other AI coding agents.
When your agent uses it
- Codex needs to create
- Update a multi-file plan
- Design-doc folder
- Active implementation-status file
Example prompts
- “/plan-tree”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Identify the plan root and user intent before editing.
- Read the root index plus only the relevant status, topic, decision, question, idea, or history files.
- Classify the request as an idea, promotion, status update, question, decision, archive, audit, resume, restructure, or consistency repair.
- Preserve the existing planning entrypoint, registered plan roots, folder names, document style, and authority order unless the task is…
- Keep active roadmap and handoff files small; move historical evidence out of active state.
- Update indexes, retrieval headers, and links when adding, moving, promoting, archiving, or splitting durable files.
- Run the final checks before replying.
- Report changed files, unresolved questions, and the next useful maintenance action.
What it can do on your machine
Read from SKILL.md and the folder at commit 0b81137. 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 Tree loads about 6.3k tokens when it runs. Until then it costs about 190 tokens; SKILL.md has 3,404 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 3,404 words (~6,346 tokens).
“Use this skill to manage a tree of Markdown planning documents. The goal is to keep plans navigable, current, and internally consistent while preserving the user's intent and existing document style.”
- name
- plan-tree
Files
SKILL.md and 1 other file in useful_tools/codex_skills/plan-tree of SeemSeam/claude_codex_bridge.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 0b81137
Compare with similar skills
Plan Tree 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 Tree this skillSeemSeam/claude_codex_bridge | 3.5k | — | ~6.3k | Automated safety check: Pass | Custom licence | |
| Create Vibe Featuremistralai/mistral-vibe | 5.1k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| ObservalObserval/Observal | 4.1k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Auto Memorytractorjuice/arc-kit | 2.3k | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| Grill With Docsmeain/dotfiles | 285 | 21 repos | ~875 | Automated safety check: Pass | MIT | |
| Rememberantonio-orionus/Arroxy | 389 | — | ~571 | Automated safety check: Pass | MIT |
Similar skills
- Official
Observal
Observal/Observal
A skill your agent uses when starting any task the organization may already have an approved skill, prompt, MCP server, or Agent for: reviewing code, a commit, a diff, or a pull request; writing…
Auto Memory
tractorjuice/arc-kit
This skill should be used when the user asks to 'set up memory', 'create memory files', 'create MEMORY.md', 'set up topic files', 'improve memory organization', 'what should I remember', 'how to…
Grill With Docs
meain/dotfiles
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise.
Remember
antonio-orionus/Arroxy
Persists a durable Arroxy lesson — a gotcha, user preference, workflow rule, or design decision — to the right tracked file (project memory, AGENTS.md, CONTEXT.md, dev-docs, or an ADR) so any coding…
Grounding A Design
andrew-blake/melcloudhome
A skill your agent uses when about to propose, brainstorm, review or revise a design, fix approach or plan for a feature or behaviour change in this repo, including "brief" or "quick" design…
More from SeemSeam/claude_codex_bridge
All 28 skills in this repoCcb GitHub
SeemSeam/claude_codex_bridge
Maintain this CCB project's GitHub-facing release and npm publication surface.
Ccb Diagnose
SeemSeam/claude_codex_bridge
Diagnose a named CCB agent by combining authoritative runtime and job lineage with deep read-only pane inspection, apply bounded recovery when evidence supports it, verify the result, and request…
Ask
SeemSeam/claude_codex_bridge
Delegate work or request information from another CCB-managed agent using ask.
Assigned Review Chain
SeemSeam/claude_codex_bridge
Submit one node result to the assigned Reviewer and finish only after a bounded pass/rework chain.
Frontdesk Intake
SeemSeam/claude_codex_bridge
Convert user conversation into macro workflow requests and present curated clarification or final artifacts.
Planner Closure Backfill
SeemSeam/claude_codex_bridge
Produce one revision-fenced Planner backfill proposal for either a Detailer replan or task-set closure, with compact Frontdesk status evidence.
Related
Questions about Plan Tree
What does Plan Tree do?
Maintain a structured planning document tree made of roadmap/status files, implementation status or handoff TODO files, topic notes, decision records, open questions, ideas/inspiration pools, and…. Plan Tree is an agent skill from SeemSeam/claude_codex_bridge. Maintain a structured planning document tree made of roadmap/status files, implementation status or handoff TODO files, topic notes, decision records, open questions, ideas/inspiration pools, and repository/file-structure hygiene plans.
When should I use Plan Tree?
Plan Tree fits situations like: Codex needs to create; update a multi-file plan; design-doc folder; active implementation-status file.
How do I install Plan Tree in Claude Code?
Run `npx skills add SeemSeam/claude_codex_bridge --skill plan-tree -a claude-code`. Or copy the skill folder (useful_tools/codex_skills/plan-tree in SeemSeam/claude_codex_bridge) into .claude/skills/plan-tree in your project. Claude Code loads it when a task matches its description.
How do I install Plan Tree in Codex?
Run `npx skills add SeemSeam/claude_codex_bridge --skill plan-tree -a codex`. Or copy the skill folder (useful_tools/codex_skills/plan-tree in SeemSeam/claude_codex_bridge) into .agents/skills/plan-tree in your project. Codex loads it when a task matches its description.
Can I use Plan Tree 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 SeemSeam/claude_codex_bridge --skill plan-tree -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-tree, .gemini/skills/plan-tree, .github/skills/plan-tree and .opencode/skills/plan-tree in your project.
What does Plan Tree need to run?
SKILL.md names no scripts, command-line tools or credentials: Plan Tree is instructions for the agent only.
Does Plan Tree 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 Tree 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 Tree use?
Plan Tree has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Plan Tree use?
About 6.3k tokens (SKILL.md is roughly 25k 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 Tree?
Skills that share tags, products or a category with Plan Tree: Create Vibe Feature (mistralai/mistral-vibe, 5.1k stars), Observal (Observal/Observal, 4.1k stars), Auto Memory (tractorjuice/arc-kit, 2.3k stars) and Grill With Docs (meain/dotfiles, 285 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Plan Tree?
SeemSeam (a GitHub user) maintains it in SeemSeam/claude_codex_bridge, which has 3,550 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 6, 2026.
Source: SeemSeam/claude_codex_bridge on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.