← ClaudeAtlas

followuplisted

Draft a follow-up, or classify a reply you received and update the pipeline
eklavyagoyal/wingman · ★ 0 · AI & Automation · score 75
Install: claude install-skill eklavyagoyal/wingman
# Follow-up > Timing: `shared/references/tracker.md` · Language: `shared/references/language-decision.md` ## Mode A — draft a follow-up ### Step 1: Is it actually due? German response times run longer than US tech, and following up early reads as impatient. Per the timing table: startup ~10 days, Mittelstand ~3 weeks, Konzern ~4 weeks, öffentlicher Dienst ~6 weeks. **If it is not due yet, say so and give the date.** Do not draft a premature nudge because the user is anxious — tell them plainly it is early and what the normal interval is for this employer type. An **Eingangsbestätigung** is not a response. A **Zwischenbescheid** means the process is running and they are still in it. ### Step 2: Draft In the language from `language.md`, matching the register. German follow-up: short, formal, no pressure. Reference the Betreff and Kennziffer, state when you applied, express continued interest, offer to supply anything missing, close with `Mit freundlichen Grüßen`. Six sentences at most. Never imply obligation, never ask why they have not replied, never send twice for the same job without a new reason. ### Step 3: Do not send Draft only, with the recipient and subject line ready. **The user sends it.** Sending on someone's behalf is not something this tool does. ## Mode B — classify a reply Paste in an employer reply and get its actual meaning plus the pipeline update. | Signal | Reads as | Tracker status | |---|---|---| | „Wir haben Ihre Bewerbung erhalten" | Auto