follow-up-radarlisted

# Follow-up Radar Most outreach dies not because the first email failed but because the follow-up never went out. This skill finds the follow-ups you owe and puts the drafts in front of you. It reports first and it never sends anything. ## Step 0: Load the radar config (once) Look for a `follow-up-radar.config.md` file in the project root. If it does not exist, ask for the values below, then offer to save them. ``` WATCH_FOLDER Folder containing one markdown file per prospect or contact STATUS_KEY Frontmatter key holding the state (default: status) DUE_KEY Frontmatter key holding the follow-up date (default: follow_up_due) DONE_VALUES Status values that need no follow-up (default: Replied, Closed, Skip) VOICE_NOTES Optional tone guidance for drafts ``` The expected file shape is simple frontmatter, for example: ```markdown --- company: Example Studio status: Sent follow_up_due: 2026-05-01 --- ``` If the user's files use different keys, map them in the config instead of asking them to change their files. ## Step 1: Scan and report Read the frontmatter of every markdown file in WATCH_FOLDER. Build the report before drafting anything: ```markdown # Follow-up Radar: <today> ## Overdue (oldest first) | Contact | Status | Due | Days overdue | File | |---|---|---|---|---| ## Due in the next 7 days | Contact | Status | Due | File | |---|---|---|---| ## Waiting, not yet due: N ## Done or closed: N ## Files with missing or unparseable dates: <list t