# Brief

Interactive briefing of a plan file, explains reasoning, schema decisions, component...

- Repository: https://github.com/oliver-kriska/claude-elixir-phoenix (572 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add oliver-kriska/claude-elixir-phoenix --skill brief -g -a claude-code -y`
Codex: `npx skills add oliver-kriska/claude-elixir-phoenix --skill brief -g -a codex -y`
Cursor: `npx skills add oliver-kriska/claude-elixir-phoenix --skill brief -g -a cursor -y`
Gemini CLI: `npx skills add oliver-kriska/claude-elixir-phoenix --skill brief -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add oliver-kriska/claude-elixir-phoenix`

## Description

Interactive briefing of a plan file, explains reasoning, schema decisions, component choices. Use when developers need to understand a plan before approving.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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` (decisions, dead-ends)
- `.claude/plans/{slug}/progress.md` (work log, post-work only)

### Step 3: Present Briefing Sections

Present ONE section at a time, wrapped in the visual briefing block
(see `${CLAUDE_SKILL_DIR}/references/briefing-guide.md` Visual Formatting).

**The section MUST be emitted as visible response text BEFORE the
`AskUserQuestion` call.** Content composed only in thinking/reasoning
is invisible to the user, and the `question` field is too short to
carry it. If the user would see only a "Continue?" dialog, the section
was never shown. Write the ★ Briefing block as normal output first,
then ask:

The rest: https://github.com/oliver-kriska/claude-elixir-phoenix/blob/HEAD/plugins/elixir-phoenix/skills/brief/SKILL.md