follow-up-patrol

Automated follow-up tracking parses MEMORY.md and your issue tracker to compute item ages and trigger escalation alerts when thresholds are exceeded. It classifies items into Known Follow-ups, Next Priorities, and Open Loops to ensure nothing rots unattended during weekly audits.

Monitoring open loops involves parsing memory sections to extract labels, dates, and statuses, then computing ages to detect deadlines. This process generates escalation statuses across CRITICAL, HIGH, MEDIUM, and WATCH tiers, writing results to a follow-up status report.

Calculating item ages requires extracting the date and status from each follow-up entry, then computing the duration against predefined thresholds. The system assigns escalation tiers like CRITICAL or WATCH and logs the results to memory/topics/follow-up-status.md.

Yes, automated escalation audits run without external dependencies by reading directly from MEMORY.md and the issue tracker. The skill internally parses multiple sections, computes ages, and generates optional notifications alongside the status report.

Weekly escalation audits should be run during regular review cycles to parse the latest MEMORY.md and issue tracker entries. Running the audit computes current item ages and immediately flags any follow-ups that have crossed urgency thresholds.

Follow-up status reports capture open loops by parsing specific sections within MEMORY.md, extracting the label, date, and status for each item. If entries lack proper dating or status formatting, the age computation and subsequent escalation detection may fail to classify them correctly.