rb:brief

Brief the Work

Read the supplied artifact, then explain what matters in a concise summary.

Purpose

Briefs provide high-signal explanations for busy developers. After planning, working, or reviewing, use /rb:brief to understand:

• What's happening
• What matters most
• What to do next

Brief Process

START ──▶ READ ARTIFACT(S) ──▶ EXTRACT SIGNAL ──▶ SYNTHESIZE
                                                │
                                                ▼
                                         STRUCTURE BRIEF
                                                │
                                                ▼
                                              OUTPUT

Brief Structure

1. One-Line Summary

The goal in 10-15 words.

2. The Moving Parts (3-5 bullets)

What changed or will change:

• Files modified/created
• New components
• Dependencies added
• Configuration changes

3. Risk Areas

What could go wrong:

• Breaking changes
• Security implications
• Performance concerns
• Deployment risks

4. Next Action

What to do now:

• Start implementation
• Address review findings
• Run specific commands
• Make decisions

Brief by Artifact Type

Briefing a Plan

Read: plan.md

Extract:

• Goal from overview
• Phases and task count
• Risk areas from risk table
• Recommended next step

Format:

## Plan Brief: {Feature Name}

**Goal**: {one line}

**Scope**: {N} tasks across {N} phases
- Phase 1: {summary}
- Phase 2: {summary}
...

**Key Risks**:
- {risk} ({severity})
- {risk} ({severity})

**Next Step**: {action}

Briefing Work Results

Read: plan.md (updated), changed files

Extract:

• What was completed
• What was blocked
• Files that changed
• Verification results

Format:

## Work Brief: {Feature Name}

**Completed**: {N}/{N} tasks

**Changes**:
- Created: {files}
- Modified: {files}
- Deleted: {files}

**Blockers**: {N}
- {blocker description}

**Verification**: {status}
- Tests: {pass/fail}
- Linter: {clean/issues}

**Next Step**: {action}