Communication

Explain changes, failures, options, and handoffs with clarity, evidence, and low noise.

Canonical skill profile. This page is generated from the repository contract. The linked SKILL.md remains the source of authority.

Jump to

• Overview
• When to use
• When not to use
• Core moves
• Expected output
• Verification
• Handoff signals
• Pairs well with
• Anti-patterns

View the canonical contract on GitHub.

Overview

Use this skill when technical work needs to be made legible for humans or for another agent.

When to Use

• status updates
• handoffs
• decision framing
• failure reporting

When NOT to Use

• to replace proof with storytelling
• to bury uncertainty under long prose

Core Moves

1. Lead with the main point.
2. Separate fact from interpretation when needed.
3. Name impact and trade-offs briefly.
4. Close with the next step or decision needed.

Optional Modules

• Decision frame — Add options, trade-offs, and a recommendation when a choice is needed.
• Failure report — Describe symptom, likely cause, and blocker shape.
• Handoff packet — Summarize boundary, ownership, and expected continuation.

Activation Triggers

• Use decision frame when multiple options remain.
• Use failure report when progress is blocked or risky.
• Use handoff packet when another owner must continue the work.

Expected Output

• clear status or decision note
• explicit trade-off or blocker
• next step

Verification

• A reader can understand the point in one pass.
• Evidence and recommendation are not blurred together.
• The next action is explicit.

Handoff Signals

• The note is primarily for another owner to continue the work.
• The change crosses team or specialty boundaries.

Pairs Well With

• workflow
• feature-planning
• api-design

Anti-patterns

• Writing chronologically instead of by importance.
• Using vague words instead of naming the decision.
• Reporting work without saying what should happen next.