Skip to content

samber/dev-event-organizer-skills / skills/event-positioning

event-positioning

Verified

Define a technical event's positioning - what it stands for, against which alternatives, for which audience identity. Covers the governance axis (community-run, foundation, media-run, vendor-owned), competitive-alternative mapping, best-fit attendee and sponsor segments (and when a conference may serve several targets), the business-oriented layer sponsors buy, market-category strategy (head-to-head, subcategory, new category and its education tax), the positioning statement, contrast-not-attack anti-positioning, and the rebrand gate. Use whenever asked to position a conference, meetup or hackathon, differentiate it from neighboring events, decide who it is for, write a positioning statement, weigh a vendor-neutrality claim, or judge an event rename. Strategy only. Do NOT use for on-site embodiment - use samber/dev-event-organizer-skills@event-cultural-identity.

references/promise-and-audience-level.md

View on GitHub
# Promise feasibility, audience level, and why vs impact

Treat it as field testimony, not established practice. Everything unmarked is this skill's own construction.

## Contents

- Candidate values
- Promise-feasibility check
- Audience-level decision
- Specialist-competitor drain
- Topic durability
- Why vs impact exercise

## Candidate values

Positioning values to consider. Use them as a prompt list for step 3's unique attributes, never as a template to copy:

- **State of the art** - not months behind the frontier; excellence outside the capital too.
- **Decentralization and proximity** - the event comes to the attendee's city.
- **Inclusivity** - across geography, gender, and level.
- **Connecting people** - the room is the product.
- **Building projects together** - attendees leave with collaborators, not only notes.
- **Fun and kindness.**
- **"No bullshit" and actionable** - content an attendee can apply the next day.
- **Horizontality** - no organizer or chapter above another.
- **Tone: "pizza-beer, not champagne"** - a register decision; hand it to `samber/dev-event-organizer-skills@event-cultural-identity`.

Each value only belongs in the positioning when it passes the "only this event" test against the named alternatives. "Fun and kindness" rarely does on its own; "state of the art outside the capital" can, in a region whose alternative is a train ticket.

## Promise-feasibility check

Run it on the headline promise before publishing, then once per edition.

1. Write the headline promise as one sentence an attendee could quote back.
2. For each of the next N editions (N self-set; 3 is a reasonable start), name what delivers it: speakers, format, venue, budget, organizer hours.
3. Mark each edition **deliverable**, **deliverable with a named risk**, or **not deliverable**.
4. Any **not deliverable** edition means the promise is too strong for the resources. Narrow the promise, or secure the resource before publishing it.

Worked example: "state of the art every month" at a monthly meetup needs a speaker pipeline that can supply frontier content twelve times a year. If the speaker bank holds four such speakers, the promise fails by edition five. Narrower promise: "a state-of-the-art session every quarter, practitioner talks in between."

Negative example: "the best AI event in the region" - no edition can check it, so no edition can fail it, and attendees discount it to zero.

## Audience-level decision

The choice: **make the strong stronger, or make everyone aware.**

| Choice                   | Best-fit attendee                | Program shape                             | Risk                                              |
| ------------------------ | -------------------------------- | ----------------------------------------- | ------------------------------------------------- |
| Make the strong stronger | Practitioners already building   | Deep dives, live code, frontier topics    | Small room; newcomers bounce                      |
| Make everyone aware      | Curious professionals, newcomers | Overviews, use cases, demystification     | Advanced attendees drain to specialist events     |
| Split by format or track | Both, kept apart                 | Separate sessions or alternating editions | Twice the program work; the brand must carry both |

Reported observations:

- "For everyone" was judged too broad - the same non-option the main skill deletes.
- Meetup attendees are already convinced of the topic; an "awareness" promise mostly reaches people already aware.
- Mixed-level rooms produce contradictory feedback: "too technical" and "not technical enough" on the same session. Read that pair as a level-split signal, not as a quality verdict.

Decide the level explicitly, write it in the positioning statement's attendee clause ("For [practitioners who already ship X]"), and tell `samber/dev-event-organizer-skills@event-talk-selection` and `samber/dev-event-organizer-skills@event-feedback` which level the program targets.

## Specialist-competitor drain

Specialist meetups (one framework, one tool, one sub-discipline) can drain the most advanced attendees from a generalist community. Map them in step 2 as direct rivals for that segment only. Then pick one:

- **Concede the segment** - state the level as "everyone aware"; point advanced attendees to the specialist events and partner with them.
- **Defend the segment** - offer what a specialist meetup cannot: cross-topic synthesis, a bigger network, project-building formats.
- **Absorb by partnership** - co-host specialist sessions under your calendar via `samber/dev-event-organizer-skills@cross-event-promotion`.

Never leave the drain unnamed: an unexplained fall in advanced attendees reads as a quality problem and triggers the wrong fix.

## Topic durability

One practitioner argued that communities scoped to one programming language or framework will not last, because AI tools reduce how much the language matters. Do not treat it as a forecast. Treat it as a re-test trigger:

- If the positioning is scoped to one technology, re-test the scope on a self-set cadence (every N editions or yearly).
- The test: would the best-fit attendee still define themselves by this technology in two years? If the answer drifts, widen to the job ("people who build X") rather than the tool.
- A rename stays behind the rebrand gate in the main skill: widen the program first, the name second.

## Why vs impact exercise

The "why" is stable and high-level; the "impact" evolves with the community's stage. Separating them stops the positioning statement from churning every time the impact goal moves.

Exercise, reported as taking about five minutes per community with sticky notes:

1. Each organizer writes one sticky: "We exist because..." (why).
2. Each organizer writes one sticky: "This year, success changes..." (impact).
3. Cluster each set. Matching whys mean the team is aligned; scattered whys are the misalignment finding interview Q3 looks for.
4. Keep the why in the positioning statement. Put the impact in this edition's goals, handed to `samber/dev-event-organizer-skills@event-debrief` and `samber/dev-event-organizer-skills@event-continuous-improvement`.
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