follow-up-detector

Skill: Follow-Up Detector

Use this skill to keep follow-ups from slipping through the cracks and to stop defer from turning into a hidden backlog.

Objective

Classify thread posture into:

• waiting_on_kyle
• waiting_on_them
• closed_loop
• ambiguous

Then recommend the safest visibility action.

Required Inputs

• sender(s)
• latest message summary
• last outbound message summary if available
• thread age
• last response timestamp
• whether a question or commitment is open
• any deadline or date references

Output Format

{
  "thread_id": "...",
  "status": "waiting_on_kyle|waiting_on_them|closed_loop|ambiguous",
  "confidence": 0.0,
  "reasoning_summary": ["..."],
  "recommended_visibility_action": "leave_visible|label_waiting|digest_only|escalate",
  "recommended_label": "[Superhuman]/AI/Waiting|[Superhuman]/AI/Review|none",
  "human_review_required": false
}

Rules

waiting_on_kyle

• the other party asked a direct question
• Kyle committed to send something and has not
• a deadline is approaching and the ball is clearly in Kyle's court

Recommended action:

• leave_visible or label_waiting

waiting_on_them

• Kyle already replied with a clear next step or question
• someone else owes the response
• no imminent deadline requires more action right now

Recommended action:

• label_waiting or digest_only

closed_loop

• no open asks remain
• the thread naturally ended
• the latest state is informational only

Recommended action:

• digest_only

ambiguous

• unclear who owes the next step
• multiple asks crossed
• latest message changed the frame
• thread is sensitive or risky

Recommended action:

• escalate

Guardrails

• if the thread is high-stakes, emotional, legal, finance, security, fundraising, press, or personnel, prefer ambiguous + escalate
• do not assume a thread is closed just because it is old
• time alone is not enough; rely on who owes what