Codexkit Report Summarizer

Procedure

1. Identify the document's purpose and core thesis.
2. Extract key findings, data points, and conclusions.
3. Note any recommendations, action items, or decisions embedded in the source.
4. Structure the summary: what (findings) → so what (implications) → now what (actions).
5. Calibrate detail level to the target audience.
6. Flag anything notable that was omitted from the summary.

Output

• structured summary (format per user preference)
• key findings list
• recommended actions or decisions (if present in source)
• "what was left out" note (for transparency)

Definition of done

• summary can be read in under 2 minutes
• no critical points from the source are missing
• the reader can decide whether to read the full document based on the summary
• action items are preserved with owners and timelines if mentioned

Examples

• "Summarize this 40-page market research report into a one-page executive brief."
• "Extract the top 5 findings from the quarterly budget review and list recommended actions."
• "Create a 3-bullet pre-read summary of the vendor evaluation document for tomorrow's meeting."
• "Condense this audit report into key risks and remediation priorities."

Quality Criteria

• All claims reference specific frameworks, standards, or quantifiable data
• Content matches the stated audience's expertise level
• Recommendations are actionable — each includes a concrete next step
• No unsupported assertions or generic filler language

Verification (4C)

Edge Cases

• Conflicting frameworks — State which framework takes precedence and why. Document the trade-off explicitly.
• Rapidly changing domain — Note information currency date. Flag sections likely to need updates.
• Audience has mixed expertise levels — Provide a glossary and mark advanced sections as optional.

Changelog

• v1.0.0 — Initial release