# Work Back

> Build the months-long work-back plan for a technical event, then the checkpoint sheet its track owners run. Enter the
> doors-open date, the tracks with their owners and milestones, the irreversible commitments, the gates between tracks,
> the external deadlines and the checkpoints. Built on the SkillSafe skill @samber/event-planning-timeline
> (samber/dev-event-organizer-skills, MIT).

https://work-back.skillsafe.ai/

## What is free
- Every milestone bucketed by whole weeks before doors-open (S-4 is four weeks out), each track worked backward from its terminal milestone, late milestones against the as-of date, milestones written as instructions instead of finished states, and long unwatched stretches in a track.
- Ownership: every track held to exactly one accountable owner.
- Every gate checked for both sides, for crossing tracks and for its dates; the sequencing gates the plan implies but never states (payment before the date announcement, venue before the announcement, budget before the prospectus, speakers before the program, the program before its sales push, headcount before catering).
- Every irreversible commitment held to a latest-safe date and an owner, with commitments planned earlier than they need to be flagged.
- The granularity rung (gated milestones by default, milestone-only for one or two organizers, the task-level critical path promoted by paid staff, several venues or a penalty clause and deleted for one or two volunteers), the buffers (delayed commitment, the Good/Better/Best ladder promoted by unbooked revenue, padding only for external lead times) and the replanning menu (pre-written checkpoints, the cadence review promoted or deleted, the event-driven floor).
- Every checkpoint held to a date, a measurable condition, a pre-written action and an owner; an announced date never moves; on a plan already behind, the levers in spending order.
- Plan CSV, Markdown and JSON exports.

## The metered lanes
Two tasks on gpt-terra, metered per run, routed by `task`. Input string fields: `task` (plan or sheet), `event`, `plan` and `facts`.
- `plan` replies with `summary`, `anchor`, `granularity`, `tracks`, `gates`, `missing`, `commitments`, `buffers`, `replanning`, `levers`, `measurement`, `signals` and `caveats`; the page holds every track's owner, terminal milestone and late count, every gate status, every latest-safe date, the menus and the plan gates to its own.
- `sheet` replies with `title`, `checkpoints`, `added`, `replan`, `message` and `note`; the page requires every checkpoint's date and owner, labelled replacements for flagged actions, added checkpoints only on milestone dates, and no move of an announced date.

## Links
- API tutorial: https://work-back.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@samber/event-planning-timeline