Skip to content

samber/dev-event-organizer-skills / skills/event-planning-timeline

event-planning-timeline

Verified

Build the months-long work-back plan for a tech event, any edition - the doors-open anchor date, parallel tracks (venue, program/CFP, sponsors, marketing, ticketing) each worked back from that date, cross-track dependency gates, a buffer policy through latest-safe commitment dates, and replanning checkpoints that cut scope instead of moving the date. Use whenever asked to build an event planning timeline, conference retroplanning, a work-back or reverse schedule, event milestone sequencing, or to replan an event running behind schedule. Scheduling mechanics only. Do NOT use to pick the date itself - use samber/dev-event-organizer-skills@event-date-selection - or for the day-of run of show - use samber/dev-event-organizer-skills@event-run-of-show.

FileKindSize
SKILL.mdskill md21.1 KB
evals/evals.jsonconfig24.3 KB
references/buffers-and-replanning.mdmarkdown7.9 KB
references/tracks-and-gates.mdmarkdown5.5 KB

references/tracks-and-gates.md

View on GitHub
# Tracks and cross-track dependency gates

The track taxonomy and gate catalog behind the work-back plan. Milestone chains here are the general pattern - how long each chain runs is a format-driven question answered by `samber/dev-event-organizer-skills@event-first-edition`'s sourced runways, not by this file. Trim the taxonomy to the event: merge tracks a small event doesn't need rather than leaving empty ones on the plan.

## Per-track milestone chains

Each chain reads backward: the terminal milestone sits at or near doors-open, the head milestone is the track's first action. Write dates onto the chain only after the anchor date and the immovable external deadlines are fixed.

**Venue & logistics** - requirements sheet → search → shortlist and site visits → venue locked → contract signed → deposit paid (a latest-safe-date commitment, not an automatic next step) → build-up/tear-down plan → final logistics walkthrough.

**Program** - CFP designed → CFP opens → CFP closes → selection/voting → speakers confirmed → program announced. Selection needs real lead time before announcement: speakers need employer approval and travel arrangements, so the confirmation-to-announcement segment cannot be compressed to zero (a sequencing constraint stated in a major community-conference organizing guide). An invited-speaker program replaces the CFP segment of this chain - the trade-offs of that swap belong to `samber/dev-event-organizer-skills@event-first-edition`'s compression levers.

**Sponsors & partners** - budget-derived sponsorship target → tier design → prospectus assembled → outreach begins → agreements signed → invoicing → fulfillment obligations scheduled through the marketing and logistics tracks.

**Marketing & comms** - channel setup → announcement plan (each announcement is a dated milestone, not ambient activity) → sustained outreach → reminder sequence → final-two-weeks push.

**Ticketing & registration** - payment infrastructure live → pricing set → sales open → early-bird close → sales checkpoints → final headcount.

**Budget & finance** - draft budget → scope tiers costed (Good/Better/Best, if the ladder is in use) → revenue checkpoints → vendor payment deadlines → reconciliation.

**Team & volunteers** - track owners confirmed → delegation as workload grows → day-of volunteer recruitment → volunteer briefing.

## Cross-track gate catalog

A gate names two milestones in different tracks: the prerequisite and the milestone it blocks. Every gate on the plan must name both sides: "sponsors depend on budget" is a sentence, "prospectus assembled ⟸ draft budget approved" is a gate.

Sourced gates (from named organizing guides, generalized here to any edition):

- **Payment infrastructure live ⟸ blocks ⟹ date announced.** A major community-conference organizing guide states this as a hard rule - a date cannot be announced until the team can handle money - and reports rescheduled or cancelled events from skipping it. The general lesson: announcement is a gated milestone whose prerequisites span three tracks (venue, ticketing, comms).
- **Code of conduct published ⟸ first public listing.** Sourced sequencing from the same guide's ecosystem - the earliest hard administrative gate, ahead of venue and date. The CoC's content belongs to `samber/dev-event-organizer-skills@event-code-of-conduct`. First-edition specifics belong to `samber/dev-event-organizer-skills@event-first-edition`.
- **Sponsor prospectus timing ⟸ sponsors' fiscal-year budget cycles.** Larger sponsors commit budget a fiscal year ahead (same guide) - an _external_ deadline that pulls the whole sponsor track earlier than internal logic alone would place it. List external budget cycles among the immovable deadlines in interview Q3.
- **Venue locked ⟸ date announced publicly.** Date and venue are a joint negotiation, not a sequence - holding several candidate date windows open improves venue availability (a named practice in the same guide's date-selection advice - the decision itself belongs to `samber/dev-event-organizer-skills@event-date-selection`).

Derived gates (standard sequencing logic rather than published event-industry rules):

- **Draft budget approved ⟸ sponsor prospectus assembled** - tiers are priced off the budget gap, not invented.
- **Program announced ⟸ the program-driven sales push** - announcements are the moments sales spike, so marketing schedules its pushes onto program-track milestones (demand thresholds at those moments: `samber/dev-event-organizer-skills@event-market-fit`).
- **Speakers confirmed ⟸ program announced** - never announce a program still being negotiated.
- **Final headcount ⟸ catering and swag orders** - the canonical delayed-commitment pair: the order's latest-safe date is set by the vendor's real lead time, and headcount must be frozen just before it.
- **Track owners confirmed ⟸ any track's first milestone** - an ownerless track has no one to notice its slip.

## Latest-safe dates on the gate view

For every gate whose downstream milestone is an irreversible commitment (deposit, catering order, print run, contractor booking), record two dates: the earliest the commitment _could_ be made and the latest it _safely_ can. Plan to the latest-safe date whenever the cost of committing early and being wrong exceeds the cost of committing late and scrambling - the asymmetry test from the buffer policy in SKILL.md. The earliest-possible date is not a target: it is how teams quietly spend their reversibility.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall