菜单
Interactive briefing of a plan file — explains reasoning, schema decisions, component choices. Use when developers need to understand a plan before approving.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/majiayu000/claude-skill-registry --skill phx-brief命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | phx:brief |
| description | Interactive briefing of a plan file — explains reasoning, schema decisions, component choices. Use when developers need to understand a plan before approving. |
| effort | low |
| argument-hint | ["path to plan file"] |
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.