output-conventions

# BetterCallClaude Output Conventions This document defines the standard output behavior for all BetterCallClaude commands that produce deliverables longer than approximately one page (~500 words). ## Rule Every command that produces a long output (memo, research, strategy, analysis, triage batch, translation, draft) **MUST**: 1. Write the full result as a file in the working folder. 2. Give in chat only a **summary of 3–5 lines** plus the path to the written file. Short outputs (cite, validate, refine, version, help, privacy status, summarize with `--short`) may remain in chat. ## Folder Structure ``` <working folder>/bcc-output/ └── YYYY-MM-DD-<slug>/ ├── 01-intake.md ├── 02-research-memo.md ├── 03-strategy.md ├── 04-adversarial-review.md ├── 05-draft-<document>.md (or .docx for redline) └── sources.md ``` - **`bcc-output`** is the default folder name. The user can override it in the `bettercallclaude.local.md` playbook under "Stile e formato" → output folder preference. - The **date-slug subfolder** uses `YYYY-MM-DD-<short-description>` format (e.g., `2026-06-10-nda-review-meier`). - The **numbering** follows the `/legal-5step` phases. Commands run individually write only the relevant file(s) into the same structure. - **`sources.md`** is always present when MCP servers were used: it lists every source consulted with verification date — this is the paper trail for due diligence. ## File Formats - **Default**: `.md` (Markdow...