brief

# 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/bri...