executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
email-triageClassify a batch of emails into action categories (reply now, reply later, archive, delete, unsubscribe) and surface unsubscribe candidates. Use after a busy week, running inbox zero, or triaging email overload.
Independent GitHub snapshot · Automated classification · Original documentation governs
Classify a batch of email subjects + senders into action buckets and surface inbox-zero candidates.
email, inbox, inbox zero, triage, unsubscribe, mailing list, mailbox, gmail, outlook, productivity
Before triaging, confirm these inputs. If any is unknown or vague, ASK — do not assume:
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
subject,sender,snippet,received_atpython scripts/email_classifier.py inbox.csvassets/gmail_filter_template.md) so future similar emails route automaticallyTime Estimate: 30-45 minutes for a busy week.
Time Estimate: 15 minutes per pass.
references/inbox_zero_method.mdTime Estimate: 1-2 hours one-time; then 20 min/week to maintain.
Classifies email rows into action buckets using rule-based pattern matching on sender domain, subject line, and snippet.
python scripts/email_classifier.py inbox.csv
python scripts/email_classifier.py inbox.csv --json
Action buckets:
references/inbox_zero_method.md — Method, daily routine, common pitfallsassets/gmail_filter_template.md — Common Gmail filter recipes for the action buckets above