Skip to content

samber/dev-event-organizer-skills / skills/event-growth-strategy

event-growth-strategy

Verified

Grow an established technical event edition over edition, or decide not to - the demand-headroom read, one discrete lever per edition (venue squeeze, track or day addition, venue step-up, price-led growth), the contract-risk gate on venue moves (deposits, attrition penalties, F&B minimums, long lead times), the pricing posture before scaling, and deliberate non-growth (caps, lotteries, shrinking back down) as a real strategy. Use whenever asked whether a conference or hackathon should grow, how to scale capacity, whether to add a track, a day or a venue, or how to stay small under excess demand. Do NOT use for a first launch - use samber/dev-event-organizer-skills@event-first-edition - or multi-event portfolios - use samber/dev-event-organizer-skills@event-portfolio-strategy.

FileKindSize
SKILL.mdskill md21.6 KB
evals/evals.jsonconfig27.5 KB
references/growth-case-studies.mdmarkdown10.1 KB
references/venue-and-money-mechanics.mdmarkdown5.3 KB

evals/evals.json

View on GitHub
{
  "skill_name": "event-growth-strategy",
  "evals": [
    {
      "id": 1,
      "prompt": "I organize VectorConf, a 400-seat conference on embedded ML in Rotterdam. Our first edition took about three weeks to sell out. This year's second edition sold out in 25 minutes and we ended with a 170-person waitlist, plus one sponsor emailed us out of the blue asking about next year. The convention center across town has a 900-seat hall available in 14 months and wants a 40% deposit to lock the date. The whole team is hyped. Can you help us plan the move and figure out what we'd need to make 900 work?",
      "expected_output": "A recommendation against signing the 900-seat venue: the demand-headroom gate fails on repetition (edition one sold out in weeks, not minutes), so the next step is a venue squeeze in the current hall, with the financial exposure of the proposed jump spelled out and a warning-sign watch installed.",
      "files": [],
      "expectations": [
        "Recommends against signing the 900-seat venue for the next edition",
        "Applies a demand-headroom gate and states its signals must repeat across editions, so a single fast-sellout edition is insufficient evidence",
        "Notes the first edition's three-week sellout means the sub-hour sellout has not yet repeated, which is why the gate fails here",
        "States the gate's composite threshold: sellout well under an hour, a waitlist around 30-50% of capacity, and unsolicited sponsor inbound, all required together",
        "Labels the headroom heuristic a research synthesis rather than a published industry standard",
        "Recommends venue squeeze (extracting more capacity from the current venue via layout changes) as the default next rung",
        "Notes squeeze headroom is bounded by occupancy or fire-code sign-off",
        "Warns that 900 seats sizes to aspiration and that any future step-up must be sized to the proven number plus a modest buffer",
        "Names the deposit exposure, typically 25-50% at signing, as part of the financial risk of a venue move committed long before that edition's demand is visible",
        "Mentions attrition or food-and-beverage minimum penalties owed even when attendance falls short of the commitment",
        "Checks or asks whether the 25-minute sellout was manufactured through batch ticket releases before trusting the signal",
        "Recommends exactly one growth lever for the next edition rather than several at once",
        "Pairs the recommendation with a warning-sign watch built on the four reversal benchmarks (sellout speed slowing, no-show rate rising, single-sponsor revenue share, organizers reporting the work unpleasant), each with an owner and a check date"
      ]
    },
    {
      "id": 2,
      "prompt": "Our community-run conference LatticeDays (350 attendees, database internals) turns 10 next year. We've sold out three years running, the waitlist hovers around 120, and our anchor sponsor offered an extra 40k EUR if we make the anniversary edition huge. The plan on the table: move to a 1,200-cap venue, add a second track, and bolt on a workshop day, all for edition 10. Can you sanity-check the plan and help us sequence the announcement?",
      "expected_output": "A rejection of the combined plan: one discrete lever for edition 10 with the others explicitly rejected, the 350-to-1,200 jump identified as the deleted multi-rung leap, the anniversary-plus-sponsor pressure named as the force that resurrects it, adjacency ordering, the whole-product check, mitigation pairing, and the financial gate.",
      "files": [],
      "expectations": [
        "Rejects running the venue move, track addition, and day addition together in one edition",
        "States the rule of one discrete lever per edition",
        "Treats the jump from 350 to a 1,200-cap venue as a deleted option removed from the menu entirely, not an option ranked last",
        "References the documented case of a roughly 300-person event leaping to a roughly 1,300-person format in one edition and drawing 'does not scale' verdicts from its own community",
        "Identifies the anniversary milestone plus the anchor sponsor's 40k EUR as exactly the pressure that quietly resurrects the deleted leap, and resists it",
        "Orders growth steps by adjacency, track then day then satellite city, each step small enough that credibility and playbook transfer",
        "Applies a whole-product check to any venue step-up: AV, networking infrastructure, and the volunteer bench must scale along with the seats",
        "Recommends exactly one lever for edition 10 and names the rejected rungs explicitly",
        "Pairs any track or day addition with the documented mitigation of recording everything and protecting unstructured time",
        "Names the hallway-track dilution trade-off rather than presenting the chosen lever as free",
        "Requires the pricing posture to be decided before scaling, not after",
        "Runs the financial risk gate on any venue-touching lever, covering deposits, attrition and food-and-beverage minimum penalties, and the 9-18 month lead time"
      ]
    },
    {
      "id": 3,
      "prompt": "I run SolderSocial with two friends - a hands-on hardware festival. We grew it from 140 to 280 people last year because demand was crazy (sold out in minutes, waitlist over 100). Honestly, the bigger edition was miserable to run; I caught myself dreading the production weekends and my co-organizer half-joked about quitting. Ticket demand is still hot. We're deciding between keeping 280 or pushing to 400 next year. What would you do?",
      "expected_output": "A hold-or-shrink recommendation: the organizers' own misery is a fired reversal benchmark that overrides green demand signals, deliberate shrink is presented as a documented legitimate strategy with its budget cost, and the answer routes through the reach-versus-intimacy call into the allocation-mechanism menu rather than a growth lever.",
      "files": [],
      "expectations": [
        "Treats the organizers' dread and the miserable-to-run report as a named reversal benchmark, not a mood to push through",
        "Recommends holding at or shrinking below 280 rather than growing to 400, despite the hot demand signals",
        "Presents deliberate shrink as a documented, legitimate strategy rather than an admission of failure",
        "Notes the documented shrink case accepted roughly a 50% production-budget cut as the price of going back down",
        "Notes that in documented cases organizer burnout preceded any financial or operational trigger, making it a leading indicator",
        "Forces the reach-versus-intimacy choice explicitly and warns that drifting into a middle size serves neither",
        "Presents allocation mechanisms from the non-growth menu: hold the cap, group-purchase ban, application plus lottery, deliberate shrink",
        "Names the documented bias of first-come-first-served allocation: it favors those with time and money",
        "Recommends application plus lottery specifically when the cap is about who is in the room, not just how many",
        "Treats any shrink as a pricing event too, adjusting the price to the smaller product instead of letting the old price ride",
        "Does not propose hiring staff or delegating as a way to push growth to 400 through the burnout signal",
        "Notes the waitlist doubles as the standing demand instrument while capacity holds"
      ]
    },
    {
      "id": 4,
      "prompt": "PixelForge Days is a free, no-registration community event about open-source game tooling that we run with about 30 volunteers. Last edition roughly 2,500 people showed up, popular rooms were impossible to get into, and the hallways were rammed. Demand clearly keeps growing. We're debating adding a registration system with a hard cap, or finding money to rent a bigger paid venue. Which way should we go?",
      "expected_output": "A recommendation to scale through track and room addition, the natural default for a free volunteer-run event where the financial axes collapse, with room-level overcrowding control instead of gate-level caps, the documented cost named, and the portability boundary of this lever ordering stated.",
      "files": [],
      "expectations": [
        "Identifies the event as the free, volunteer-run posture where the financial axes of the growth menu collapse",
        "Recommends adding tracks or rooms as the natural default lever for a free event",
        "Recommends against introducing registration with a hard cap as the primary fix",
        "Cites the documented free event that scaled to 8,000+ visitors and 79 tracks with no registration at all",
        "Names the documented cost of that model: chronic room overcrowding, because the capacity problem relocates from the gate to each room",
        "Recommends room-level control, staffing the door and using full-room signs, rather than gate-level caps",
        "States the free-event lever ordering holds only because there is no ticket revenue and no per-head financial risk, so it does not transfer to a ticketed conference",
        "Pairs track addition with the mitigation of recording sessions and protecting unstructured time",
        "Names hallway-track dilution as the universal documented trade-off of track addition",
        "Asks for or references demand evidence (visitor growth or a demand read) before committing the lever",
        "Asks clarifying interview questions one at a time rather than as a single batch"
      ]
    },
    {
      "id": 5,
      "prompt": "TensorTide is our 900-person applied-AI conference, fifth edition coming up. Sellout took 6 weeks two years ago and 10 weeks last year, and attendance slipped from 1,150 at peak to about 900. Most of our early attendees came through our own meetup networks, and those referrals are clearly drying up. The board's plan is to reignite buzz by adding a second track and going for 1,200 next edition. Does that plan hold up?",
      "expected_output": "A rejection of the growth push: slowing sellout is a fired reversal benchmark meaning hold or shrink, the ceiling diagnostic identifies channel decay routed to the marketing plan rather than a capacity lever, and the attendance slide is read against the documented market-wide post-pandemic contraction before any per-event diagnosis.",
      "files": [],
      "expectations": [
        "Rejects the board's plan to add a track and target 1,200 next edition",
        "Identifies the year-over-year sellout slowdown from 6 weeks to 10 weeks at flat-or-lower attendance as a firing reversal benchmark",
        "States that a fired reversal benchmark means hold or shrink the next edition, never push through with growth",
        "Runs a ceiling diagnostic distinguishing saturation, channel decay, and quality collapse before discussing any lever",
        "Diagnoses the drying-up meetup-network referrals as channel decay rather than audience saturation",
        "Routes the channel-decay problem to samber/dev-event-organizer-skills@event-marketing-plan rather than to a capacity lever",
        "Reads the attendance decline against the documented market-wide contraction, with independent in-person events running 30-40% below pre-pandemic attendance per a 2023 industry write-up",
        "States that the market-wide contraction is not evidence this event mismanaged its growth",
        "Routes the soft demand back to samber/dev-event-organizer-skills@event-market-fit for a fresh demand read before any growth work",
        "Recommends holding capacity roughly flat, with no growth lever this edition, while the acquisition channels are rebuilt",
        "Warns that buying a bigger commitment ahead of proven demand loses money even at attendance that looks respectable"
      ]
    },
    {
      "id": 6,
      "prompt": "OrbitCon (community-run, cloud-native, currently 500 seats) has sold out in under 30 minutes for three straight editions, with waitlists around 200 each time, and two sponsors approached us unprompted this year. We're finally moving to a bigger venue, roughly 700 seats. Our treasurer proposes raising ticket prices 60% since demand obviously supports it and the raise would cover the bigger venue on its own. How should we set up the move and the pricing?",
      "expected_output": "The step-up is confirmed as gated-and-passed, but the 60% raise is rejected in favor of the default posture: a public community-price commitment funded by sponsorship cross-subsidy, with supporter tier and early-bird ladder as complements, the sponsor-concentration dependency named with a self-set threshold, the financial gate run, capacity sized to proven demand, and execution handed to the venue-sourcing skill.",
      "files": [],
      "expectations": [
        "Rejects funding the step-up primarily through the 60% ticket-price increase",
        "Recommends the default posture of a public community-price commitment: individual prices held, funded by sponsorship cross-subsidy",
        "Cites the documented case that held individual prices flat while cutting student tickets around 40% across five years of venue growth",
        "States the pricing posture must be decided before the scaling, not after",
        "Presents a supporter-tier cross-subsidy, a premium tier whose surplus funds other attendees' access, as distinct from a VIP upsell",
        "Presents early-bird laddering, dated or volume-gated tiers, as complementary to the community-price commitment rather than an alternative",
        "Names the dependency the public commitment creates: it is only as durable as the sponsor base funding it, so the sponsor-concentration watch matters more once it is public",
        "Sets a self-set single-sponsor revenue-share threshold declared before the growth push as a reversal benchmark",
        "Routes exact price-setting mechanics to samber/dev-event-organizer-skills@event-ticket-pricing",
        "Confirms the demand gate passes here on repeated sub-hour sellouts, a waitlist around 40% of capacity, and unsolicited sponsor inbound",
        "Runs the financial risk gate on the venue move: deposits typically 25-50% at signing, attrition and food-and-beverage minimum penalties, 9-18 month lead time, and post-pandemic venues rarely renegotiating",
        "Sizes the new capacity to the proven number plus a modest buffer rather than an aspirational one",
        "Hands venue search and negotiation execution to samber/dev-event-organizer-skills@event-venue-sourcing"
      ]
    },
    {
      "id": 7,
      "prompt": "A growth advisor pitched us this for KernelFest, our 600-person systems conference: release tickets in eight small weekly batches so each drop sells out in minutes, screenshot the sellouts for social proof, then use the sold-out-eight-times story to justify booking a 1,000-seat venue next year. It sounds clever and costs nothing. Should we run it, and how would we structure the batches?",
      "expected_output": "A refusal: batch drops engineered for sellout optics are deleted from the menu because manufactured scarcity corrupts sellout speed, the very signal the growth gate reads, so batch-sellout screenshots cannot justify a venue step-up; the genuine headroom gate and honest demand instruments are laid out instead, with volume-gated early-bird tiers distinguished as a legitimate pricing mechanism.",
      "files": [],
      "expectations": [
        "Refuses to run the batch-release plan",
        "States that ticket drops engineered to manufacture sellout optics are deleted from the menu entirely, not merely discouraged",
        "Explains the reason: manufactured scarcity corrupts sellout speed, the exact demand signal the growth gate reads",
        "Refuses to use batch-drop sellout evidence to justify booking the 1,000-seat venue",
        "Requires the genuine headroom gate instead: organic sellout well under an hour, a waitlist around 30-50% of capacity, and unsolicited sponsor inbound, repeated across editions",
        "Distinguishes legitimate volume-gated early-bird tiers, a pricing mechanism such as a first-N-tickets tier, from batching engineered for sellout optics",
        "Notes that any event's historical sellout speed must be checked for batch manufacturing before the signal is believed",
        "Points to the waitlist as the honest standing demand instrument instead of manufactured drops"
      ]
    },
    {
      "id": 8,
      "prompt": "Our API-infrastructure company runs MeshWorks Summit, a 600-person user conference with tickets at 99 USD. Finance flagged that the event loses about 180k USD a year against ticket revenue and says growing it just deepens the loss, so they want it capped or cut. Our DevRel lead says demand is the strongest it has ever been: sold out early, big waitlist, customers asking for more seats. How should we decide whether the summit grows next year?",
      "expected_output": "A company-run analysis: growth judged on pipeline and adoption outcomes rather than ticket revenue, the ticket-revenue shortfall declined as the deciding metric, the substitutions flagged as judgment calls, sponsor-concentration risk translated into budget-owner risk, venue-contract exposure kept in full, and the standard gates (repeated demand evidence, one lever, declared watch) still applied.",
      "files": [],
      "expectations": [
        "Identifies MeshWorks Summit as company-run and applies the company-run substitutions to the financial axes",
        "Judges the growth decision on pipeline and adoption outcomes, not ticket revenue",
        "Declines to treat the 180k USD ticket-revenue shortfall as, by itself, the growth-blocking metric",
        "Flags the company-run substitutions as judgment calls rather than established event-industry practice",
        "Translates sponsor-concentration risk into budget-owner risk: the budget owner changing their mind",
        "States the venue-contract exposure still applies in full despite the funding model, covering deposits, attrition and food-and-beverage minimums, and lead time",
        "Still requires the demand-headroom evidence, repeated fast sellouts with a waitlist share and inbound interest, before choosing a lever",
        "Recommends exactly one discrete lever for the next edition if growth is chosen",
        "Installs the warning-sign watch with trigger values declared before the sale opens"
      ]
    }
  ],
  "trigger_queries": [
    { "query": "Our conference sold out in 15 minutes with a 300-person waitlist - should we book a venue twice the size?", "should_trigger": true },
    { "query": "Should our established conference add a second track next year?", "should_trigger": true },
    { "query": "We've run three editions of our developer conference. How do we decide whether year four should be bigger?", "should_trigger": true },
    { "query": "Demand for our annual hackathon keeps growing but we like it small. Can staying small be a real strategy?", "should_trigger": true },
    { "query": "Is it a mistake to double our event's capacity in one year?", "should_trigger": true },
    { "query": "Our community conference outgrew its venue. What are our options besides moving?", "should_trigger": true },
    { "query": "How risky is signing a much bigger venue for next year's edition?", "should_trigger": true },
    { "query": "We want to add a workshops day to our conference - what does that actually cost us beyond money?", "should_trigger": true },
    { "query": "Attendees keep asking us to bring our conference to a second city. When does that make sense?", "should_trigger": true },
    { "query": "Our tickets sell out instantly every year. How do we know if we should expand?", "should_trigger": true },
    { "query": "The team is exhausted but the event keeps selling out. Do we have to keep growing?", "should_trigger": true },
    { "query": "What's the smartest way to grow a 200-person tech conference to 400?", "should_trigger": true },
    { "query": "Should we cap attendance at our developer festival or let it keep growing?", "should_trigger": true },
    { "query": "We're thinking of running a ticket lottery instead of first-come-first-served for our capped event. Good idea?", "should_trigger": true },
    { "query": "Our conference got too big and lost its soul. Can we shrink it back down?", "should_trigger": true },
    { "query": "How much bigger can we safely go next edition?", "should_trigger": true },
    { "query": "waitlist is huge again this year, time for a bigger room?", "should_trigger": true },
    { "query": "Our anchor sponsor wants us to double the event for their anniversary. Should we?", "should_trigger": true },
    { "query": "When should an established conference add parallel tracks versus an extra day?", "should_trigger": true },
    { "query": "We fit 450 people in our hall last year - can we squeeze more in without moving venues?", "should_trigger": true },
    { "query": "Is one sold-out edition enough evidence to book a venue twice the size?", "should_trigger": true },
    { "query": "How do we grow the event without pricing out the community that built it?", "should_trigger": true },
    { "query": "Free community event, no tickets, rooms are overflowing - how do we scale it?", "should_trigger": true },
    { "query": "Should we keep our event at 150 people even though we could sell 300 tickets?", "should_trigger": true },
    { "query": "Our conference attendance dropped from 1,200 to 800 - did we grow too fast?", "should_trigger": true },
    { "query": "Planning next year's edition: same size, bigger, or smaller?", "should_trigger": true },
    { "query": "What signals tell us our event has real headroom to grow?", "should_trigger": true },
    { "query": "We're debating banning group ticket purchases at our capped event. Thoughts?", "should_trigger": true },
    { "query": "The organizing committee can't agree whether to stay single-track. Help us decide.", "should_trigger": true },
    { "query": "Next edition we could do a bigger venue OR a second track OR an extra day - which one first?", "should_trigger": true },
    { "query": "Do slimmer chairs and a tighter room layout count as a real growth strategy?", "should_trigger": true },
    { "query": "How do I know if my annual conference is ready for a second day?", "should_trigger": true },
    { "query": "Our event has sold out in under an hour three years running - what now?", "should_trigger": true },
    { "query": "Scaling our conference to twice the size: what could go wrong financially?", "should_trigger": true },
    { "query": "Should demand or venue availability drive our capacity decision next year?", "should_trigger": true },
    { "query": "The last edition felt too crowded but the waitlist is still 200 deep. What do we do?", "should_trigger": true },
    { "query": "We doubled last year and regret it. How do we walk it back without looking like a failure?", "should_trigger": true },
    { "query": "Growth plan for edition five of our infrastructure conference - where do we start?", "should_trigger": true },
    { "query": "Attendance keeps climbing - when do we say no to more growth?", "should_trigger": true },
    { "query": "Is it crazy to deliberately shrink a sold-out conference?", "should_trigger": true },
    { "query": "We're launching our first developer conference next spring - how many tickets should we plan for?", "should_trigger": false },
    { "query": "How do I figure out whether there's real demand for a Rust conference in my city before announcing it?", "should_trigger": false },
    { "query": "What should we charge for early-bird versus standard tickets?", "should_trigger": false },
    { "query": "Help me negotiate the venue contract terms for next year's conference.", "should_trigger": false },
    { "query": "Build me a 12-month planning timeline for our 500-person conference.", "should_trigger": false },
    { "query": "We run a conference and a podcast - should we add a hackathon to the portfolio?", "should_trigger": false },
    { "query": "Single-track or multi-track for the brand-new conference we're designing from scratch?", "should_trigger": false },
    { "query": "What overbooking ratio should we use to absorb no-shows at our free meetup?", "should_trigger": false },
    { "query": "How do we promote our conference to sell the tickets we already have?", "should_trigger": false },
    { "query": "Our waitlist process is a mess - how should day-of waitlist promotions work?", "should_trigger": false },
    { "query": "How should we structure the standing volunteer team for our recurring conference?", "should_trigger": false },
    { "query": "What's the ROI case for our company running a user conference at all?", "should_trigger": false },
    { "query": "User conference versus multi-city roadshow - which format fits our devtools startup?", "should_trigger": false },
    { "query": "How do we price our sponsorship tiers for next year?", "should_trigger": false },
    { "query": "Draft the sponsorship prospectus for our 800-person conference.", "should_trigger": false },
    { "query": "How do we keep our conference's Discord active between editions?", "should_trigger": false },
    { "query": "Growth strategy for my B2B SaaS - we're at $40k MRR and stalling.", "should_trigger": false },
    { "query": "How do I grow my tech newsletter from 2,000 to 10,000 subscribers?", "should_trigger": false },
    { "query": "Our monthly meetup needs more members - how do we grow attendance month over month?", "should_trigger": false },
    { "query": "Set up a ticket-swap promotion with a conference in the neighboring city.", "should_trigger": false },
    { "query": "How do we measure whether last edition met attendee expectations?", "should_trigger": false },
    { "query": "Run a retrospective on what went wrong at this year's edition.", "should_trigger": false },
    { "query": "Which cities should our company's first developer roadshow hit?", "should_trigger": false },
    { "query": "How big should the prize pool be for our hackathon?", "should_trigger": false },
    { "query": "We've decided to move venues - find and shortlist options for 1,000 people.", "should_trigger": false },
    { "query": "What's a reasonable catering budget per attendee for a two-day conference?", "should_trigger": false },
    { "query": "How do I reposition our conference now that a big competitor event launched?", "should_trigger": false },
    { "query": "Should our conference add a livestream so remote folks can attend too?", "should_trigger": false },
    { "query": "Write the CFP text for our new two-track program.", "should_trigger": false },
    { "query": "How many parallel sessions can our schedule grid fit across three rooms?", "should_trigger": false },
    { "query": "I organize conferences for a living - how do I level up to a senior producer role?", "should_trigger": false },
    { "query": "We want to license our conference brand to independent organizers in other countries - what should the license require?", "should_trigger": false },
    { "query": "Estimate the market size for developer conferences in Southeast Asia.", "should_trigger": false },
    { "query": "Mid-sale ticket numbers look soft this year - is the edition still viable?", "should_trigger": false },
    { "query": "What conversion rate should our event landing page be hitting?", "should_trigger": false },
    { "query": "How do we grow our open-source project's contributor base?", "should_trigger": false },
    { "query": "Should our team spin up a second annual conference on a sister topic?", "should_trigger": false },
    { "query": "What should go in the sponsor renewal deck after this year's edition?", "should_trigger": false },
    { "query": "Pick the best week next year to hold our conference.", "should_trigger": false },
    { "query": "How do we handle refunds for attendees who can't make it anymore?", "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