# Output Formatting

<!-- FLY-1138: full ruleset moved here from AGENTS.md, which keeps a condensed
     always-on digest plus a pointer. The digest carries the rules every
     response needs; this file carries the complete conventions. -->

Consistent formatting across all agent output. Follow these rules in every
response — session summaries, issue comments, status updates, and plans.

**Structure:**

- Lead with a one-line summary or status before detail.
- Use `##` for major sections, `###` for subsections. Never skip levels.
- Use bullet lists for 3+ related items. Use numbered lists only for sequences.
- One blank line between sections. No double-blank lines.

**Readability:**

- Keep paragraphs to 2-3 sentences. Break long blocks into scannable lists.
- Bold key terms and status labels on first use: **Completed**, **Blocked**, **Next**.
- Use inline code for file paths, commands, and identifiers: `project.md`, `/start-session`, `FLY-123`.
- Use code blocks with language tags for multi-line code or script examples.

**Consistency:**

- Status labels: **Completed**, **In Progress**, **Blocked**, **Next Up** (always bolded).
- Issue references: `FLY-123` format (uppercase prefix, hyphen, number).
- File paths: relative from project root, in backticks.
- Dates: `YYYY-MM-DD` format.
- No emoji in output unless the user explicitly requests it.

**Tables:**

- Use tables for structured comparisons (3+ items with 2+ attributes).
- Left-align text columns, keep headers short.