Summarize document-heavy inputs such as memos, policies, PDFs, research notes, proposals, and multi-document packets. Use when users need key points, obligations, questions, and action implications from documents.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Classify the source: policy, proposal, memo, research, contract-like document, transcript, academic paper, operating document, or mixed packet.
Capture:
Keep source-backed summary separate from analysis or recommendation. Mark anything inferred.
Adapt format for executive, manager, student, legal/compliance reviewer, or team member.
State which sections deserve human review and why.
| Input | Required | Format |
|---|---|---|
| Document text or excerpt | Yes | Pasted text, extracted notes, OCR |
| Document type | Recommended | Proposal, policy, memo, research, etc. |
| Audience | Recommended | Executive, manager, student, team |
| Desired length | Optional | 5 bullets, one page, detailed brief |
| Focus area | Optional | Risks, obligations, actions, decisions |
## Document Summary - [Document Name]
### One-Line Takeaway
[Core point]
### Key Points
- [Point backed by source]
### Actions / Decisions
| Item | Owner | Deadline | Source Note |
|------|-------|----------|-------------|
### Risks / Caveats
- [Risk]
### Needs Human Review
- [Section or issue]
| Check | Question |
|---|---|
| Correctness | Are all summarized claims traceable to the document text? |
| Completeness | Are key points, actions, deadlines, risks, and review needs captured? |
| Context-fit | Does the summary match the audience and intended decision? |
| Consequence | What could be misread if the user relies only on the summary? |
Prompt: "Summarize this vendor proposal for an operations manager. Focus on deliverables, pricing assumptions, risks, and questions for the vendor."
Good pattern: "The proposal assumes customer data export is available by June 1. This is a dependency, not a confirmed commitment."
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Design rigorous A/B test plans with hypothesis, sample size calculation, Minimum Detectable Effect (MDE), randomization strategy, and decision rules. Includes guardrail metrics and rollout playbook. Use when planning product experiments, conversion optimization, or data-driven feature decisions.
The English summary is being prepared. Showing the original description.
Review REST and GraphQL API designs for consistency, usability, and best practices. Covers naming conventions, versioning strategy, error format, pagination, authentication patterns, and breaking change detection. Use when reviewing API specs, designing new APIs, or auditing existing endpoints.
The English summary is being prepared. Showing the original description.
Write Architecture Decision Records (ADRs) following the Michael Nygard format. Captures context, options considered, decision rationale, and consequences. Use when making technology choices, framework selections, or any architectural decision that future developers need to understand.
The English summary is being prepared. Showing the original description.
Assess organizational readiness for financial audits (internal or external). Map assertions to account balances, check evidence completeness, score readiness using a Red/Amber/Green framework, and generate a remediation timeline. Aligned with SOX, IFRS, and GAAP audit standards. Use before scheduled audits or when preparing for first-time compliance.
The English summary is being prepared. Showing the original description.
Design safe recurring Codex automations with clear prompts, outputs, schedules, and gating rules.
The English summary is being prepared. Showing the original description.
Refine Product Backlog Items to meet INVEST criteria. Write User Stories with Acceptance Criteria in Given/When/Then format, estimate with Story Points, and flag dependencies. Use before sprint planning when backlog items need grooming. Do not use to prioritize the backlog — that is the Product Owner's decision.
The English summary is being prepared. Showing the original description.