report-format

To format an owner-facing report, start with a one-line conclusion, follow with 2–4 evidence bullets containing inline sources, note uncertainties, and add a section for open questions to ensure concise, readable communication.

A conclusion-first report structure begins with a rapid one-line summary, followed by sequentially readable evidence, inline sources, and uncertainties, ensuring project reviews and incident post-mortems remain free of agent chatter.

Write source-backed reports by linking evidence inline and enforcing a strict conclusion-first narrative flow, keeping communication focused strictly on results and sources while eliminating unnecessary agent chatter.

Yes, the report format enforces YAML frontmatter with name and description in SKILL.md, and emits structured metadata fields including dependencies, components, and toxicity indicators alongside optional scripts and assets.

Yes, you can apply this reporting format to scenarios like product updates and incident post-mortems, ensuring final reports remain concise, source-backed, and structured for sequential readability across various project communications.

The concise format limits narrative depth by restricting evidence to 2–4 inline source bullets and a one-line conclusion, requiring uncertainties and open questions to be documented separately rather than fully explored in the main text.