phx-brief
Interactive briefing of a plan file — explains reasoning, schema decisions, component choices. Use when developers need to understand a plan before approving.
npx skills add oliver-kriska/claude-elixir-phoenix --skill phx-brief --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Plan Briefing 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. ## Why This Exists Plans answer "what to do" but bury "why." This skill bridges that gap with an interactive walkthrough. ## Usage ``` phx-brief # Latest plan phx-brief .claude/plans/user-auth/plan.md # Specific plan ``` ## Arguments - `$ARGUMENTS` = Path to plan file (optional, auto-detects latest) ## Mode Detection Read the plan file and determine mode from phase statuses: - **All phases `[PENDING]`** = Pre-work briefing (what WILL happen) - **Any phase `[COMPLETED]` or `[IN_PROGRESS]`** = Post-work briefing (what WAS done and why) ## Execution Flow ### Step 1: Locate and Load Plan 1. If `$ARGUMENTS` has a path, use it 2. Otherwise, find latest plan: Use Glob to find `.claude/plans/*/plan.md` and pick the most recent. 3. If no plan found, tell user and suggest `phx-plan` 4. Read the plan file ### Step 2: Load Supporting Artifacts Read what's available (don't fail if missing): - `.claude/plans/{slug}/summaries/consolidated.md` (research summary) - `.claude/plans/{slug}/scratchpad.md`
- Why This Exists
- Usage
- Arguments
- Mode Detection
- Execution Flow
- Step 1: Locate and Load Plan
- Step 2: Load Supporting Artifacts
- Step 3: Present Briefing Sections
- Section Flow (Pre-Work Mode)
- Section Flow (Post-Work Mode)
- Iron Laws
- Closing Message
- Integration
- Complex Plan Enhancement
What does the phx-brief skill do?
Interactive briefing of a plan file — explains reasoning, schema decisions, component choices. Use when developers need to understand a plan before approving.
How do I install it?
Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill phx-brief --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From oliver-kriska/claude-elixir-phoenix, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.