What problem does it solve? Organizing a tech event means coordinating venue, program, sponsors, marketing, and ticketing workstreams that all depend on each other, and a single chronological to-do list hides which slip blocks what until it is too late. This Skill turns a locked doors-open date into a structured work-back plan that surfaces dependencies, protects irreversible commitments, and pre-decides what to do when things fall behind. ## Core Features & Use Cases - Work-back planning by track: Works each parallel track (venue, program/CFP, sponsors, marketing, ticketing, budget, team) backward from the doors-open date, with cross-track dependency gates naming both milestones. - Buffer policy and latest-safe dates: Marks every irreversible spend or headcount decision with its latest-safe commitment date, and sets up a Good/Better/Best scope-tier ladder when the budget depends on unbooked revenue. - Pre-written replanning checkpoints: Defines dated checkpoints with a measurable condition, a pre-decided action, and an owner, plus a mid-flight replan procedure that cuts scope instead of moving an announced date. - Use Case: Your conference is locked for June 12 with the venue signed, but the CFP closed late and sponsorship is behind target. The Skill rebuilds per-track actuals, spends buffers in order, cuts scope at the gate level, and rewrites the remaining checkpoints without moving the date. ## Quick Start Ask the assistant to build a work-back plan for your event by giving it the locked doors-open date, the tracks involved, and any immovable external deadlines.
