Draft

---
description: Write a short-form artifact (PR description, commit message, changelog entry, copy snippet).
argument-hint: <kind>: <topic>  (e.g. pr: council v2, copy: error empty state)
allowed-tools: Read, Write, Glob, Grep
---

You are running **draft**. One-shot writing. Goal: produce the artifact, no implementation.

Input: **$ARGUMENTS**

## Steps

1. **Identify kind.** Common: `pr`, `commit`, `changelog`, `copy`, `email-internal`, `release-notes`.

2. **Gather context.**
   - `pr` → `git log main..HEAD --oneline` and `git diff main...HEAD --stat`.
   - `commit` → `git status` + `git diff --staged`.
   - `changelog` → `git log <last-tag>..HEAD --oneline`.
   - `copy` → read `lib/data/banned-jargon.json` first; cite the rule applied.

3. **Write.**
   - **PR title** ≤ 70 chars.
   - **PR body** has `## Summary` (1–3 bullets) and `## Test plan` (markdown checklist).
   - **Commit message** is one line ≤ 72 chars + optional body separated by blank line. Imperative voice.
   - **Copy** must pass `lib/data/banned-jargon.json` and `lib/data/impeccable-rules.json` IMP-UXW-* rules. Show the result alongside which rules you checked.

4. **Verify.**
   - For PR/commit: do NOT include emojis unless requested.
   - For copy: read it back as if you're the ICP (CPA, M&A advisor, age 35–55). Does it sound like a peer or an Instagram ad? Iterate until peer.

## Output

The artifact, ready to paste. Brief preamble only if the user needs to know what assumptions you made.

## Boundaries

- Do NOT push, commit, or open the PR.
- Do NOT edit code.
- Do NOT use jargon from the banned list.

## Suggested next

`/ship` if this was the PR description for an outgoing change.