Show Me Your Work Decision Log
cursor/plugins
Keeps a TSV decision log for long or unattended agent runs, one row per decision with what, why, evidence and result, so a reviewer can check the work later.
A skill your agent uses when running claudikins-kernel:outline, brainstorming implementation approaches, gathering requirements iteratively, structuring complex technical plans, or facing analysis…
Install Brain Jam Plan
$ npx skills add povvo/claudikins-kernel --skill brain-jam-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install povvo/claudikins-kernel brain-jam-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/povvo/claudikins-kernel.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/brain-jam-plan .claude/skills/brain-jam-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 "brain-jam-plan" agent skill from https://github.com/povvo/claudikins-kernel/tree/main/skills/brain-jam-plan into .claude/skills/brain-jam-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brain-jam-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/povvo/claudikins-kernel/tree/main/skills/brain-jam-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 povvo/claudikins-kernel --skill brain-jam-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install povvo/claudikins-kernel brain-jam-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/povvo/claudikins-kernel.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/brain-jam-plan .agents/skills/brain-jam-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 "brain-jam-plan" agent skill from https://github.com/povvo/claudikins-kernel/tree/main/skills/brain-jam-plan into .agents/skills/brain-jam-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brain-jam-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 povvo/claudikins-kernel --skill brain-jam-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install povvo/claudikins-kernel brain-jam-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/povvo/claudikins-kernel.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/brain-jam-plan .cursor/skills/brain-jam-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 "brain-jam-plan" agent skill from https://github.com/povvo/claudikins-kernel/tree/main/skills/brain-jam-plan into .cursor/skills/brain-jam-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brain-jam-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/povvo/claudikins-kernel.git --path skills/brain-jam-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 povvo/claudikins-kernel --skill brain-jam-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install povvo/claudikins-kernel brain-jam-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/povvo/claudikins-kernel.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/brain-jam-plan .gemini/skills/brain-jam-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 "brain-jam-plan" agent skill from https://github.com/povvo/claudikins-kernel/tree/main/skills/brain-jam-plan into .gemini/skills/brain-jam-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brain-jam-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 povvo/claudikins-kernel brain-jam-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 povvo/claudikins-kernel --skill brain-jam-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/povvo/claudikins-kernel.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/brain-jam-plan .github/skills/brain-jam-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 "brain-jam-plan" agent skill from https://github.com/povvo/claudikins-kernel/tree/main/skills/brain-jam-plan into .github/skills/brain-jam-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brain-jam-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 povvo/claudikins-kernel --skill brain-jam-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 povvo/claudikins-kernel brain-jam-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/povvo/claudikins-kernel.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/brain-jam-plan .opencode/skills/brain-jam-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 "brain-jam-plan" agent skill from https://github.com/povvo/claudikins-kernel/tree/main/skills/brain-jam-plan into .opencode/skills/brain-jam-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "brain-jam-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
brain-jam-plan- GitHub stars
- 128
- Token cost
- ~2k tokens
- SKILL.md length
- 691 words
- Files
- 10 (incl. references)
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when running claudikins-kernel:outline, brainstorming implementation approaches, gathering requirements iteratively, structuring complex technical plans, or facing analysis…
- Works in 4 steps: Requirements Gathering → Context Building → Approach Generation → …
- Running claudikins-kernel:outline
- SKILL.md covers Overview, Trigger Symptoms, The Brain-Jam Process and Non-Negotiables, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Brain Jam Plan is an agent skill from povvo/claudikins-kernel. Use when running claudikins-kernel:outline, brainstorming implementation approaches, gathering requirements iteratively, structuring complex technical plans, or facing analysis paralysis with too many options — provides iterative human-in-the-loop planning with explicit checkpoints and trade-off presentation
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `references/approach-conflict-resolution.md`, `references/approach-template.md` and `references/iteration-limits.md`).
It sits in Agent Workflows, covering Brainstorming and Human-in-the-loop approvals. The repository describes itself as: SRE thinking applied to Claude Code, based on Boris Cherny's Q&A. It enforces a strict 4-stage pipeline with gates between each step. You literally cannot skip verification. You… The licence is MIT.
When your agent uses it
- Running claudikins-kernel:outline
- Brainstorming implementation approaches
- Gathering requirements iteratively
- Structuring complex technical plans
Example prompts
- “/brain-jam-plan”
Requirements
- Pre-approved tools (allowed-tools): Read, Grep, Glob, TodoWrite, WebSearch, Skill, mcp__plugin_claudikins-tool-executor_tool-executor__search_tools, mcp__plugin_claudikins-tool-executor_tool-executor__get_tool_schema, mcp__plugin_claudikins-tool-executor_tool-executor__execute_code
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 8b626a4. 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:
ReadGrepGlobTodoWriteWebSearchSkillmcp__plugin_claudikins-tool-executor_tool-executor__search_toolsmcp__plugin_claudikins-tool-executor_tool-executor__get_tool_schemamcp__plugin_claudikins-tool-executor_tool-executor__execute_code
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
Brain Jam Plan loads about 2k tokens when it runs, and up to ~13k if it reads all its reference files. Until then it costs about 81 tokens; SKILL.md has 691 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 povvo/claudikins-kernel at commit 8b626a4, republished under its MIT licence (© povvo). 691 words, ~2,005 tokens.
Download SKILL.mdSave it as
.claude/skills/brain-jam-plan/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.- name
- brain-jam-plan
- description
- Use when running claudikins-kernel:outline, brainstorming implementation approaches, gathering requirements iteratively, structuring complex technical plans, or facing analysis paralysis with too many options — provides iterative human-in-the-loop planning with explicit checkpoints and trade-off presentation
- allowed-tools
- Read, Grep, Glob, TodoWrite, WebSearch, Skill, mcp__plugin_claudikins-tool-executor_tool-executor__search_tools, mcp__plugin_claudikins-tool-executor_tool-executor__get_tool_schema, mcp__plugin_claudikins-tool-executor_tool-executor__execute_code
Brain-Jam Planning Methodology
Overview
Planning is an iterative conversation, not a production line. The human stays in the loop at every phase.
"Go back and forth with Claude until I like its plan. A good plan is really important." — Boris
Core principle: Understand before solving. Ask before assuming. Recommend but let user decide.
Trigger Symptoms
Use this skill when:
- Running the
claudikins-kernel:outlinecommand - Requirements are unclear or keep changing
- Multiple valid approaches exist and you can't choose
- User wants involvement in decisions (not just receive a plan)
- Previous plans failed due to missed requirements
- Scope creep is a concern
- You're tempted to just start coding without a plan
The Brain-Jam Process
Phase 1: Requirements Gathering
One question at a time. Wait for the answer.
Key questions to answer:
- What problem are we solving?
- What does success look like?
- What constraints exist?
- What's explicitly OUT of scope?
Use AskUserQuestion with specific options — never open-ended unless necessary.
Phase 2: Context Building
Before proposing solutions, understand the landscape:
- What exists already in the codebase?
- What patterns should we follow?
- What dependencies apply?
- What has been tried before?
Phase 3: Approach Generation
Generate 2-3 distinct approaches. Each must include:
| Element | Purpose |
|---|---|
| Summary | 1-2 sentence overview |
| Pros | Clear benefits |
| Cons | Honest trade-offs |
| Effort | low / medium / high |
| Risk | low / medium / high |
Always recommend one with reasoning. See approach-template.md.
Phase 4: Section-by-Section Drafting
Draft one section at a time. Get approval before moving on.
Never batch approvals — each checkpoint is a chance to course-correct.
Non-Negotiables
These rules have no exceptions:
One question at a time.
- Not "let me ask a few things"
- Not "quick questions"
- One question. Wait. Process answer. Next question.
Always present 2-3 approaches.
- Not "here's what I recommend"
- Not "the obvious choice is..."
- Present options. Recommend one. User decides.
Checkpoint before proceeding.
- Not "I'll assume that's fine"
- Not "continuing unless you object"
- Explicit approval. "Does this look right?" Wait for yes.
Never fabricate research.
- Not "based on my understanding"
- Not "typically in codebases like this"
- If you don't know, research or ask. Don't invent.
Plan Quality Criteria
A good plan has:
- Clear problem statement
- Explicit scope boundaries (IN and OUT)
- Measurable success criteria
- Task breakdown with dependencies
- Risk identification and mitigations
- Verification checklist
See plan-checklist.md for full verification.
Output Format
Plans must include machine-readable task markers for claudikins-kernel:execute compatibility:
<!-- EXECUTION_TASKS_START -->
| # | Task | Files | Deps | Batch |
| --- | ------------- | -------------------- | ---- | ----- |
| 1 | Create schema | prisma/schema.prisma | - | 1 |
| 2 | Add service | src/services/user.ts | 1 | 1 |
<!-- EXECUTION_TASKS_END -->See plan-format.md for complete structure.
Anti-Patterns
Don't do these:
- Batching multiple questions together
- Proposing solutions before understanding requirements
- Presenting only one approach
- Skipping the verification checklist
- Continuing without explicit approval at checkpoints
- Fabricating research findings when data is sparse
Show full SKILL.md (263 more words)Show less
Rationalizations to Resist
Agents under pressure find excuses. These are all violations:
| Excuse | Reality |
|---|---|
| "I'll batch questions to save time" | Batching causes missed requirements. One at a time. |
| "User knows what they want, skip brain-jam" | Assumptions cause rework. Gather requirements explicitly. |
| "I'll propose solutions while gathering requirements" | Solutions bias requirements. Understand first, solve second. |
| "User implied preference, don't need alternatives" | Implied ≠ decided. Always present 2-3 options. |
| "This is simple, don't need checkpoints" | Simple plans still fail. Checkpoints catch errors early. |
| "I already know the right approach" | Your confidence isn't approval. User decides. |
| "Alternatives will confuse them" | Confusion means requirements are unclear. Clarify. |
| "I'll get approval for multiple sections at once" | Batched approvals hide problems. One section, one checkpoint. |
All of these mean: Follow the methodology. No shortcuts.
Red Flags — STOP and Reassess
If you're thinking any of these, you're about to violate the methodology:
- "Let me just quickly..."
- "The user probably wants..."
- "This is obvious, I don't need to ask"
- "I'll come back to requirements later"
- "One approach is clearly best"
- "They already approved something similar"
- "Checkpoints slow things down"
- "I know what they meant"
All of these mean: STOP. Return to methodology. Ask, don't assume.
Edge Case Handling
| Situation | Reference |
|---|---|
| Context collapse mid-plan | session-collapse-recovery.md |
| Endless iteration loop | iteration-limits.md |
| Research taking too long | research-timeouts.md |
| Approaches contradict each other | approach-conflict-resolution.md |
| User abandons plan | plan-abandonment-cleanup.md |
| Requirements keep changing | requirement-stability.md |
References
- plan-checklist.md — Verification checklist
- approach-template.md — How to present options
- plan-format.md — Output structure for claudikins-kernel:execute
- iteration-limits.md — When to stop iterating
- requirement-stability.md — Scope creep detection
- approach-conflict-resolution.md — Conflicting approaches
- session-collapse-recovery.md — Context collapse handling
- research-timeouts.md — Timeout handling
- plan-abandonment-cleanup.md — Cleanup procedures
© povvo, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 9 other files (references) in skills/brain-jam-plan of povvo/claudikins-kernel.
- SKILL.md
- references/approach-conflict-resolution.md
- references/approach-template.md
- references/iteration-limits.md
- references/plan-abandonment-cleanup.md
- references/plan-checklist.md
- references/plan-format.md
- references/requirement-stability.md
- references/research-timeouts.md
- references/session-collapse-recovery.md
Open the folder on GitHubat commit 8b626a4
Compare with similar skills
Brain Jam 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 |
|---|---|---|---|---|---|---|
| Brain Jam Plan this skillpovvo/claudikins-kernel | 128 | — | ~2k | Automated safety check: Pass | MIT | |
| Show Me Your Work Decision Logcursor/plugins | 10k | 8 repos | ~1.6k | Automated safety check: Pass | None | |
| Brainstormingxpinjection/test-driven-spring-boot | 112 | 54 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Darwin Skill Optimizeralchaincyf/darwin-skill | 6.2k | 1 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Typesafe AIOpenAgentsInc/openagents | 455 | 9 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Yao Meta Skillyaojingang/yao-meta-skill | 2.7k | — | ~768 | Automated safety check: Pass | MIT |
Similar skills
- Official
Brainstorming
xpinjection/test-driven-spring-boot
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior.
Darwin Skill Optimizer
alchaincyf/darwin-skill
Scores SKILL.md files on a nine-dimension rubric, then improves them in a keep-or-revert loop with independent judge agents, test prompts, git history and human checkpoints.
Typesafe AI
OpenAgentsInc/openagents
Build AI-powered software with TypeSafe: small units of AI intelligence you can use like programming primitives.
Yao Meta Skill
yaojingang/yao-meta-skill
Create, improve, or evaluate an existing skill from workflows, prompts, SOPs, scripts.
Loop Constraints Enforcer
cobusgreyling/loop-engineering
Loads a project's loop-constraints.md before any other action and blocks pushes, edits or merges that violate the rules it defines.
More from povvo/claudikins-kernel
Git Workflow
povvo/claudikins-kernel
A skill your agent uses when running claudikins-kernel:execute, decomposing plans into tasks, setting up two-stage review, deciding batch sizes, or handling stuck agents — enforces isolation…
Shipping Methodology
povvo/claudikins-kernel
A skill your agent uses when running claudikins-kernel:ship, preparing PRs, writing changelogs, deciding merge strategy, or handling CI failures — enforces GRFP-style iterative approval, code…
Strict Enforcement
povvo/claudikins-kernel
A skill your agent uses when running claudikins-kernel:verify, checking implementation quality, deciding pass/fail verdicts, or enforcing cross-command gates — requires actual evidence of code…
Related
Categories
Questions about Brain Jam Plan
What does Brain Jam Plan do?
A skill your agent uses when running claudikins-kernel:outline, brainstorming implementation approaches, gathering requirements iteratively, structuring complex technical plans, or facing analysis…. Brain Jam Plan is an agent skill from povvo/claudikins-kernel.
When should I use Brain Jam Plan?
Brain Jam Plan fits situations like: running claudikins-kernel:outline; brainstorming implementation approaches; gathering requirements iteratively; structuring complex technical plans.
How do I install Brain Jam Plan in Claude Code?
Run `npx skills add povvo/claudikins-kernel --skill brain-jam-plan -a claude-code`. Or copy the skill folder (skills/brain-jam-plan in povvo/claudikins-kernel) into .claude/skills/brain-jam-plan in your project. Claude Code loads it when a task matches its description.
How do I install Brain Jam Plan in Codex?
Run `npx skills add povvo/claudikins-kernel --skill brain-jam-plan -a codex`. Or copy the skill folder (skills/brain-jam-plan in povvo/claudikins-kernel) into .agents/skills/brain-jam-plan in your project. Codex loads it when a task matches its description.
Can I use Brain Jam 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 povvo/claudikins-kernel --skill brain-jam-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/brain-jam-plan, .gemini/skills/brain-jam-plan, .github/skills/brain-jam-plan and .opencode/skills/brain-jam-plan in your project.
What does Brain Jam Plan need to run?
SKILL.md names no scripts, command-line tools or credentials: Brain Jam Plan is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Glob, TodoWrite, WebSearch, Skill, mcp__plugin_claudikins-tool-executor_tool-executor__search_tools, mcp__plugin_claudikins-tool-executor_tool-executor__get_tool_schema, mcp__plugin_claudikins-tool-executor_tool-executor__execute_code.
Does Brain Jam 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 Brain Jam 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 Brain Jam Plan use?
Brain Jam 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 Brain Jam Plan use?
About 2k tokens (SKILL.md is roughly 8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.
What are the alternatives to Brain Jam Plan?
Skills that share tags, products or a category with Brain Jam Plan: Show Me Your Work Decision Log (cursor/plugins, 10k stars), Brainstorming (xpinjection/test-driven-spring-boot, 112 stars), Darwin Skill Optimizer (alchaincyf/darwin-skill, 6.2k stars) and Typesafe AI (OpenAgentsInc/openagents, 455 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Brain Jam Plan?
povvo (a GitHub user) maintains it in povvo/claudikins-kernel, which has 128 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on April 22, 2026.
Source: povvo/claudikins-kernel on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.