Ad Deepen
alexandremendoncaalvaro/CorridorKey-Runtime
Surface deepening opportunities in the codebase using the Ousterhout/Feathers vocabulary from WORKFLOW §8 (Module / Interface / Depth / Seam / Adapter / Leverage / Locality).
Interview-driven planning methodology that produces implementation-ready plans.
Install Planning
$ npx skills add markmdev/meridian --skill planning -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install markmdev/meridian planning --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/markmdev/meridian.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/planning .claude/skills/planning && 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 "planning" agent skill from https://github.com/markmdev/meridian/tree/main/skills/planning into .claude/skills/planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning", 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/markmdev/meridian/tree/main/skills/planningType 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 markmdev/meridian --skill planning -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install markmdev/meridian planning --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/markmdev/meridian.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/planning .agents/skills/planning && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "planning" agent skill from https://github.com/markmdev/meridian/tree/main/skills/planning into .agents/skills/planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning", 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 markmdev/meridian --skill planning -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install markmdev/meridian planning --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/markmdev/meridian.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/planning .cursor/skills/planning && 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 "planning" agent skill from https://github.com/markmdev/meridian/tree/main/skills/planning into .cursor/skills/planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning", 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/markmdev/meridian.git --path skills/planning--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 markmdev/meridian --skill planning -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install markmdev/meridian planning --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/markmdev/meridian.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/planning .gemini/skills/planning && 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 "planning" agent skill from https://github.com/markmdev/meridian/tree/main/skills/planning into .gemini/skills/planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning", 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 markmdev/meridian planningInstalls 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 markmdev/meridian --skill planning -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/markmdev/meridian.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/planning .github/skills/planning && 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 "planning" agent skill from https://github.com/markmdev/meridian/tree/main/skills/planning into .github/skills/planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning", 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 markmdev/meridian --skill planning -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install markmdev/meridian planning --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/markmdev/meridian.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/planning .opencode/skills/planning && 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 "planning" agent skill from https://github.com/markmdev/meridian/tree/main/skills/planning into .opencode/skills/planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "planning", 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
planning- GitHub stars
- 186
- Token cost
- ~1.3k tokens
- SKILL.md length
- 627 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- None found
At a glance
Interview-driven planning methodology that produces implementation-ready plans.
- Architecture changes
- SKILL.md covers Verbatim Requirements, The Core Loop, Interviewing and Exploring the Codebase, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Any non-trivial implementation work
What it does
Planning is an agent skill from markmdev/meridian. Interview-driven planning methodology that produces implementation-ready plans. Always use this skill INSTEAD of EnterPlanMode — it provides structured interviewing (20-40 clarifying questions), exhaustive parallel codebase exploration (5-15 Explore agents), verbatim requirements capture, and automated plan validation via plan-reviewer (must score 9+). Use for new features, refactoring, architecture changes, migrations, or any non-trivial implementation work.
Its SKILL.md is about 1.3k 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 Development, covering Requirements gathering and Refactoring. The repository describes itself as: Zero-config Claude Code setup with enforced task scaffolding, structured memory, persistent context after compaction, plug-in code standards, optional TDD mode, and zero behavior…
When your agent uses it
- Architecture changes
- Any non-trivial implementation work
Example prompts
- “/planning”
What it can do on your machine
Read from SKILL.md and the folder at commit d9b8775. 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
Planning loads about 1.3k tokens when it runs. Until then it costs about 118 tokens; SKILL.md has 627 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 627 words (~1,309 tokens).
“Good plans prove you understand the problem. Size matches complexity — a rename might be 20 lines, a complex feature might be 500.”
- name
- planning
Files
Just SKILL.md in skills/planning of markmdev/meridian.
Open the folder on GitHubat commit d9b8775
Compare with similar skills
Planning 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 |
|---|---|---|---|---|---|---|
| Planning this skillmarkmdev/meridian | 186 | — | ~1.3k | Automated safety check: Pass | None | |
| Ad Deepenalexandremendoncaalvaro/CorridorKey-Runtime | 755 | 1 repos | ~2k | Automated safety check: Pass | Custom licence | |
| Absolute Workmaddhruv/absolute | 218 | — | ~5.3k | Automated safety check: Pass | MIT | |
| Grilling Ideasopsmill/infrahub | 531 | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Migrate Core Code to Submodulestinyhumansai/openhuman | 42k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Vibe Coding PartnershareAI-lab/Kode-CLI | 5.2k | — | ~5.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Absolute Work
maddhruv/absolute
End-to-end, phase-gated SDLC for AI coding agents: relentless design interview → reviewed spec → dependency-graphed task board → safe-wave TDD execution → verification → converge.
Grilling Ideas
opsmill/infrahub
Stress-tests a fuzzy or vague feature idea before any PRD, spec, or ticket is written.
Migrate Core Code to Submodules
tinyhumansai/openhuman
Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.
Vibe Coding Partner
shareAI-lab/Kode-CLI
Gives an agent a set of working rules for any development task: understand first, surface decisions, verify results, and load deeper reference files per scenario.
Filescope MCP
admica/FileScopeMCP
Codebase intelligence via FileScopeMCP — symbol lookup, dependency mapping, importance ranking, and semantic search.
More from markmdev/meridian
Add Frontmatter
markmdev/meridian
Scan all .md files in the project and add or fix YAML frontmatter (summary + readwhen) so they can be discovered by context routers like Reflex.
Error Audit
markmdev/meridian
Audit code for silent error swallowing, fallbacks to degraded alternatives, backwards compatibility shims, and UI that fails to show errors to the user.
Observability Audit
markmdev/meridian
Audit code for observability gaps — debug logs left in, errors caught without being logged, missing context on log entries, untracked slow operations.
UX States Audit
markmdev/meridian
Audit UI code for missing loading states, empty states, and error states.
Create Docs
markmdev/meridian
Create or update .meridian/docs/ knowledge files for a module or directory.
Related
Categories
Questions about Planning
What does Planning do?
Interview-driven planning methodology that produces implementation-ready plans. Planning is an agent skill from markmdev/meridian. Interview-driven planning methodology that produces implementation-ready plans.
When should I use Planning?
Planning fits situations like: architecture changes; any non-trivial implementation work.
How do I install Planning in Claude Code?
Run `npx skills add markmdev/meridian --skill planning -a claude-code`. Or copy the skill folder (skills/planning in markmdev/meridian) into .claude/skills/planning in your project. Claude Code loads it when a task matches its description.
How do I install Planning in Codex?
Run `npx skills add markmdev/meridian --skill planning -a codex`. Or copy the skill folder (skills/planning in markmdev/meridian) into .agents/skills/planning in your project. Codex loads it when a task matches its description.
Can I use Planning 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 markmdev/meridian --skill planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/planning, .gemini/skills/planning, .github/skills/planning and .opencode/skills/planning in your project.
What does Planning need to run?
SKILL.md names no scripts, command-line tools or credentials: Planning is instructions for the agent only.
Does Planning 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 Planning 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 Planning use?
No licence was found for Planning or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Planning use?
About 1.3k tokens (SKILL.md is roughly 5.2k 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 Planning?
Skills that share tags, products or a category with Planning: Ad Deepen (alexandremendoncaalvaro/CorridorKey-Runtime, 755 stars), Absolute Work (maddhruv/absolute, 218 stars), Grilling Ideas (opsmill/infrahub, 531 stars) and Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Planning?
markmdev (a GitHub user) maintains it in markmdev/meridian, which has 186 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on March 11, 2026.
Source: markmdev/meridian on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.