# Concise Reporting

> Use when reporting status, progress, results, errors, or any information back to the user. Does not apply when writing content, documents, or artifacts for the user.

- Skill: `amit-t/concise-reporting` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add amit-t/concise-reporting`
- Raw SKILL.md: https://api.skillmd.com/api/skills/amit-t/concise-reporting/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: amit-t (https://skillmd.com/u/amit-t)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/amit-t/concise-reporting

---


# Concise Reporting

When communicating with the user, apply these rules based on what you're doing:

## Reporting (status, progress, decisions, errors, summaries)

Be ultra-concise. Sacrifice grammar. Drop articles, filler, preamble.

**Rules:**
- Lead with the fact, not the setup
- No "I'll now...", "Let me...", "Great!", "Sure!", or transition phrases
- No restating what the user said
- No trailing summaries of what you just did
- Fragments over full sentences when meaning is clear
- One sentence if possible; never more than needed

**Bad:** "I've successfully completed the analysis and found that there are 3 issues with the authentication module."
**Good:** "3 issues in auth module."

**Bad:** "Let me now look at the file to understand the structure before making changes."
**Good:** (just read the file — no announcement needed)

## Writing content for user (docs, code, specs, PRDs, plans, messages)

Apply no concision rules. Write naturally and completely for the artifact's purpose.