From elixir-phoenix
Provides interactive walkthroughs of Claude Code plan files, explaining reasoning, schema decisions, component choices, and phases. Use for quick plan understanding before or after work.
How this skill is triggered — by the user, by Claude, or both
Slash command
/elixir-phoenix:briefThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Interactive walkthrough of a plan's reasoning, decisions, and solution
Interactive walkthrough of a plan's reasoning, decisions, and solution shape. Designed for developers who need to understand a plan in 1-2 minutes instead of reading the full document.
Plans answer "what to do" but bury "why." This skill bridges that gap with an interactive walkthrough.
/phx:brief # Latest plan
/phx:brief .claude/plans/user-auth/plan.md # Specific plan
$ARGUMENTS = Path to plan file (optional, auto-detects latest)Read the plan file and determine mode from phase statuses:
[PENDING] = Pre-work briefing (what WILL happen)[COMPLETED] or [IN_PROGRESS] = Post-work briefing
(what WAS done and why)If $ARGUMENTS has a path, use it
Otherwise, find latest plan:
Use Glob to find .claude/plans/*/plan.md and pick the most recent.
If no plan found, tell user and suggest /phx:plan
Read the plan file
Read what's available (don't fail if missing):
.claude/plans/{slug}/summaries/consolidated.md (research summary).claude/plans/{slug}/scratchpad.md (decisions, dead-ends).claude/plans/{slug}/progress.md (work log, post-work only)Present ONE section at a time, wrapped in the visual briefing block
(see ${CLAUDE_SKILL_DIR}/references/briefing-guide.md Visual Formatting). After each
section, use AskUserQuestion with options:
| # | Title | Source |
|---|---|---|
| 1 | What We're Building | Summary + Scope |
| 2 | Key Decisions | Technical Decisions + scratchpad rationale |
| 3 | Solution Shape | Phases overview + Data Model |
| 4 | Risks & Confidence | Risks table + unknowns/spikes |
| # | Title | Source |
|---|---|---|
| 1 | What Was Built | Summary + completion status |
| 2 | Key Decisions & Why | Technical Decisions + scratchpad |
| 3 | How It Was Built | Phases with implementation notes |
| 4 | Lessons & Patterns | Risks encountered + patterns used |
See ${CLAUDE_SKILL_DIR}/references/briefing-guide.md for section content templates.
/phx:work without explicit user requestAfter final section (or when user stops):
That's the briefing! For full details, see:
{plan_path}
Ready to proceed? Try `/phx:work {plan_path}` to start execution.
Post-work variant:
That's what was built! For full details, see:
{plan_path}
Consider `/phx:compound` to capture key learnings for future reference.
/phx:plan --> /phx:brief (optional) --> /phx:work --> /phx:brief (optional)
create understand before execute understand after
For plans with 5+ phases or 4+ key decisions, consider suggesting
visual rendering after Section 3. See
${CLAUDE_SKILL_DIR}/references/visual-explainer.md for thresholds and commands.
npx claudepluginhub oliver-kriska/claude-elixir-phoenix --plugin elixir-phoenixReplicates Claude Code plan mode in read-only fashion: explores codebase, designs changes, gets user approval, then writes plan to .claude/plans/<slug>.md without executing. Triggers on 'plan only' phrases.
Loads plan-review.md to review project plans, architecture decisions, and implementation strategies before coding begins.
Generates a single-file HTML plan brief for non-engineer stakeholders before implementation. Searches project memory for past decisions and patterns, then renders understanding, options, risks, and acceptance criteria.