Inbox Reply Triage

Organize message backlog into prioritized actions with draft replies, defer/archive/delegate suggestions, and a same-day processing plan.

Convert message backlog into a priority queue with reply, defer, archive, or delegate drafts.

When to Use

Use this skill when you need a repeatable workflow for: inbox, email, reply draft, triage. It is designed for professionals, freelancers, creators, students who need practical structure, not vague advice.

What This Skill Does

The assistant should help the user move through a structured workflow:

1. Sort — Sort messages by urgency, importance, and effort
2. Draft — Draft concise replies in the user's tone
3. Suggest — Suggest defer/archive/delegate decisions
4. Create — Create a same-day processing plan

How to Run the Workflow

1. Intake

Ask concise questions to understand the user's situation, constraints, timeline, desired outcome, and any non-negotiables. If the user provides messy notes, first summarize what is known and what is missing.

2. Structure

Transform the input into a clear working artifact: tables, checklists, scripts, decision memos, timelines, or SOP sections as appropriate. Prefer concrete fields such as owner, due date, next action, evidence, risk, status, and follow-up.

3. Draft Useful Output

Provide ready-to-edit drafts in a calm, professional tone. Include short and long versions when communication is involved. For checklists, mark must-do vs optional items.

4. Verification

Before finalizing, add a verification pass: facts to confirm, missing information, assumptions made, and places where the user should check official or authoritative sources.

Suggested Output Formats

• Quick summary
• Action table
• Checklist
• Timeline
• Message/script draft
• Risks and assumptions
• Next 3 concrete steps

Example Prompts

• "Help me organize this messy situation into a clear plan: ..."
• "Turn these notes into a checklist and message draft: ..."
• "What am I missing before I take action?"
• "Make this more concise, polite, and firm."

Safety and Boundaries

Users must verify facts, recipients, tone, and attachments before sending.

Do not invent facts, policies, prices, laws, deadlines, or commitments. When uncertain, clearly label assumptions and tell the user what to verify.