OpenSpec Guided Onboarding
Fission-AI/OpenSpec
Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.
Research the codebase and create an implementation plan following Propose/Justify/Recommend.
Install Plan
$ npx skills add cortex-tms/cortex-tms --skill plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cortex-tms/cortex-tms plan --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/cortex-tms/cortex-tms.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/plan .claude/skills/plan && 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" agent skill from https://github.com/cortex-tms/cortex-tms/tree/main/.claude/skills/plan into .claude/skills/plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan", 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/cortex-tms/cortex-tms/tree/main/.claude/skills/planType 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 cortex-tms/cortex-tms --skill plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cortex-tms/cortex-tms plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cortex-tms/cortex-tms.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/plan .agents/skills/plan && 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" agent skill from https://github.com/cortex-tms/cortex-tms/tree/main/.claude/skills/plan into .agents/skills/plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan", 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 cortex-tms/cortex-tms --skill plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cortex-tms/cortex-tms plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cortex-tms/cortex-tms.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/plan .cursor/skills/plan && 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" agent skill from https://github.com/cortex-tms/cortex-tms/tree/main/.claude/skills/plan into .cursor/skills/plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan", 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/cortex-tms/cortex-tms.git --path .claude/skills/plan--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 cortex-tms/cortex-tms --skill plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cortex-tms/cortex-tms plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cortex-tms/cortex-tms.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/plan .gemini/skills/plan && 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" agent skill from https://github.com/cortex-tms/cortex-tms/tree/main/.claude/skills/plan into .gemini/skills/plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan", 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 cortex-tms/cortex-tms planInstalls 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 cortex-tms/cortex-tms --skill plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cortex-tms/cortex-tms.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/plan .github/skills/plan && 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" agent skill from https://github.com/cortex-tms/cortex-tms/tree/main/.claude/skills/plan into .github/skills/plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan", 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 cortex-tms/cortex-tms --skill plan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cortex-tms/cortex-tms plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cortex-tms/cortex-tms.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/plan .opencode/skills/plan && 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" agent skill from https://github.com/cortex-tms/cortex-tms/tree/main/.claude/skills/plan into .opencode/skills/plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan", 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- GitHub stars
- 180
- Token cost
- ~388 tokens
- SKILL.md length
- 166 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
Research the codebase and create an implementation plan following Propose/Justify/Recommend.
- Works in 7 steps: Enter plan mode — use EnterPlanMode… → Research first — read relevant source… → Follow Propose/Justify/Recommend → …
- Tasks that involve Planning
- SKILL.md covers Rules, You CANNOT and Arguments
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Plan is an agent skill from cortex-tms/cortex-tms. Research the codebase and create an implementation plan following Propose/Justify/Recommend. Use this before any feature, fix, or refactor.
Its SKILL.md is about 390 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 Agent Workflows, covering Planning. The repository describes itself as: The Universal AI-Optimized Project Boilerplate. A Tiered Memory System (TMS) designed to maximize AI agent performance. Includes an interactive CLI tool and a high-signal… The licence is MIT.
When your agent uses it
- Tasks that involve Planning
Example prompts
- “/plan”
Requirements
- Pre-approved tools (allowed-tools): Read, Glob, Grep, WebSearch, WebFetch, Edit, Write, Task, EnterPlanMode, ExitPlanMode, AskUserQuestion
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Enter plan mode — use EnterPlanMode before doing anything else
- Research first — read relevant source files, tests, docs, and patterns before proposing anything
- Follow Propose/Justify/Recommend
- Write the plan — update NEXT-TASKS.md with a sprint checklist (- [ ] items) and acceptance criteria
- Update task files if needed
- Exit plan mode — present the plan for user approval via ExitPlanMode
- STOP — do not write any code. Wait for the user to approve or give feedback.
What it can do on your machine
Read from SKILL.md and the folder at commit 2e7c79e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGlobGrepWebSearchWebFetchEditWriteTaskEnterPlanModeExitPlanMode
…and 1 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
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 loads about 388 tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 166 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 cortex-tms/cortex-tms at commit 2e7c79e, republished under its MIT licence (© cortex-tms). 166 words, ~388 tokens.
Download SKILL.mdSave it as
.claude/skills/plan/SKILL.md (or your agent's skills folder).- name
- plan
- description
- Research the codebase and create an implementation plan following Propose/Justify/Recommend. Use this before any feature, fix, or refactor.
- allowed-tools
- Read, Glob, Grep, WebSearch, WebFetch, Edit, Write, Task, EnterPlanMode, ExitPlanMode, AskUserQuestion
- disable-model-invocation
- true
Plan
You are planning a feature for Cortex TMS. Enter plan mode immediately.
Rules
- Enter plan mode — use EnterPlanMode before doing anything else
- Research first — read relevant source files, tests, docs, and patterns before proposing anything
- Follow Propose/Justify/Recommend:
- Propose: What you will build and how
- Justify: Why this approach, with evidence from the codebase
- Recommend: One clear recommendation — then stop and wait
- Write the plan — update NEXT-TASKS.md with a sprint checklist (- [ ] items) and acceptance criteria
- Update task files if needed:
- Move tasks between NEXT-TASKS.md and FUTURE-ENHANCEMENTS.md
- Update status markers in FUTURE-ENHANCEMENTS.md
- Archive completed sprints to docs/archive/
- Exit plan mode — present the plan for user approval via ExitPlanMode
- STOP — do not write any code. Wait for the user to approve or give feedback.
You CANNOT
- Touch any file in src/, bin/, templates/
- Edit README.md, package.json, or any config file
- Write code, tests, or build artifacts
- Run build, test, or lint commands
- Proceed to implementation without explicit user approval
Arguments
$ARGUMENTS
© cortex-tms, 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 .claude/skills/plan of cortex-tms/cortex-tms.
Open the folder on GitHubat commit 2e7c79e
Compare with similar skills
Plan 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 this skillcortex-tms/cortex-tms | 180 | — | ~388 | Automated safety check: Pass | MIT | |
| OpenSpec Guided OnboardingFission-AI/OpenSpec | 71k | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Paseo Committeegetpaseo/paseo | 20k | 1 repos | ~496 | Automated safety check: Pass | Custom licence | |
| Improvefossasia/eventyay-interpretation | 1.6k | 10 repos | ~3.7k | Automated safety check: Warn | MIT | |
| Implementation Plan Creatortailcallhq/forgecode | 7.6k | 1 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Plan Previewu-ichi/reviewable-html-workbench | 298 | 1 repos | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
Paseo Committee
getpaseo/paseo
Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.
Improve
fossasia/eventyay-interpretation
Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute.
Implementation Plan Creator
tailcallhq/forgecode
Writes a structured Markdown implementation plan with checkbox tasks, verification criteria and risks, then checks it with a validation script; no code changes.
Plan Preview
u-ichi/reviewable-html-workbench
Plan Mode の <proposedplan を出す直前に、計画の段階・依存関係・検証観点を一時HTMLで視覚確認したい時に使う agent-internal skill。Use this agent-internal skill to create a temporary HTML preview for a plan just before presenting…
PRP Loop: Autonomous Pipeline
Wirasm/prp
Runs a detached, resumable loop that plans, implements, opens a PR, reviews and fixes a feature across headless CLI sessions until the review is clean.
More from cortex-tms/cortex-tms
Release
cortex-tms/cortex-tms
Guide through the Cortex TMS release process — version bump, changelog, sync, tag, publish.
Implement
cortex-tms/cortex-tms
Implement an approved plan. An agent skill from cortex-tms/cortex-tms.
New Command
cortex-tms/cortex-tms
Scaffold a new CLI command for Cortex TMS following the existing codebase patterns.
Sync
cortex-tms/cortex-tms
Synchronize task files and source-of-truth documents. An agent skill from cortex-tms/cortex-tms.
Validate
cortex-tms/cortex-tms
Run the full quality gate — tests, lint, build, and cortex-tms validate --strict.
Related
Categories
Questions about Plan
What does Plan do?
Research the codebase and create an implementation plan following Propose/Justify/Recommend. Plan is an agent skill from cortex-tms/cortex-tms. Research the codebase and create an implementation plan following Propose/Justify/Recommend.
When should I use Plan?
Plan fits situations like: tasks that involve Planning.
How do I install Plan in Claude Code?
Run `npx skills add cortex-tms/cortex-tms --skill plan -a claude-code`. Or copy the skill folder (.claude/skills/plan in cortex-tms/cortex-tms) into .claude/skills/plan in your project. Claude Code loads it when a task matches its description.
How do I install Plan in Codex?
Run `npx skills add cortex-tms/cortex-tms --skill plan -a codex`. Or copy the skill folder (.claude/skills/plan in cortex-tms/cortex-tms) into .agents/skills/plan in your project. Codex loads it when a task matches its description.
Can I use Plan 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 cortex-tms/cortex-tms --skill plan -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, .gemini/skills/plan, .github/skills/plan and .opencode/skills/plan in your project.
What does Plan need to run?
SKILL.md names no scripts, command-line tools or credentials: Plan is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, WebSearch, WebFetch, Edit, Write, Task, EnterPlanMode, ExitPlanMode, AskUserQuestion.
Does Plan 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 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 use?
Plan 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 use?
About 388 tokens (SKILL.md is roughly 1.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?
Skills that share tags, products or a category with Plan: OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 71k stars), Paseo Committee (getpaseo/paseo, 20k stars), Improve (fossasia/eventyay-interpretation, 1.6k stars) and Implementation Plan Creator (tailcallhq/forgecode, 7.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Plan?
cortex-tms (a GitHub organization) maintains it in cortex-tms/cortex-tms, which has 180 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 5, 2026.
Source: cortex-tms/cortex-tms on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.