ai-secretary

Use the BLUF (Bottom Line Up Front) pattern: state your ask in the first line, then add context. Tag subject lines with prefixes like [ACTION] or [DECISION] so recipients know what is needed, and keep emails under five sentences.

Audit each recurring meeting by asking what decision it produces and whether it generated action items recently. Convert status updates to async Slack threads, reduce frequency for low-output meetings, and cancel meetings with no recent decisions.

No, calendar access is read-first by design. The assistant reads your schedule and proposes changes, but never creates, modifies, or deletes an event until you explicitly confirm the action.

Share the meeting notes or email thread and each action item is extracted in the format: owner, task, and due date. Items missing an owner or date are flagged so you can fill in the gap before they are tracked.

Use chat for quick questions, real-time collaboration, and internal FYIs. Use email for formal requests, approvals, external communication, and anything needing a paper trail or detailed attachments.

It is not designed for cold outreach emails, marketing email sequences, or project management artifacts like PRDs. Those scenarios are better handled by dedicated skills such as cold-email-writer or product-manager.