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.
Interactively investigate a request, compare approaches, and write the selected implementation plan to a supplied Markdown path.
Install Plan
$ npx skills add HazAT/pi-config --skill plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install HazAT/pi-config 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/HazAT/pi-config.git skills-src && mkdir -p .claude/skills && cp -r skills-src/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/HazAT/pi-config/tree/main/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/HazAT/pi-config/tree/main/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 HazAT/pi-config --skill plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install HazAT/pi-config plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HazAT/pi-config.git skills-src && mkdir -p .agents/skills && cp -r skills-src/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/HazAT/pi-config/tree/main/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 HazAT/pi-config --skill plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install HazAT/pi-config plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HazAT/pi-config.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/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/HazAT/pi-config/tree/main/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/HazAT/pi-config.git --path 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 HazAT/pi-config --skill plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install HazAT/pi-config plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HazAT/pi-config.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/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/HazAT/pi-config/tree/main/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 HazAT/pi-config 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 HazAT/pi-config --skill plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/HazAT/pi-config.git skills-src && mkdir -p .github/skills && cp -r skills-src/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/HazAT/pi-config/tree/main/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 HazAT/pi-config --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 HazAT/pi-config plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HazAT/pi-config.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/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/HazAT/pi-config/tree/main/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
- 451
- Token cost
- ~528 tokens
- SKILL.md length
- 176 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
Interactively investigate a request, compare approaches, and write the selected implementation plan to a supplied Markdown path.
- Works in 6 steps: Investigate: inspect repository… → Confirm intent: summarize the requested… → Clarify: ask only questions whose… → …
- Tasks that involve Planning
- SKILL.md covers Workflow and Plan Format
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Plan is an agent skill from HazAT/pi-config. Interactively investigate a request, compare approaches, and write the selected implementation plan to a supplied Markdown path. Use for planning, brainstorming, or exact /plan.
Its SKILL.md is about 530 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: My personal pi coding agent configuration - skills and extensions. The licence is MIT.
When your agent uses it
- Tasks that involve Planning
- Tasks that involve Brainstorming
Example prompts
- “/plan”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Investigate: inspect repository instructions, Git state, relevant files, tests, and existing patterns. Ground claims in what you read.
- Confirm intent: summarize the requested outcome, implicit requirements, boundaries, and the most important success condition. Ask for…
- Clarify: ask only questions whose answers materially change the design. Resolve observable behavior, edge cases, quality level, and…
- Compare approaches: present 2–3 materially different options with tradeoffs, risks, effort, and a recommendation.
- Select: ask the user to choose or approve an approach. Do not write the plan before this checkpoint.
- Write: after selection, resolve routine details from evidence and write only the absolute plan path supplied by the caller. Stop.
What it can do on your machine
Read from SKILL.md and the folder at commit 655acd4. 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 loads about 528 tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 176 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 HazAT/pi-config at commit 655acd4, republished under its MIT licence (© HazAT). 176 words, ~528 tokens.
Download SKILL.mdSave it as
.claude/skills/plan/SKILL.md (or your agent's skills folder).- name
- plan
- description
- Interactively investigate a request, compare approaches, and write the selected implementation plan to a supplied Markdown path. Use for planning, brainstorming, or exact /plan.
Plan
Plan in the current chat. Do not implement, create todos, review, or launch source-writing agents.
Workflow
- Investigate: inspect repository instructions, Git state, relevant files, tests, and existing patterns. Ground claims in what you read.
- Confirm intent: summarize the requested outcome, implicit requirements, boundaries, and the most important success condition. Ask for corrections.
- Clarify: ask only questions whose answers materially change the design. Resolve observable behavior, edge cases, quality level, and explicit exclusions.
- Compare approaches: present 2–3 materially different options with tradeoffs, risks, effort, and a recommendation.
- Select: ask the user to choose or approve an approach. Do not write the plan before this checkpoint.
- Write: after selection, resolve routine details from evidence and write only the absolute plan path supplied by the caller. Stop.
Keep each interactive turn focused. Investigate facts instead of asking the user to provide facts available in the checkout.
Plan Format
# [Plan name]
**Status:** Ready
**Request:** [one sentence]
**Selected approach:** [one sentence]
## Intent
## Scope
### In scope
- ...
### Out of scope
- ...
## Acceptance Criteria
- [ ] ISC-1: [binary, observable criterion]
- [ ] ISC-2: ...
## Repository Evidence
- `path:line` — [relevant fact or convention]
## Approaches Considered
### Selected: [name]
[Why it best fits]
### Rejected: [name]
[Tradeoff that ruled it out]
## Implementation
1. [ordered change with files/components]
## Verification
- `[command]` — [what it proves]
## Assumptions and Risks
- [assumption or failure mode] — [mitigation or accepted risk]Use objective acceptance criteria and name important wrong approaches. Do not create a sidecar directory, run record, todo file, review file, or custom state.
© HazAT, 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/plan of HazAT/pi-config.
Open the folder on GitHubat commit 655acd4
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 skillHazAT/pi-config | 451 | — | ~528 | Automated safety check: Pass | MIT | |
| Brainstorming Before BuildingjnMetaCode/superpowers-zh | 8.3k | — | ~1.8k | Automated safety check: Pass | MIT | |
| LLM Councilgcpdev/llm-council-skill | 461 | — | ~1k | Automated safety check: Notes | 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
LLM Council
gcpdev/llm-council-skill
Multi-LLM collaborative brainstorming and planning. An agent skill from gcpdev/llm-council-skill.
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 HazAT/pi-config
All 10 skills in this repoSession Reader
HazAT/pi-config
Efficiently read and analyze pi agent session JSONL files. An agent skill from HazAT/pi-config.
Pi Extension Development
HazAT/pi-config
Defines the local standard for standalone Pi extension repositories.
Superconductor
HazAT/pi-config
Operates the super.engineering/Superconductor sc CLI for app-managed agents, teams, sessions, layouts, worktrees, and review threads.
Review
HazAT/pi-config
Coordinate a model-diverse local code review, automatically repair actionable findings with sequential workers, and re-review to a final verdict.
Setup Superconductor Project
HazAT/pi-config
Configures a repository for super.engineering with repo-owned worktree setup and development-server scripts.
Worker
HazAT/pi-config
Implement one todo or review-fix task supplied by a coordinator, verify it, create one focused commit, and report evidence through the current Superconductor session.
Related
Categories
Questions about Plan
What does Plan do?
Interactively investigate a request, compare approaches, and write the selected implementation plan to a supplied Markdown path. Plan is an agent skill from HazAT/pi-config. Interactively investigate a request, compare approaches, and write the selected implementation plan to a supplied Markdown path.
When should I use Plan?
Plan fits situations like: tasks that involve Planning; tasks that involve Brainstorming.
How do I install Plan in Claude Code?
Run `npx skills add HazAT/pi-config --skill plan -a claude-code`. Or copy the skill folder (skills/plan in HazAT/pi-config) 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 HazAT/pi-config --skill plan -a codex`. Or copy the skill folder (skills/plan in HazAT/pi-config) 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 HazAT/pi-config --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.
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 528 tokens (SKILL.md is roughly 2.1k 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: Brainstorming Before Building (jnMetaCode/superpowers-zh, 8.3k stars), LLM Council (gcpdev/llm-council-skill, 461 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 Plan?
HazAT (a GitHub user) maintains it in HazAT/pi-config, which has 451 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on August 25, 2026.
Source: HazAT/pi-config on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.