Skip to content

samber/dev-event-organizer-skills / skills/business-event-formats

business-event-formats

Verified

Choose which company-run event shape to run - invite-only dinner, executive summit, single-city user conference, multi-city roadshow, or a floor-primary trade-show event - plus how its program is sourced and what shape its floor takes. Also owns the business-oriented activity layer any conference can run beside its program for sponsors (hiring corner, hands-on product feedback session, opt-in demo space, matchmaking). Use whenever a company weighs a user conference against a roadshow or a summit, asks what kind of event to put on for developers, customers or partners, or asks whether to run its own floor or exhibit on someone else's, or an organizer asks what to offer sponsors beyond talks, even if they only say "we want to do an event". Format catalog only. Do NOT use for track count or session mix - use samber/dev-event-organizer-skills@event-format-selection; for floor operations use samber/dev-event-organizer-skills@event-booth-experience; for goals and budget use samber/dev-event-organizer-skills@corporate-event-strategy.

references/ranking-dominance-analysis.md

View on GitHub
# Ranking dominance analysis

Full pairwise dominance checks and tie justifications for the three ranked menus in SKILL.md: the event-shape ladder, the program-sourcing posture, and the floor shape.

## Event-shape ladder

The effort tie (`multi-city roadshow == single-city user conference`) holds because both spend comparable total effort in incompatible shapes. The conference concentrates it into one long runway and one venue commitment that stops being reversible early. The roadshow spreads it across repeated small productions that stay individually cancellable but keep demanding coordination. Neither is the cheap one.

The compliance tie (`single-city user conference == floor-primary event`) holds on this axis's own definition:

- A single-city conference and a floor-primary event sign the same class of ordinary venue, exhibitor and vendor paper for an event of their size. Neither creates a per-guest obligation a third party's compliance function has to approve.
- Hosted hospitality for a named individual does create that obligation: an accepted invitation cannot be withdrawn without insult, and it lands on the guest's own gift and anti-bribery policy before it lands on yours.
- A roadshow crossing jurisdictions triggers a registration-data and marketing-consent review at every stop.

The account-depth efficiency line discriminates nothing. It is rank-identical to the account-depth value axis and to inverse effort simultaneously, so dividing value by effort changes no position: the ordering is cheapest-first by construction. It is still the right ordering when Q3 says named accounts, because a dinner really does move a named account more cheaply than a floor. But the ratio adds nothing the value axis did not already carry, and it cannot catch an error.

Dominance: 10 pairs examined, 0 strict dominance relations, one mechanism accounts for all 10. The two value axes (reach, account depth) are exact reversals of each other across all five rungs, so in every pair whichever rung wins reach loses depth. That blocks dominance in all ten pairs before effort or compliance is even consulted, and adding those two cost axes changes nothing: a rung cheaper on both still loses one value axis.

The consequence: this menu's ordering is clean by construction, not by care. The dominance check verifies nothing here, and the efficiency lines rest entirely on the Q3 answer plus the judgment above.

## Program-sourcing posture

The message-control efficiency line discriminates nothing. It is rank-identical to inverse effort and to the control value axis at once, so it reduces to cheapest-first, the one ordering a ranking exists to prevent. Never let the control axis pick the posture on its own; use it only to see what the credibility ordering costs.

Dominance: 6 pairs examined, 0 strict dominance relations, one mechanism accounts for all 6. Credibility and message control reverse each other across all four rungs, so every pair splits the two value axes before effort is consulted. The check verifies nothing here either.

## Floor shape

The borrowed-access tie is argued at zero: both own-floor rungs fill their own room without borrowing a single attendee, so on that axis they are identical by definition and their ratio stays zero whatever effort is spent. That is also why the second efficiency line ties them at the bottom rather than separating them.

Dominance: 3 pairs examined, 0 strict dominance relations, and it takes two mechanisms to cover them:

- For the two pairs involving the third-party rung, ecosystem visibility runs exactly opposite to both effort and borrowed access, so each pair splits.
- For the remaining pair, own showcase floor against program-plus-floor, the borrowed-access axis is tied at zero, so the split is ecosystem visibility against effort, with neither rung better on both.

One mechanism covers only two of the three pairs. An argument that stopped there would read as complete and still be wrong.
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: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated 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: 323kUpdated Claude CodeCodexVerifiedInstall