What problem does it solve? When a marketing project or campaign blows its deadline, coordinators often accept the first recovery plan out of inertia. This Skill structures the replanning decision: it reads open tasks, dependencies, deadlines, and team workload from Notion, asks the decision-maker for their own guess first, and only then presents 2-3 scenarios with explicit trade-offs. ## Core Features & Use Cases - Evidence-based scenario generation: Always presents 2-3 options (cut named scope, push the deadline, redistribute work) with who is affected, risk, and a one-line premortem for each. - Notion data grounding: Reads open tasks, blocking dependencies, approval bottlenecks, and absolute workload per person from the PMO Notion databases before proposing anything. - Anti-inertia decision flow: Requires the coordinator to state their own guess before seeing scenarios, reducing passive acceptance of the first recommendation. - Use Case: A coordinator says "the congress campaign won't make it" — the Skill reads the campaign's open tasks and team load, asks for the coordinator's hunch, then presents cut/push/redistribute scenarios and delivers the chosen one as a concrete change list. ## Quick Start Ask the assistant to replan a delayed project by name, for example: "replaneja a campanha do congresso, não vai dar tempo".
