# Exception Note

> Write an order exception note explaining why an order is held and what has to happen next. Use this skill when asked for an exception note, a hold explanation, or a blocker write-up for an order.

- Skill: `langchain-samples/exception-note` (Agent Skill)
- Install (CLI): `npx get-skill add langchain-samples/exception-note`
- Raw SKILL.md: https://api.skillmd.com/api/skills/langchain-samples/exception-note/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: langchain-samples (https://skillmd.com/u/langchain-samples)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/langchain-samples/exception-note

---


# Exception Note Skill

The order desk works a queue. Assume the reader has thirty seconds and needs to know who does what next.

## Format

- **Headline**: one bold line naming the order and what is blocking it
- **Order**: the order number and the facts you were given — flag anything missing
- **Blockers**: one bullet per blocker, each with a citation where the requirement comes from
- **Actions Taken**: what you checked, and explicitly what you did *not* do
- **Next Step**: the concrete action required, specific enough to execute
- **Owner**: one line naming the team or role that has to act next

## Tone

- Factual and neutral — this note may be read by the account, not just the desk
- Distinguish a confirmed requirement from a plausible one; say which you have
- Never assert coverage, coding, or reimbursement outcomes as settled

## Length

- Under 250 words before the Sources section
- Bullets over paragraphs

