User Consent Lifecycle Manager: TOS Update Navigator

Your infrastructure team pushed a change last Thursday. New third-party data processor. Scoped, they said. Minimal. Your legal counsel is on retainer, not on call, and you're staring at your current Terms of Service trying to figure out if this crosses a line that requires you to re-paper your entire user base — or if a banner notification is enough. You have 140,000 users. The answer is not obvious. You have a product launch in eleven days.

The damage: you either over-react and trigger a formal re-consent flow that churns users who don't re-opt-in, or you under-react and find yourself in a regulatory conversation explaining why you didn't notify users of a material change. Both outcomes are expensive. One of them is a headline.

The obvious fix — asking your lawyer to review the change — takes a week, costs $800, and returns language that replaces your entire privacy policy with boilerplate that no longer sounds like your company. You don't need a full redraft. You need a precise answer to a precise question.

This skill gives you a structured decision framework that assesses materiality, scopes policy language to the specific change, and tells you whether you're in re-consent territory or passive notification territory — before you build the flow.

What you get: SKILL.md — the complete decision protocol, including materiality threshold criteria, re-consent trigger logic, and policy drafting sequences scoped to the change, not the whole document. SETUP_GUIDE.md — configuration instructions for deploying this workflow against your existing policy documents and change descriptions. EXAMPLES.md — worked scenarios across infrastructure changes, feature additions, and third-party processor updates, showing exactly how the skill reasons through each case. CHANGELOG.md — version history documenting updates to the materiality criteria and trigger logic. External dependency: None. Runs entirely within your agent's context.