Agent skill

Plan

by oliver-kriska in oliver-kriska/claude-elixir-phoenix

Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban).

Install Plan

skills CLI

$ npx skills add oliver-kriska/claude-elixir-phoenix --skill plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/elixir-phoenix/skills/plan .claude/skills/plan && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "plan" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/plugins/elixir-phoenix/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

$skill-installer install https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/plugins/elixir-phoenix/skills/plan

Type 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.

skills CLI

$ npx skills add oliver-kriska/claude-elixir-phoenix --skill plan -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix plan --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/elixir-phoenix/skills/plan .agents/skills/plan && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "plan" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/plugins/elixir-phoenix/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.

skills CLI

$ npx skills add oliver-kriska/claude-elixir-phoenix --skill plan -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix plan --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/elixir-phoenix/skills/plan .cursor/skills/plan && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "plan" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/plugins/elixir-phoenix/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

$ gemini skills install https://github.com/oliver-kriska/claude-elixir-phoenix.git --path plugins/elixir-phoenix/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.

skills CLI

$ npx skills add oliver-kriska/claude-elixir-phoenix --skill plan -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix plan --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/elixir-phoenix/skills/plan .gemini/skills/plan && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "plan" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/plugins/elixir-phoenix/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.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix plan

Installs 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).

skills CLI

$ npx skills add oliver-kriska/claude-elixir-phoenix --skill plan -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/elixir-phoenix/skills/plan .github/skills/plan && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "plan" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/plugins/elixir-phoenix/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.

skills CLI

$ npx skills add oliver-kriska/claude-elixir-phoenix --skill plan -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix plan --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/elixir-phoenix/skills/plan .opencode/skills/plan && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "plan" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/plugins/elixir-phoenix/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: 565
Token cost: ~1.6k tokens
SKILL.md length: 668 words
Files: 7 (incl. references)
Skills in repo: 109
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban).

Works in 5 steps: Spawns Elixir specialist agents for… → Plans with [ecto], [liveview], [oban]… → Checks for Iron Law compliance in the plan → …
Designing interconnected systems
SKILL.md covers What Makes /phx:plan Different…, Usage, Arguments and Workflow, plus 5 more sections
Calls claude

What it does

Plan is an agent skill from oliver-kriska/claude-elixir-phoenix. Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban). Use when designing interconnected systems or converting review findings into tasks.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/agent-selection.md`, `references/breadboarding.md` and `references/complexity-detail.md`).

It sits in Backend & APIs, covering Code review, Authorization and RBAC and Webhooks. It works with Stripe and Elixir. The repository describes itself as: Claude Code plugin for Elixir/Phoenix/LiveView — 26 specialist agents, Iron Laws enforcement, and Tidewave MCP integration. Plan features with parallel research agents, execute… The licence is MIT.

When your agent uses it

Designing interconnected systems
Converting review findings into tasks

Example prompts

“/plan”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Spawns Elixir specialist agents for research
Plans with [ecto], [liveview], [oban] task routing
Checks for Iron Law compliance in the plan
Includes mix compile/format/credo/test verification
Understands Phoenix context boundaries

What it can do on your machine

Read from SKILL.md and the folder at commit 9767a82. 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
Shell commands in SKILL.md call:
- claude
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 1.6k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 51 tokens; SKILL.md has 668 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~51
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~12k

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 oliver-kriska/claude-elixir-phoenix at commit 9767a82, republished under its MIT licence (© oliver-kriska). 668 words, ~1,585 tokens.

Download SKILL.mdSave it as .claude/skills/plan/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.

name: plan
description: Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban). Use when designing interconnected systems or converting review findings into tasks.
effort: high
argument-hint: <feature description OR path to review/plan file>

Plan Elixir/Phoenix Feature

Plan a feature by spawning Elixir specialist agents, then output structured plan with checkboxes.

What Makes /phx:plan Different from /plan

Spawns Elixir specialist agents for research
Plans with [ecto], [liveview], [oban] task routing
Checks for Iron Law compliance in the plan
Includes mix compile/format/credo/test verification
Understands Phoenix context boundaries

Usage

/phx:plan Add user avatars with S3 upload
/phx:plan .claude/plans/notifications/reviews/notifications-review.md
/phx:plan Implement notifications --depth deep
/phx:plan .claude/plans/auth/plan.md --existing

Arguments

$ARGUMENTS = Feature description, review file, or existing plan
--depth quick|standard|deep = Planning depth (auto-detected)
--existing = Enhance an existing plan with deeper research

Workflow

Gather context — File path (skip to agents), brainstorm interview.md (skip clarification), clear description, or vague
Clarify if vague — Ask questions ONE at a time (skip if brainstorm interview.md exists with Status: COMPLETE)
Detect depth — Auto-detect quick/standard/deep
Runtime context (Tidewave) — Gather live schemas, routes, and warnings before spawning agents (direct path only — the research orchestrator gathers its own)
Spawn research — Selective, based on need. 0–2 agents: spawn directly in parallel. 3+ agents (broad multi-context feature): determine the effective maximum nesting depth. Use an explicit positive-integer CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH value first; when it is unset, inspect claude --version (the default is 1 in 2.1.217–2.1.218 and 3 in 2.1.219+). If the version is unavailable, conservatively use 1. At depth 3+, spawn ONE planning-orchestrator to run and compress the fan-out. At depth 1 or 2, keep orchestration in this main session: spawn the selected specialist agents directly, wait for them, then spawn phx:context-supervisor directly if compression is needed. Never spawn an orchestrator that cannot delegate. Read only the resulting digest and summaries/consolidated.md. If TaskCreate is in your tool list (never ToolSearch for it), create a task per spawn: TaskCreate({subject: "{Agent} research", activeForm: "Researching..."}), mark in_progress on spawn, completed when done
Wait for ALL agents — Do NOT proceed until all return "completed". NEVER write plan while any agent is still running
Breadboard (LiveView) — System map for multi-page features
Completeness check — required when planning from review
Split decision — One plan or multiple, concrete options
Generate plan — Checkboxes, phased tasks, code patterns. Also create plans/{slug}/scratchpad.md for decisions and dead-ends
Self-check (deep only) — Three questions in Risks section
Present and ask — STOP, show summary, let user decide

When planning from review: Every finding must appear in the plan — either as a task OR explicitly deferred by the user.

See ${CLAUDE_SKILL_DIR}/references/planning-workflow.md for detailed step-by-step.

Show full SKILL.md (282 more words)Show less

--existing Mode (Deepening)

Enhances an existing plan instead of creating a new one:

Load plan, search .claude/solutions/ for known risks
Spawn SPECIALIST agents (not Explore) for thin sections. Each agent writes to .claude/plans/{slug}/research/ and returns only a 500-word summary. Same agent selection rules
Wait for ALL agents (mark tasks completed as each finishes)
Add implementation detail, resolve spikes, add verification
Present diff summary — NEVER delete existing tasks

Iron Laws

NEVER auto-start /phx:work — Always present plan and ask
Research before assuming — Web-search unfamiliar tech
Spawn agents selectively — Only relevant, not all
NEVER write plan while agents still running
NEVER skip input findings — Every finding MUST have a task
Do NOT spawn hex-library-researcher for existing deps
Skip research when planning from review/investigation — When input is a review file or /phx:investigate output, the findings ARE the research. Do NOT spawn agents to re-discover what the review already found. Convert findings directly to plan tasks. (Confirmed: 56-session analysis showed same findings discovered 3-4x across review→investigate→plan phases, wasting ~96K tokens)

Integration with Workflow

text

/phx:plan {feature}  <-- YOU ARE HERE
       |
   /phx:plan --existing (optional enhancement)
       |
   ASK USER -> /phx:work .claude/plans/{feature}/plan.md
       |
/phx:review → /phx:compound

Notes

Plans saved to .claude/plans/{slug}/plan.md
Research reports in .claude/plans/{slug}/research/ can be deleted after

CRITICAL: After Writing the Plan

STOP. Do NOT proceed to implementation.

After writing .claude/plans/{slug}/plan.md:

Summarize: task count, phases, key decisions
Use AskUserQuestion with options:
- "Start in fresh session" (recommended for 5+ tasks)
- "Get a briefing" (/phx:brief — interactive walkthrough)
- "Start here"
- "Review or adjust the plan"
Wait for user response. Never auto-start work.

When user selects "Start in fresh session", print:

1. Run `/new` to start a fresh session
2. Then run one of:
   /phx:work .claude/plans/{slug}/plan.md
   /phx:full .claude/plans/{slug}/plan.md  (includes review + compound)

This is Iron Law #1. Violating it wastes user context.

References (DO NOT read — for human reference only)

${CLAUDE_SKILL_DIR}/references/planning-workflow.md — Detailed step-by-step
${CLAUDE_SKILL_DIR}/references/plan-template.md
${CLAUDE_SKILL_DIR}/references/complexity-detail.md
${CLAUDE_SKILL_DIR}/references/example-plan.md
${CLAUDE_SKILL_DIR}/references/agent-selection.md
${CLAUDE_SKILL_DIR}/references/breadboarding.md

Files

SKILL.md and 6 other files (references) in plugins/elixir-phoenix/skills/plan of oliver-kriska/claude-elixir-phoenix.

SKILL.md
references/agent-selection.md
references/breadboarding.md
references/complexity-detail.md
references/example-plan.md
references/plan-template.md
references/planning-workflow.md

Open the folder on GitHubat commit 9767a82

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.

Plan compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Plan this skilloliver-kriska/claude-elixir-phoenix	565	—	~1.6k	Automated safety check: Pass	MIT	4 days ago
Stripe Appsfossasia/eventyay	1.7k	1 repos	~3.6k	Automated safety check: Pass	Apache-2.0	today
Stripe Best Practiceskanchengw/cnllm	173	2 repos	~925	Automated safety check: Pass	Apache-2.0	3 mo ago
Cashier Stripe Developmentluadotsh/lua	343	1 repos	~1.2k	Automated safety check: Pass	MIT	18 days ago
API Route Patternsbybren-llc/safe-agentic-workflow	423	—	~1.6k	Automated safety check: Pass	MIT	2 mo ago
Stripe Best Practicesfossasia/eventyay	1.7k	1 repos	~1.7k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Stripe Apps
fossasia/eventyay
A skill your agent uses when building, modifying, or reviewing a Stripe App — or when the user describes something that implies one (e.g.
1.7k GitHub starsUsed in 1 repo~3.6k tokens
Backend & APIsAuto-check passed
Stripe Best Practices
kanchengw/cnllm
Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial…
173 GitHub starsUsed in 2 repos~925 tokens
Backend & APIsAuto-check passed
Cashier Stripe Development
luadotsh/lua
Handles Laravel Cashier Stripe integration including subscriptions, webhooks, Stripe Checkout, invoices, charges, refunds, trials, coupons, metered billing, and payment failure handling.
343 GitHub starsUsed in 1 repo~1.2k tokens
Backend & APIsAuto-check passed
API Route Patterns
bybren-llc/safe-agentic-workflow
API route implementation patterns with RLS, validation, and error handling. Use when creating API routes, implementing CRUD endpoints, adding server-side…
423 GitHub stars~1.6k tokensUpdated 2 mo ago
Backend & APIsAuto-check passed
Stripe Best Practices
fossasia/eventyay
Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents)…
1.7k GitHub starsUsed in 1 repo~1.7k tokens
Backend & APIsAuto-check passed
Stripe Integration
wshobson/agents
Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks.
40k GitHub starsUsed in 10 repos~1k tokens
Backend & APIsAuto-check passed

Questions about Plan

What does Plan do?

Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban). Plan is an agent skill from oliver-kriska/claude-elixir-phoenix. Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban).

When should I use Plan?

Plan fits situations like: designing interconnected systems; converting review findings into tasks.

How do I install Plan in Claude Code?

Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill plan -a claude-code`. Or copy the skill folder (plugins/elixir-phoenix/skills/plan in oliver-kriska/claude-elixir-phoenix) 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 oliver-kriska/claude-elixir-phoenix --skill plan -a codex`. Or copy the skill folder (plugins/elixir-phoenix/skills/plan in oliver-kriska/claude-elixir-phoenix) 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 oliver-kriska/claude-elixir-phoenix --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?

Going by SKILL.md and its folder, Plan needs the command-line tools its instructions call (claude).

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 1.6k tokens (SKILL.md is roughly 6.3k 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 10k tokens, read only when the agent opens those files.

What are the alternatives to Plan?

Skills that share tags, products or a category with Plan: Stripe Apps (fossasia/eventyay, 1.7k stars), Stripe Best Practices (kanchengw/cnllm, 173 stars), Cashier Stripe Development (luadotsh/lua, 343 stars) and API Route Patterns (bybren-llc/safe-agentic-workflow, 423 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Plan?

oliver-kriska (a GitHub user) maintains it in oliver-kriska/claude-elixir-phoenix, which has 565 GitHub stars. The repository holds 109 skills in this directory. The repository was last updated on October 5, 2026.

Source: oliver-kriska/claude-elixir-phoenix on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Plan

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Plan Elixir/Phoenix Feature

What Makes /phx:plan Different from /plan

Usage

Arguments

Workflow

--existing Mode (Deepening)

Iron Laws

Integration with Workflow

Notes

CRITICAL: After Writing the Plan

References (DO NOT read — for human reference only)

Files

Compare with similar skills

Similar skills

More from oliver-kriska/claude-elixir-phoenix

Related

Questions about Plan