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.

evals/evals.json

View on GitHub
{
  "skill_name": "event-positioning",
  "evals": [
    {
      "id": 1,
      "prompt": "I run marketing for Quaylight, an observability vendor. Our annual event QuaylightCon pulls 2,400 people. This year 38 of our 52 sessions are Quaylight product content - deep dives, roadmap, certification. Our Slack is genuinely warm, we call attendees 'the Quaylight family' and people fly in from 30 countries on their own dime. The exec team wants the new tagline to be 'the vendor-neutral observability community gathering' and wants that language on the site, the prospectus and the CFP. Can you write up our positioning around that?",
      "expected_output": "A positioning brief that places QuaylightCon at the vendor-owned pole, refuses the vendor-neutral claim on the single-vendor program share, offers rebalance-or-drop as the only two remedies, and proposes honest vendor-pole framing instead.",
      "files": [],
      "expectations": [
        "Places QuaylightCon at the vendor-owned end of the governance spectrum, justified by ownership and where surplus money goes rather than by the event's tone",
        "States the vendor-neutral claim is forfeit because single-vendor program content (38 of 52 sessions, roughly 73%) exceeds the threshold",
        "Names the threshold explicitly as roughly 30-40% single-vendor program content",
        "Offers exactly two remedies for the neutrality claim: rebalance the CFP so single-vendor content falls under the line, or drop the claim",
        "Rejects the warm Slack, the 'family' language and the self-funded travel as evidence of community governance",
        "States that warm or belonging language is available at every point on the governance spectrum and is deliberately borrowed by vendor events",
        "Does not recommend 'vendor-neutral', 'community-run' or an equivalent neutrality claim in any tagline or prospectus line",
        "Names what the vendor pole can honestly claim instead, such as practitioner or builder framing, scale and access to launches, or an executive carrying the edition's thesis",
        "Produces a positioning statement in the shape 'For [best-fit attendee], [event] is the [event category] that [unique value theme]'",
        "Does not deliver a finished tagline or hero copy before audience, alternatives and category are settled",
        "Presents 2-3 candidate positionings with trade-offs and one recommendation rather than a single answer",
        "Adds a recurring neutrality audit measuring single-vendor share of program content against the same threshold"
      ]
    },
    {
      "id": 2,
      "prompt": "Northbound is a 300-person data-engineering conference I run in Manchester, third edition next spring. There are two other data conferences in the north of England - Pipeline North and DataHaus - and honestly we blur together. I sat my four co-organizers down last week and we listed out what we think attendees would do if they didn't come to us. Can you build me a differentiation angle against those two so I can start writing the sponsor deck?",
      "expected_output": "A competitive-alternatives map across all five types, per segment, with the organizers' guesses rejected as a basis and interviews specified before any differentiation claim is written.",
      "files": [],
      "expectations": [
        "Maps alternatives across all five types: direct rivals, adjacent events repurposed for the same job, doing the job without any event, sending a delegate instead, and doing nothing at all",
        "Names doing nothing as frequently the largest true competitor rather than a marginal case",
        "Includes a concrete eventless alternative such as watching the talks on video afterwards or living in the topic's Slack or Discord community",
        "Includes sending one delegate to report back to the team as its own distinct alternative type",
        "Rejects the four organizers' own guesses as a basis for differentiation and requires real interview answers first",
        "Specifies interviewing roughly 15-20 people",
        "Specifies interviewing the happiest repeat attendees and sponsors rather than prospects",
        "Keeps separate alternative lists per segment instead of one blended ranking across attendees and sponsors",
        "States that the sponsor's primary alternative typically differs from an individual attendee's, for example a rival vendor summit or running their own private event versus doing nothing or watching videos",
        "Classifies Pipeline North and DataHaus by ownership and money flow rather than by their tone or marketing language",
        "Runs the do-nothing diagnostic when do-nothing dominates, mapping causes such as acute-trigger gap, risk perception and inertia to different positioning answers",
        "Does not produce a finished differentiation claim or sponsor-deck copy before the alternatives research exists"
      ]
    },
    {
      "id": 3,
      "prompt": "We're launching ThreadFest next May - first edition, targeting about 150 people, and it's basically me part time plus two friends who help on weekends. Zero sponsors so far. The topic is the overlap between developer experience and internal documentation, and genuinely nothing out there covers exactly that. My plan is to invent and own a whole new conference category, 'the docs-ops summit', because if we define the category we own it and nobody can catch us. That's our moat. How do we build the positioning around that?",
      "expected_output": "A category-strategy recommendation that refuses the new category on this edition's resources, prices the education tax, and starts the event as a named subcategory with an evolution path.",
      "files": [],
      "expectations": [
        "Ranks the market-category menu on separate axes for effort, value and efficiency rather than one blended order",
        "States that efficiency never selects the new category, because it is simultaneously highest effort and highest value",
        "Names the subcategory of an existing category as the default rung",
        "Refuses the new category here, citing the unmet promotion condition: no multi-edition runway, no existing sponsor relationships, no established brand",
        "Names the education tax concretely, including slower ticket and sponsor cycles because nothing maps to a known budget line, copy that must explain the concept itself, marketing spend at multiples of a known category's, and multiple editions before awareness exists",
        "States that a first edition already carries unproven-event risk and a new category compounds it with the attendee not knowing how to judge the event",
        "Recommends starting as a subcategory and evolving toward the new category once traction exists",
        "Proposes at least one concrete subcategory name following a naming pattern such as [topic] for [vertical], format-modified [topic] conference, or [audience]-first [topic] event",
        "Explains that a subcategory inherits the parent category's existing sponsor budget lines and audience understanding",
        "Deletes 'for anyone who cares about docs' or any everyone-audience framing rather than listing it as a weaker option",
        "Asks about the publication deadline, one-off versus compounding mandate, and the effort ceiling before committing to a ranking",
        "Does not accept the user's 'moat' framing for the new category unchallenged"
      ]
    },
    {
      "id": 4,
      "prompt": "Foundry Days is our volunteer-run platform engineering conference, second edition, about 250 people, tickets at cost. There's a much bigger paid event called PlatformScale run by a consultancy - 900 pounds a ticket and every keynote is basically a sales pitch for their services. We want our marketing to say plainly that we are not PlatformScale, name them, let people draw the conclusion. Draft that line for us. Side note, when a sponsor asked my four co-organizers last month what the event is, we each gave a different answer, which was awkward.",
      "expected_output": "A refusal to name the rival, an archetype contrast sentence, the alignment-rubric diagnosis of the four different answers, and the two cheap levers published together.",
      "files": [],
      "expectations": [
        "Refuses to name PlatformScale or any specific rival event in the anti-positioning line",
        "Produces a contrast sentence that names an archetype instead of a competitor",
        "Uses the shape 'There are many [archetype] events. This is not one of them.'",
        "Gives both reasons an archetype contrast is required: it does not age out when the rival changes strategy, and it cannot be read as an attack inviting public rebuttal",
        "Classifies PlatformScale by ownership and money flow rather than accepting 'sales pitch' tone as the classification",
        "Identifies four organizers giving four different answers as a positioning-alignment finding in its own right, not a communications or training problem",
        "Scores the current state against the 0-10 alignment rubric and places it in the band where organizers describe the event differently from each other",
        "States that 7 or above is the pass threshold and treats anything below it as unfinished work to iterate on",
        "Recommends publishing the contrast sentence together with a public rationale for the event's structural choice, as the default pair",
        "States that the two cheap levers tie on effort because the real cost is the decision behind each, not the writing",
        "Does not recommend a rename or rebrand as the fix"
      ]
    },
    {
      "id": 5,
      "prompt": "Our conference has been JVM Summit Krakow for six years. Program is still about 85% JVM content - Spring, Kotlin, GraalVM, the usual. Registrations were flat this year, 620 against 640 last year. The board is convinced the name is holding us back and wants to rename to 'Krakow Polyglot' to signal we're modern and to open up sponsor categories beyond the JVM vendors. We've already commissioned a logo and bought the domain. Can you write the launch announcement for the new name?",
      "expected_output": "A rebrand gate that fails, a refusal to draft the announcement, direction to fix program scope first, and the compliance exposure a rename carries spelled out.",
      "files": [],
      "expectations": [
        "Runs the rebrand gate before drafting anything, asking whether the audience or content scope has already moved beyond what the current name promises",
        "Concludes the gate fails, because the program is still roughly 85% JVM content",
        "States the rename is off the table, not postponed",
        "Directs the team to settle program scope first: either broaden the program deliberately, or narrow back to what the existing name promises and keep it",
        "States the order is substance first and name second, and that a rename promising change rather than recording one reads as churn",
        "Declines to produce the rename launch announcement copy",
        "Notes that a justified rename must map old scope to new scope explicitly in the announcement itself",
        "Flags rebrand as the only positioning lever carrying compliance exposure, naming trademark and domain clearance plus renaming the event across signed sponsor agreements, venue contracts and listings",
        "States a rename cannot be quietly walked back the way a published sentence can",
        "Does not treat the flat registration figures (620 against 640) as evidence the name is the cause",
        "Recommends a cheaper lever instead, such as the contrast sentence or a public rationale for the event's structure",
        "Does not attach any figure or percentage to what the rename would do for registrations or sponsor categories"
      ]
    },
    {
      "id": 6,
      "prompt": "BuildJam is our 36-hour student hackathon, 400 participants, fourth year. A fintech sponsor has committed 40,000 euros in prizes on the condition that the whole campaign is built around the pool - they want 'Europe's biggest student hackathon prize' as the headline everywhere. Our marketing lead already drafted the tagline and had the hero image designed last week. Build the positioning out from that so we can brief the design agency on Friday.",
      "expected_output": "A rejection of prize-led positioning as a known failure mode, learn/build/share plus beginner inclusion as the lead, the drafted tagline treated as an output rather than an input, and 2-3 candidates with a recommendation.",
      "files": [],
      "expectations": [
        "Rejects prize-led positioning as the lead and names it as a known failure mode rather than a stylistic preference",
        "Recommends leading instead with learning, building, sharing, and explicit beginner inclusion",
        "States that leading with prize size cedes ground and attracts the wrong room",
        "Notes the format can remain genuinely competitive underneath while the positioning does not lead with prizes",
        "States that positioning must be settled before the tagline and hero copy, and that deciding messaging first is the most common ordering error",
        "Refuses to treat the already-drafted tagline and hero image as fixed inputs the positioning must serve",
        "Keeps the 40,000 euro prize pool available as a proof point or supporting detail rather than the positioning itself",
        "Chooses a best-fit attendee segment narrower than 'students' and does not position for everyone",
        "Produces a positioning statement in the 'For [best-fit attendee], [event] is the [event category] that [unique value theme]' shape",
        "States explicitly that first-time or non-programmer participants are welcome as part of the positioning",
        "Presents 2-3 candidate positionings with trade-offs and one recommendation rather than executing the sponsor's brief directly"
      ]
    },
    {
      "id": 7,
      "prompt": "Relay is our single-track frontend conference, five editions in, 700 attendees, curated end to end by our founder Ana who writes a newsletter with about 40,000 subscribers and personally picks every single speaker. We have nine months to the next edition and the ambition is that Relay becomes the thing people plan their year around for the next decade. Our sponsor deck currently says 'a marquee keynote lifts early registrations by 30%'. Should we lean harder into booking big-name keynotes? Where should we put our effort beyond just writing a positioning line?",
      "expected_output": "A lever-investment recommendation promoting lineup-as-brand on the compounding mandate and curator, with the 30% headliner claim refused and removed, and the single-track choice published as an identity claim.",
      "files": [],
      "expectations": [
        "Refuses to use the '30% lift in early registrations' headliner claim, identifying it as speaker-bureau or PR advocacy rather than verified data",
        "Recommends removing that claim from the sponsor deck rather than restating or softening it",
        "Promotes lineup-as-brand for Relay, citing the compounding multi-edition mandate and a curator whose taste is genuinely the product",
        "States lineup-as-brand is the starved option under a pure efficiency ranking: top on value but second on effort",
        "Names the effort lineup-as-brand costs as a season of curation and invitations",
        "Ranks the positioning-lever menu on separate axes including effort, value, efficiency and compliance cost, rather than one blended order",
        "States rebrand is the only lever carrying compliance cost, and that the other levers tie at no review triggered and no reversibility spent",
        "Applies the lineup benchmark question: can attendees say why these specific speakers are together",
        "Treats a shrug on that benchmark as the lever not yet working, not as an individual speaker-quality problem",
        "Recommends publishing the single-track choice as an explicit public identity claim rather than leaving the event undeclared in the middle",
        "Distinguishes booking individually famous keynotes from lineup-as-brand, which turns on the coherence of the set",
        "Does not recommend a rebrand or rename"
      ]
    },
    {
      "id": 8,
      "prompt": "Kestrel is a four-year-old SRE conference, 900 attendees, we run it as a small company. Two problems. First, sponsors keep describing us to their colleagues as 'a recruiting fair', which is not what we are. Second, our sponsor-close cycle is running five months when the comparable conferences we know close in about six weeks. Our head of marketing wants to reposition the event every year so it stays fresh, and she's asking me for the industry benchmark number that links positioning quality to ticket sales so we can track it on the dashboard. What's that benchmark and how do we fix the two problems?",
      "expected_output": "A refusal to supply a benchmark that does not exist, the 0-10 alignment rubric offered instead, both symptoms read as misdescription-watch triggers firing a category re-run, and annual repositioning rejected.",
      "files": [],
      "expectations": [
        "States plainly that no industry number ties positioning quality to ticket or sponsor outcomes, and declines to supply one",
        "Does not invent or cite any percentage, conversion rate or benchmark figure linking positioning to ticket or sponsor results",
        "Offers the 0-10 alignment rubric with a pass threshold of 7 or above as the judged measure instead",
        "Identifies both reported symptoms as misdescription-watch triggers: sponsors consistently describing the event wrongly to colleagues, and a sponsor cycle far longer than category peers'",
        "Recommends re-running the market-category step at the next edition on the strength of those triggers",
        "Rejects repositioning every edition, giving the reason that returning attendees and sponsors are the asset",
        "States that messaging may be adjusted more often than positioning, which is committed across multiple editions",
        "Requires deciding in advance which proxy triggers which revision and writing both down before publishing",
        "Names at least two further triggers from the misdescription watch list, such as arrivals expecting things the event does not deliver, or CFP submissions assuming capabilities the event lacks",
        "Treats 'recruiting fair' as evidence the sponsor-side best-fit segment or value theme is wrong, rather than as a copy problem",
        "Does not recommend a rename or rebrand as the fix"
      ]
    }
  ],
  "trigger_queries": [
    {
      "query": "How should we position our new platform engineering conference against the two cloud events already running in our city?",
      "should_trigger": true
    },
    {
      "query": "Write a positioning statement for our developer conference",
      "should_trigger": true
    },
    {
      "query": "Our meetup grew into a conference and sponsors keep calling it a vendor day, help me fix that",
      "should_trigger": true
    },
    {
      "query": "Should we rename the event? The name still says DevOps but half the program is platform and AI infra now",
      "should_trigger": true
    },
    { "query": "who is our conference actually for", "should_trigger": true },
    {
      "query": "The company wants our user conference to feel like a community event. What can we honestly claim?",
      "should_trigger": true
    },
    {
      "query": "What makes our hackathon different from every other hackathon out there?",
      "should_trigger": true
    },
    {
      "query": "Define what our event stands for and what it stands against",
      "should_trigger": true
    },
    {
      "query": "Can we describe our conference as vendor-neutral?",
      "should_trigger": true
    },
    {
      "query": "I need to nail down what our conference is and what it isn't before we open the CFP",
      "should_trigger": true
    },
    {
      "query": "Help me find our actual differentiator, not just a nicer way to say the same thing",
      "should_trigger": true
    },
    {
      "query": "our three organizers all describe the event differently when sponsors ask, how do we fix that",
      "should_trigger": true
    },
    {
      "query": "Should we invent a new conference category or just be another observability conference?",
      "should_trigger": true
    },
    {
      "query": "What would our attendees do next year if our event simply didn't exist?",
      "should_trigger": true
    },
    {
      "query": "we're the third data conference in the region and we all blur together",
      "should_trigger": true
    },
    {
      "query": "Is it okay to name our biggest competitor event directly in our marketing?",
      "should_trigger": true
    },
    {
      "query": "Draft the line that says what kind of conference we are NOT",
      "should_trigger": true
    },
    {
      "query": "How do I pick the narrowest audience for my conference instead of saying it's for everyone in tech?",
      "should_trigger": true
    },
    {
      "query": "What changes strategically between a community-run event and a foundation-run one?",
      "should_trigger": true
    },
    {
      "query": "we're thinking about rebranding our summit, when is the right moment to do it",
      "should_trigger": true
    },
    {
      "query": "Our sponsors and our attendees want completely different things. How do we frame the event for both?",
      "should_trigger": true
    },
    {
      "query": "Help us decide the market category for our AI infrastructure event",
      "should_trigger": true
    },
    {
      "query": "should our hackathon lead with the prize money in all the marketing",
      "should_trigger": true
    },
    {
      "query": "map out the competitive alternatives for our conference",
      "should_trigger": true
    },
    {
      "query": "The board insists the event should be 'for anyone in tech'. Push back on that for me.",
      "should_trigger": true
    },
    {
      "query": "What can a for-profit media company honestly claim about neutrality for a conference it runs?",
      "should_trigger": true
    },
    {
      "query": "I want to interview our repeat attendees to find out what we're really competing with",
      "should_trigger": true
    },
    {
      "query": "Our event feels blurry to everyone including us. Sharpen it.",
      "should_trigger": true
    },
    {
      "query": "how do we make our single-track choice part of who we are publicly",
      "should_trigger": true
    },
    {
      "query": "Before we commission a logo or a tagline, what do we actually need to decide about the event?",
      "should_trigger": true
    },
    {
      "query": "Is our curator's taste the product here, or do we need something else to stand on?",
      "should_trigger": true
    },
    {
      "query": "We change what the conference is about every single year. Is that hurting us?",
      "should_trigger": true
    },
    {
      "query": "how do we differentiate a regional conference from the big international one on the same topic",
      "should_trigger": true
    },
    {
      "query": "What's the frame that makes our event's real strengths obvious to a first-time attendee?",
      "should_trigger": true
    },
    {
      "query": "our attendees keep telling their colleagues we're something we're not",
      "should_trigger": true
    },
    {
      "query": "Give me two or three candidate identities for our conference with the trade-offs of each",
      "should_trigger": true
    },
    {
      "query": "Should we go head to head with the category leader conference or carve out a niche?",
      "should_trigger": true
    },
    {
      "query": "explain why 'the premier conference for everyone passionate about cloud' is a bad line for us",
      "should_trigger": true
    },
    {
      "query": "We're a local chapter of a global event brand. How much of our own identity can we have?",
      "should_trigger": true
    },
    {
      "query": "how do we judge whether our conference's identity is actually working",
      "should_trigger": true
    },
    {
      "query": "Our conference name promises something the program no longer delivers. What now?",
      "should_trigger": true
    },
    {
      "query": "Which audience should we narrow down to, and which sponsors follow from that choice?",
      "should_trigger": true
    },
    {
      "query": "Design the venue decor, badge design and swag so our conference feels like a hacker event",
      "should_trigger": false
    },
    {
      "query": "Should we run single track or three parallel tracks for a 400-person conference?",
      "should_trigger": false
    },
    {
      "query": "Validate whether there's real demand for a Rust conference in Lisbon at 250 euros a ticket",
      "should_trigger": false
    },
    {
      "query": "Plan the channel mix and campaign calendar to sell 600 tickets",
      "should_trigger": false
    },
    {
      "query": "Should our event grow to 1,200 next year or hold at 700?",
      "should_trigger": false
    },
    {
      "query": "Launch our first edition from zero, what's the minimum viable edition one?",
      "should_trigger": false
    },
    {
      "query": "Write the hero section and the CTA for our conference landing page",
      "should_trigger": false
    },
    {
      "query": "Build the rate card and tier pricing for our conference sponsorships",
      "should_trigger": false
    },
    {
      "query": "What do sponsors actually get out of sponsoring our conference, perk by perk?",
      "should_trigger": false
    },
    {
      "query": "Write our conference's code of conduct and the enforcement process behind it",
      "should_trigger": false
    },
    {
      "query": "Pick a date for our conference that doesn't clash with the big vendor conferences",
      "should_trigger": false
    },
    {
      "query": "Write a positioning statement for our B2B analytics SaaS product",
      "should_trigger": false
    },
    {
      "query": "Help me position my personal brand as a developer advocate on LinkedIn",
      "should_trigger": false
    },
    {
      "query": "Write our company's brand voice guidelines and tone rules",
      "should_trigger": false
    },
    {
      "query": "Build a StoryBrand messaging framework for our website homepage",
      "should_trigger": false
    },
    {
      "query": "Which company event shape should we run, a multi-city roadshow or a single-city user conference?",
      "should_trigger": false
    },
    {
      "query": "What is our user conference funded to accomplish and which department owns the budget line?",
      "should_trigger": false
    },
    {
      "query": "Shape our set of event properties into a portfolio: conference, meetup series and hackathon",
      "should_trigger": false
    },
    {
      "query": "Design the judging rubric, criteria weights and scoring scale for our hackathon",
      "should_trigger": false
    },
    {
      "query": "How much cash should our hackathon award and should it be cash or credits?",
      "should_trigger": false
    },
    {
      "query": "Write the hackathon challenge brief teams read before they start building",
      "should_trigger": false
    },
    {
      "query": "Set up a reciprocal promotion swap with another conference in our space",
      "should_trigger": false
    },
    {
      "query": "Design the attendee email sequence from announcement through to post-event follow-up",
      "should_trigger": false
    },
    {
      "query": "Run the internal retrospective on last year's edition with the organizing team",
      "should_trigger": false
    },
    {
      "query": "Which accessibility and inclusion provisions should we commit to this edition?",
      "should_trigger": false
    },
    {
      "query": "Build the P&L with fixed and per-head cost lines for a 500-person conference",
      "should_trigger": false
    },
    {
      "query": "Design the call for papers timeline and what the published call needs to say",
      "should_trigger": false
    },
    {
      "query": "Review the 180 CFP submissions we collected and design the selection process",
      "should_trigger": false
    },
    {
      "query": "Find and negotiate a venue for 800 people with a main room and two breakouts",
      "should_trigger": false
    },
    {
      "query": "Plan our conference's social media campaign phases and posting cadence",
      "should_trigger": false
    },
    {
      "query": "Pitch tech press for coverage of our conference announcement",
      "should_trigger": false
    },
    {
      "query": "Design the expo floor layout so attendees walk past every booth",
      "should_trigger": false
    },
    {
      "query": "Set our ticket prices and the early-bird ladder",
      "should_trigger": false
    },
    {
      "query": "Design our standing organizing team and decide on a legal entity posture",
      "should_trigger": false
    },
    {
      "query": "Write a competitive analysis of our SaaS competitors' pricing pages",
      "should_trigger": false
    },
    {
      "query": "Give me 20 name ideas for our new conference",
      "should_trigger": false
    },
    {
      "query": "Design the on-site check-in desk and badge pickup flow",
      "should_trigger": false
    },
    {
      "query": "How do we keep our community engaged in the gaps between editions?",
      "should_trigger": false
    },
    {
      "query": "Write the minute-by-minute run of show for day one",
      "should_trigger": false
    },
    {
      "query": "Structure the 1:1 business meeting program between sponsors and attendees",
      "should_trigger": false
    },
    {
      "query": "Rewrite our conference tagline to be punchier, the strategy is already signed off",
      "should_trigger": false
    },
    {
      "query": "Build the AV capture plan and streaming setup for our main room",
      "should_trigger": false
    }
  ]
}
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