LLM Council
gcpdev/llm-council-skill
Multi-LLM collaborative brainstorming and planning. An agent skill from gcpdev/llm-council-skill.
Write an implementation plan that leads with the decisions the user is most likely to change, and buries the mechanical work at the bottom.
Install Implementation Plan
$ npx skills add Neeeophytee/finding-unknowns-skills --skill implementation-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills implementation-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/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/implementation-plan .claude/skills/implementation-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 "implementation-plan" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/implementation-plan into .claude/skills/implementation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-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/Neeeophytee/finding-unknowns-skills/tree/main/skills/implementation-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 Neeeophytee/finding-unknowns-skills --skill implementation-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills implementation-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/implementation-plan .agents/skills/implementation-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 "implementation-plan" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/implementation-plan into .agents/skills/implementation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-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 Neeeophytee/finding-unknowns-skills --skill implementation-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills implementation-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/implementation-plan .cursor/skills/implementation-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 "implementation-plan" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/implementation-plan into .cursor/skills/implementation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-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/Neeeophytee/finding-unknowns-skills.git --path skills/implementation-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 Neeeophytee/finding-unknowns-skills --skill implementation-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Neeeophytee/finding-unknowns-skills implementation-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/implementation-plan .gemini/skills/implementation-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 "implementation-plan" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/implementation-plan into .gemini/skills/implementation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-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 Neeeophytee/finding-unknowns-skills implementation-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 Neeeophytee/finding-unknowns-skills --skill implementation-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/implementation-plan .github/skills/implementation-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 "implementation-plan" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/implementation-plan into .github/skills/implementation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-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 Neeeophytee/finding-unknowns-skills --skill implementation-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 Neeeophytee/finding-unknowns-skills implementation-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Neeeophytee/finding-unknowns-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/implementation-plan .opencode/skills/implementation-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 "implementation-plan" agent skill from https://github.com/Neeeophytee/finding-unknowns-skills/tree/main/skills/implementation-plan into .opencode/skills/implementation-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "implementation-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
implementation-plan- GitHub stars
- 343
- Token cost
- ~503 tokens
- SKILL.md length
- 272 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write an implementation plan that leads with the decisions the user is most likely to change, and buries the mechanical work at the bottom.
- Works in 6 steps: Open with a three-line summary: what is… → Section 1 — Decisions you'll probably… → Section 2 — Known unknowns and how the… → …
- Planning is requested before a build
- SKILL.md covers Steps and Guardrails
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Implementation Plan is an agent skill from Neeeophytee/finding-unknowns-skills. Write an implementation plan that leads with the decisions the user is most likely to change, and buries the mechanical work at the bottom. Use when planning is requested before a build, especially after brainstorming or an interview.
Its SKILL.md is about 500 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 and Brainstorming. The repository describes itself as: 14 installable skills for Claude Code, OpenAI Codex, and Hermes: find unknowns, clarify requirements, manage context, test assumptions, and verify bug fixes with regression… The licence is MIT.
When your agent uses it
- Planning is requested before a build
- Especially after brainstorming
Example prompts
- “/implementation-plan”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Open with a three-line summary: what is being built, the approach chosen, and the single riskiest assumption.
- Section 1 — Decisions you'll probably want to tweak. Data model changes, new type interfaces, API shapes, anything user-facing. For each…
- Section 2 — Known unknowns and how the plan absorbs them. Where ambiguity remains, state the default that will be taken and the signal…
- Section 3 — The mechanical work. Refactors, wiring, migrations, tests. Compress this; the user trusts you here and reviewing it is a waste…
- End with the review request: the 2-4 specific items you want a yes/no or a pick on before starting.
- If the plan is more than a screenful or the user prefers visual artifacts, offer it as a single self-contained HTML page — sections…
What it can do on your machine
Read from SKILL.md and the folder at commit ca5696a. 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.
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
Implementation Plan loads about 503 tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 272 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 Neeeophytee/finding-unknowns-skills at commit ca5696a, republished under its MIT licence (© Neeeophytee). 272 words, ~503 tokens.
Download SKILL.mdSave it as
.claude/skills/implementation-plan/SKILL.md (or your agent's skills folder).- name
- implementation-plan
- description
- Write an implementation plan that leads with the decisions the user is most likely to change, and buries the mechanical work at the bottom. Use when planning is requested before a build, especially after brainstorming or an interview.
Implementation plan
A plan's job is not to prove you thought of everything. It's to put the reversible-but-expensive decisions in front of the user while changing them is still free. Order the plan by likelihood-of-tweaking, not by build order.
Steps
- Open with a three-line summary: what is being built, the approach chosen, and the single riskiest assumption.
- Section 1 — Decisions you'll probably want to tweak. Data model changes, new type interfaces, API shapes, anything user-facing. For each: the choice made, one alternative considered, and what changing it later would cost.
- Section 2 — Known unknowns and how the plan absorbs them. Where ambiguity remains, state the default that will be taken and the signal that would trigger a pivot. A plan that admits its unknowns survives contact with the territory; one that doesn't just breaks quietly.
- Section 3 — The mechanical work. Refactors, wiring, migrations, tests. Compress this; the user trusts you here and reviewing it is a waste of their attention.
- End with the review request: the 2-4 specific items you want a yes/no or a pick on before starting.
- If the plan is more than a screenful or the user prefers visual artifacts, offer it as a single self-contained HTML page — sections collapsible, tweakable decisions pinned to the top.
Guardrails
- If a genuinely better approach appears mid-planning, present the pivot as its own decision — don't silently re-plan.
- Keep it reviewable in minutes. A plan too long to read gets skimmed, and skimmed plans hide bad decisions.
- The plan should leave room for improvisation during implementation; over-specified plans fail exactly where the territory disagrees with the map.
© Neeeophytee, 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/implementation-plan of Neeeophytee/finding-unknowns-skills.
Open the folder on GitHubat commit ca5696a
Compare with similar skills
Implementation 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 |
|---|---|---|---|---|---|---|
| Implementation Plan this skillNeeeophytee/finding-unknowns-skills | 343 | — | ~503 | Automated safety check: Pass | MIT | |
| LLM Councilgcpdev/llm-council-skill | 461 | 1 repos | ~1k | Automated safety check: Notes | MIT | |
| Brainstorming Before BuildingjnMetaCode/superpowers-zh | 8.3k | — | ~1.8k | Automated safety check: Pass | MIT | |
| CE BrainstormEveryInc/compound-engineering-plugin | 25k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Planmhmzdev/the-holy-quran-app | 889 | — | ~957 | Automated safety check: Pass | MIT | |
| Design Reviewxwtro0tk1t-cloud/harness | 265 | — | ~1.6k | Automated safety check: Pass | None |
Similar skills
Brainstorming Before Building
jnMetaCode/superpowers-zh
Turns a rough idea into an approved design before any code is written, sorting the request into spike, bounded or architectural and enforcing an approval gate.
CE Brainstorm
EveryInc/compound-engineering-plugin
Turns a vague or ambitious feature idea into a requirements-only plan through dialogue with you, sized to the work, before any code is written.
Plan
mhmzdev/the-holy-quran-app
Turn an idea or brainstorm into an actionable execution plan for The Holy Qur'an app with phases, file changes, and machine-checkable success criteria.
Design Review
xwtro0tk1t-cloud/harness
Dispatch an independent challenger agent to adversarially review a spec or implementation plan against the actual codebase.
Brainstorming
ed3dai/ed3d-plugins
A skill your agent uses when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning…
More from Neeeophytee/finding-unknowns-skills
All 14 skills in this repoAgent Interface Design
Neeeophytee/finding-unknowns-skills
Design tools, scripts, and CLIs that an agent will call, so the interface teaches its own use instead of a wall of prose and examples.
Assumption Test
Neeeophytee/finding-unknowns-skills
Test a consequential technical assumption with a small, falsifiable experiment before committing to an approach.
Blindspot Pass
Neeeophytee/finding-unknowns-skills
Surface the user's unknown unknowns before work starts. An agent skill from Neeeophytee/finding-unknowns-skills.
Brainstorm Prototypes
Neeeophytee/finding-unknowns-skills
Generate several genuinely different throwaway variations (designs, approaches, drafts) for the user to react to.
Change Quiz
Neeeophytee/finding-unknowns-skills
After a working session, produce a report on what changed plus a quiz the user must pass before merging.
Context Audit
Neeeophytee/finding-unknowns-skills
Audit the instructions an agent already carries — CLAUDE.md, AGENTS.md, skills, tool descriptions — for contradictions, over-constraint, and duplication, then propose a cut list.
Related
Categories
Questions about Implementation Plan
What does Implementation Plan do?
Write an implementation plan that leads with the decisions the user is most likely to change, and buries the mechanical work at the bottom. Implementation Plan is an agent skill from Neeeophytee/finding-unknowns-skills. Write an implementation plan that leads with the decisions the user is most likely to change, and buries the mechanical work at the bottom.
When should I use Implementation Plan?
Implementation Plan fits situations like: planning is requested before a build; especially after brainstorming.
How do I install Implementation Plan in Claude Code?
Run `npx skills add Neeeophytee/finding-unknowns-skills --skill implementation-plan -a claude-code`. Or copy the skill folder (skills/implementation-plan in Neeeophytee/finding-unknowns-skills) into .claude/skills/implementation-plan in your project. Claude Code loads it when a task matches its description.
How do I install Implementation Plan in Codex?
Run `npx skills add Neeeophytee/finding-unknowns-skills --skill implementation-plan -a codex`. Or copy the skill folder (skills/implementation-plan in Neeeophytee/finding-unknowns-skills) into .agents/skills/implementation-plan in your project. Codex loads it when a task matches its description.
Can I use Implementation 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 Neeeophytee/finding-unknowns-skills --skill implementation-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/implementation-plan, .gemini/skills/implementation-plan, .github/skills/implementation-plan and .opencode/skills/implementation-plan in your project.
What does Implementation Plan need to run?
SKILL.md names no scripts, command-line tools or credentials: Implementation Plan is instructions for the agent only.
Does Implementation 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 Implementation 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 Implementation Plan use?
Implementation 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 Implementation Plan use?
About 503 tokens (SKILL.md is roughly 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 Implementation Plan?
Skills that share tags, products or a category with Implementation Plan: LLM Council (gcpdev/llm-council-skill, 461 stars), Brainstorming Before Building (jnMetaCode/superpowers-zh, 8.3k stars), CE Brainstorm (EveryInc/compound-engineering-plugin, 25k stars) and Plan (mhmzdev/the-holy-quran-app, 889 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Implementation Plan?
Neeeophytee (a GitHub user) maintains it in Neeeophytee/finding-unknowns-skills, which has 343 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 28, 2026.
Source: Neeeophytee/finding-unknowns-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.