phx-brief

Presents interactive section-by-section briefings of Elixir Phoenix plan files.

537|38|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/oliver-kriska/claude-elixir-phoenix --skill phx-brief
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phx-brief
Source: https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/targets/codex/skills/phx-brief
Command: npx skills add https://github.com/oliver-kriska/claude-elixir-phoenix --skill phx-brief

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Plan documents explain what to do but bury the reasoning behind decisions, forcing developers to read entire files to understand why choices were made. This Skill delivers an interactive walkthrough that explains a plan's rationale, decisions, and solution shape in 1-2 minutes.

Core Features & Use Cases

  • Interactive Section Briefings: Presents one section at a time (What We're Building, Key Decisions, Solution Shape, Risks & Confidence) with user-controlled pacing via continue/stop prompts.
  • Dual Mode Detection: Automatically switches between pre-work briefing (what will happen) and post-work briefing (what was done and why) based on phase completion statuses.
  • Artifact-Grounded Explanations: Pulls rationale from plan.md, scratchpad.md, summaries, and progress.md to explain trade-offs, rejected alternatives, and dead-ends.
  • Use Case: After generating an implementation plan for a Phoenix LiveView feature, run the briefing to understand the key architectural decisions and risks before starting execution, or after completion to review lessons learned.

Quick Start

Ask the assistant to brief the latest plan in .claude/plans or a specific plan file path to receive an interactive section-by-section walkthrough.

Frequently Asked Questions about phx-brief

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get a quick summary of an implementation plan?

Run the briefing with no arguments to auto-detect the latest plan in .claude/plans, or pass a specific plan file path. The skill presents one section at a time covering scope, decisions, solution shape, and risks, letting you stop at any point.

How does the plan briefing decide between pre-work and post-work mode?

It reads the plan file and checks phase statuses. If all phases are marked PENDING it runs a pre-work briefing about what will happen; if any phase is COMPLETED or IN_PROGRESS it switches to a post-work briefing covering what was built and lessons learned.

What files does the plan briefing read besides plan.md?

It optionally reads consolidated.md research summaries, scratchpad.md for decisions and dead-ends, and progress.md for work logs within the plan's directory. Missing files do not cause failure; the briefing falls back to the plan document alone.

Can the briefing execute the plan or start implementation work?

No. The briefing is strictly read-only and never executes plan tasks or launches work without an explicit user request. It only explains the plan and suggests follow-up commands like phx-work or phx-compound at the end.

When does the briefing suggest a visual diagram of the plan?

It suggests visual rendering when a plan has 5 or more phases with cross-dependencies, 4 or more key decisions, or a System Map with 3 or more pages. The suggestion is optional and never blocks the terminal briefing flow.