Skip to content

samber/developer-platform-skills / skills/public-roadmap-strategy

public-roadmap-strategy

Verified

Decides whether and how a developer platform or API company publishes its roadmap to customers or the public - posture (none, NDA briefings, direction page, horizon roadmap, dated quarters), commitment vocabulary, what never goes public, disclaimers and sales citation rules, voting boards, and slipped or cancelled items. Use whenever the user mentions a public roadmap, a GitHub roadmap repo, a feature voting board, roadmap dates, sales promising unbuilt features, or a delayed roadmap item - even if they only say "customers keep asking what's coming". Not internal roadmap planning or prioritization. Do NOT use for triaging feature requests - use samber/developer-relations-skills@developer-feedback-loop; for deprecation notices use samber/developer-platform-skills@api-versioning-policy.

evals/evals.json

View on GitHub
{
  "skill_name": "public-roadmap-strategy",
  "evals": [
    {
      "id": 1,
      "prompt": "I'm head of product at Lattivo, a payroll-data API (private, Series B, about 1,100 self-serve accounts on click-through terms plus roughly 60 enterprise MSAs). Our reps keep promising things from the internal roadmap: last quarter two deals closed on 'SSO group sync by March', which isn't even staffed. The CEO's answer is a public roadmap 'like Stripe's' by the end of next month so everyone works from one page. Our VP Sales is fine with the page but says he won't sign anything that tells reps what they can and can't say to customers, 'that's what managers are for'. Background so you don't need to ask: the MSA has a future-functionality clause and the click-through terms do too; one internal roadmap, owned by me, reshuffled monthly; of 9 items customers were told to expect last year, 3 slipped; we have a changelog and a deprecation process but no preview phases, engineering just tags things 'beta' in Slack when they feel like it; no voting board, feedback comes through support; I can give this maybe 4 hours a month. Design our public roadmap.",
      "expected_output": "A diagnosis that the problem is sales governance, a refusal to publish any public posture until the sales leader and CEO sign the citation rule, the Stripe-shaped dated roadmap listed as ineligible with its failing conditions, no ROI claim, and the sales rules and sales-incident baseline that come first.",
      "files": [],
      "expectations": [
        "Attributes the sales-promises problem to the absence of a single externally sayable roadmap and of a rule governing what customer-facing staff may promise, not to a lack of transparency or of a page",
        "Declines to publish any public posture while the VP Sales refuses to sign the citation rule, removing public postures from the candidate set rather than ranking them lower",
        "Names fixing sales governance first, with no public page, as the first step, and names the signed citation rule as the condition that re-promotes a public posture",
        "States that publishing without the citation rule hands reps a larger catalogue to promise from, so the page amplifies the problem",
        "Requires both the sales leader and the CEO to sign the citation rule",
        "Scopes the citation rule to anyone customer-facing: reps, solutions engineers, customer success, DevRel, and executives on stage",
        "Reads 'like Stripe' as dated quarters, the most demanding posture, and tests it against the four promotion conditions",
        "Names the failing dated-quarters conditions from the given facts: no release phases exist, 3 of 9 told-to-customers items slipped, and finance has not reviewed revenue-recognition exposure",
        "Lists the Stripe-shaped dated roadmap as an ineligible candidate with the conditions that would make it eligible",
        "Makes no return-on-investment claim (no churn, trust or sales-cycle figure) and states that no independent evidence links public roadmaps to those outcomes",
        "Treats the Slack 'beta' tag as an informal flag: it becomes private preview only once access rules are written, and until then appears as a note on the item, not a phase",
        "Includes the rule that a deal depending on an unbuilt feature goes to product for a decision, never to a rep's judgment",
        "Includes the rule that legal and finance approve any roadmap item written into an order form before signature",
        "Sets a sales-incident baseline before launch (roadmap items in new order forms or side letters, roadmap escalations) to compare each quarter"
      ]
    },
    {
      "id": 2,
      "prompt": "Orbiflow here (workflow automation API, about 3,000 integrators). Our public roadmap is a GitHub project board. The item 'Webhook replay API' has sat in the 'Q3' column since spring, and engineering just told me it's Q1 at the earliest because replay was starving live delivery in load tests; they're redesigning the queue first. Two enterprise customers have 'webhook replay' written into their order forms, one of them a renewal that closes in six weeks. The plan I've drafted: (1) remove the issue from the board so it stops attracting comments, (2) mention the new timing in next month's newsletter, (3) post it on the status page as a scheduled change so it's official, (4) re-add the issue later as 'Coming Q1!'. Write the customer communication for me.",
      "expected_output": "A slip communication that keeps the item on the board with a delayed status, tells the two order-form customers privately first after a legal check, keeps the slip off the status page, and publishes a notice with reason, workaround, phase-capped timing and a condition to revisit.",
      "files": [],
      "expectations": [
        "Rejects removing the issue from the board; changes the status on the item itself to delayed (or descoped / not planned)",
        "Rejects the newsletter as the first channel for the slip",
        "Has the account owner tell both order-form customers privately, days before any public update",
        "Has legal check the private notice against the order-form terms first, because the slip may trigger notice, credit or termination rights",
        "Rejects posting the slip on the status page, stating a roadmap slip is not an incident",
        "Public notice gives a one-paragraph plain-language reason (replay starving live delivery, queue redesign)",
        "Public notice offers a workaround or alternative to use meanwhile",
        "Rejects re-adding the item as 'Coming Q1!' with no reason and a bare date",
        "Any new timing carries a release phase (for example Q1 - private preview), never a bare quarter",
        "Notifies subscribers, reactors on the item, and every account the briefing log shows saw the item",
        "Keeps the item visible on the board rather than deleting it, and if cancelled keeps it visible for at least one review cycle",
        "Flags that the original bare 'Q3' column without a phase read as general availability to buyers and reps, and recommends capping every date with a phase going forward",
        "States that the order-form entries bind regardless of the page disclaimer",
        "Structures the public notice as: update date and new status, what changed, what this means for you, workaround, what would change this, and a questions or thread link"
      ]
    },
    {
      "id": 3,
      "prompt": "Pinnacle Ledger, accounting API. I've exported our Jira roadmap and want to publish it as a GitHub roadmap repo this week, the same list we show enterprise prospects in NDA briefings (there we'll also name the partner, since it's under NDA anyway). The list: PL-301 Fix auth token replay weakness found in SOC 2 audit; PL-287 Sunset v1 ledger endpoints (we haven't told anyone yet); PL-312 Starter plan price increase plus a new Growth tier; PL-298 Native sync with Tarnbrook Bank (they haven't announced); PL-305 Custom SAML attribute mapping for Harrowgate Insurance (promised in their renewal); PL-320 Migrate to Postgres 17 and split the billing service; PL-290 Key rotation v2; PL-315 Bulk export of ledger data to the customer's warehouse; PL-322 Multi-entity consolidation. Format these as roadmap items for the repo.",
      "expected_output": "A gated list: security, unannounced deprecation, pricing, partner name, customer-specific commitment and internal plumbing removed or rewritten, surviving items written problem-first with stable IDs and a single discuss link, the same gate applied to NDA briefings, and an edge-case decider recorded.",
      "files": [],
      "expectations": [
        "Excludes PL-301 (auth token replay weakness) from both the public repo and the NDA briefings because publication tells attackers where the gap is",
        "Excludes PL-287 (v1 sunset) until it is announced through the deprecation process, and links the notice from the item once announced",
        "Excludes PL-312 (price increase and new tier) as pricing and packaging",
        "Replaces the Tarnbrook Bank name with the capability (sync with the customer's bank) until the partner announces, in the NDA briefing as well as the public repo",
        "Excludes PL-305 (Harrowgate SAML mapping) as a customer-specific commitment that belongs in that customer's order form under legal review",
        "Excludes PL-320 (Postgres 17 migration, billing service split) as internal plumbing",
        "Rewrites PL-290 'Key rotation v2' as a problem-first title (for example 'Rotate API keys without downtime')",
        "States that the public roadmap is never the internal roadmap minus a few rows and runs every candidate through the exclusion gate",
        "Applies the same exclusion gate to the NDA briefings, rejecting the plan to show the partner name under NDA",
        "Records who decides edge cases of the gate in the policy",
        "Marks passing items as public in the internal tool rather than maintaining a separate list",
        "Gives each public item a stable ID that survives from exploring to GA, and one discuss link to a feedback channel instead of comments on the item",
        "Checks the Growth tier and any other item that would cannibalize a current plan against the Osborne effect before publication"
      ]
    },
    {
      "id": 4,
      "prompt": "I run community at Tessaro, a developer platform for payments orchestration. We have a third-party voting board with about 1,400 open requests nobody has triaged in a year; the top request ('GraphQL API') has 900 votes, nearly all from free-tier accounts. We're launching a public roadmap next month and my plan is: embed the voting board in it, auto-promote the ten most-voted requests into the 'Next' column so people see we listen, shut down the old board the day the new roadmap goes live and start fresh with zero requests, and rank the Later column by vote count going forward. We don't have anyone whose job is triage; I do it when I can. Can you write the launch plan?",
      "expected_output": "A launch plan with locked items and one feedback channel, the untriaged board frozen read-only behind a dated notice rather than closed overnight, no vote-driven promotion, votes weighted by segment, community requests labelled apart from plans, and a format-change notice covering open requests.",
      "files": [],
      "expectations": [
        "Rejects launching with an embedded voting board while no named triage owner and no running feedback loop exist",
        "Recommends locked roadmap items, each linking to one feedback channel, as the default surface",
        "States the three-option ranking explicitly: on effort and value, separate board > reactions on items > locked items; on efficiency, locked items > reactions on items > separate board",
        "Rejects auto-promoting the ten most-voted requests into Next",
        "Treats vote counts as one weighted signal, never the ranking, weighting by segment and account value, and notes that 900 free-tier votes do not stand for paying customers",
        "Labels community requests apart from vendor plans (a Proposed label or equivalent) so a popular request never reads as a plan",
        "Freezes the existing board read-only behind a dated notice pointing to the single feedback channel, instead of closing it",
        "Rejects shutting the old board down on launch day with no notice; any closure needs a dated notice plus a migration or read-only archive of open requests",
        "States that the 1,400 untriaged requests go to the feedback loop and do not gate the roadmap launch",
        "Gives any board that stays open a not planned state with reasons and a named triage owner",
        "Plans the board's exit before launch, naming a forum closed without notice (UserVoice / Office 365) as the expectation-debt write-off to avoid",
        "Writes the transition as a format-change notice: a dated table of what changes, a 'what's not changing' section, and what happens to open requests",
        "Routes per-request triage and dedup to a feedback-loop process rather than designing it inside the roadmap launch plan"
      ]
    },
    {
      "id": 5,
      "prompt": "COO at Brightmoor Systems, a private Series C data-pipeline API company, raising again next spring. We're about to publish a dated quarterly roadmap. Counsel is on vacation for three weeks, so I need a review before they're back. Our page disclaimer so far is a paragraph I adapted from a public company's forward-looking-statements boilerplate, the one about 'risks and uncertainties described in our SEC filings' and the Private Securities Litigation Reform Act safe harbor. Our MSA has the 'purchases not contingent on future functionality' clause; the self-serve click-through terms (about 2,000 accounts) don't mention it. Four enterprise order forms name roadmap items by name. We're also planning to drop the roadmap page straight into the investor data room. What needs to change before we launch?",
      "expected_output": "A pre-launch legal review: safe-harbor language stripped for a private company and the customer sentence kept, a four-element disclaimer, the self-serve coverage gap and existing order forms handled through counsel and finance, ASC 606 review as a precondition of dated quarters, data-room reuse routed to counsel, and a four-party approval gate.",
      "files": [],
      "expectations": [
        "Removes the securities safe-harbor and SEC-filings language from the page disclaimer because Brightmoor is a private company",
        "Keeps only the customer sentence from forward-looking-statements practice: purchase decisions should rest on features available today",
        "Disclaimer carries all four elements: informational only, not a commitment or promise to deliver, timing and content may change at the company's discretion, not to be relied on for purchasing decisions",
        "Flags that the MSA clause does not cover the 2,000 self-serve accounts because the click-through terms carry no equivalent",
        "Has counsel decide whether to add the clause to the self-serve terms and to new and renewing contracts, with written sign-off on the residual risk for existing contracts",
        "States that the clause cannot exclude misrepresentation or deceptive-advertising claims in many jurisdictions, so the page's own accuracy stays the residual exposure",
        "Inventories the four order forms naming roadmap items before launch, with counsel and finance reviewing each and the account owner contacting the customer",
        "States that a feature written into an order form binds regardless of the disclaimer and the MSA clause",
        "Brings finance in before publishing dated quarters, naming ASC 606 (IFRS 15 outside US GAAP) and the risk that a dated, specified upgrade becomes a separate performance obligation deferring revenue",
        "Names finance's revenue-recognition review as a precondition of the dated-quarters posture, not an optional follow-up",
        "Routes the investor data-room reuse of the roadmap to counsel rather than approving it",
        "Defers final disclaimer and clause wording to counsel, presenting its output as shapes rather than legal advice",
        "Repeats the disclaimer on the first slide of any NDA briefing deck, not in a footer",
        "Gates publication on explicit approval by product, sales leadership, counsel and finance"
      ]
    },
    {
      "id": 6,
      "prompt": "The CEO asked me to look into a public roadmap for our API platform. Where do we start?",
      "expected_output": "A single interview question asking why now, offered as multiple choice, with no posture, vocabulary or tool recommended yet.",
      "files": [],
      "expectations": [
        "Asks a question before proposing anything",
        "Asks exactly one question in the reply",
        "The question asked is the trigger question (why now), not budget, tooling or audience",
        "Offers the trigger as multiple choice including sales promising unbuilt features, customers asking what's coming, a competitor publishing one, transparency as brand, and a slip that hurt trust",
        "Recommends no posture, vocabulary, tool or surface in the reply",
        "Keeps the reply to the question itself, without a preamble walking through the full workflow or listing the postures"
      ]
    },
    {
      "id": 7,
      "prompt": "Product lead at Dunmore Analytics, a data-enrichment API. A competitor published a public roadmap last week and leadership wants ours live in three weeks. Everything you'd probably ask: private company, no fundraise planned; customers are mostly banks and insurers on negotiated MSAs whose procurement teams ask for roadmap evidence, plus a smaller self-serve tier; they genuinely plan budgets around our release timing, which is why leadership wants dated quarters. One internal roadmap, I own it, it changes monthly; 1 of 12 items customers were told to expect slipped last year. We run private preview / public preview / GA, have a changelog and a deprecation process. The MSA carries the future-functionality clause, the self-serve terms too, no order forms name roadmap items; sales leadership and the CEO will sign a citation rule. Feedback: a GitHub Discussions category that DevRel triages every week. I can spend about 2 hours a month on upkeep after launch; setup time is whatever fits in three weeks. Finance has never looked at any of this. What should we publish?",
      "expected_output": "The four posture rankings stated and re-ranked for an enterprise-heavy audience, NDA briefings bundled with a small public page, dated quarters withheld on the missing finance review with the condition that unlocks it, item count sized from the two-hour budget, the two-review-cycle rule reconciled with the deadline, and two or three candidate bundles with a recommendation.",
      "files": [],
      "expectations": [
        "States the four posture rankings out loud (effort, value, compliance cost, efficiency) across the six postures, not only a recommendation",
        "Re-ranks for the enterprise-heavy audience: customer briefings move to second on value and third on efficiency",
        "Promotes NDA customer briefings alongside a public page because regulated procurement asks for roadmap evidence, presenting it as a bundle of two rungs",
        "Promotes the direction page or a small horizon roadmap because of the three-week deadline and the two-hour monthly budget, and says which interview answer moved which rung",
        "Withholds dated quarters, naming the missing finance revenue-recognition review as the failing promotion condition even though phases, the low slip rate and budget-planning buyers hold",
        "Names the condition that promotes dated quarters later: finance review of ASC 606 / IFRS 15 exposure",
        "Sizes the public item count from the two-hour budget using the planning assumption of about a quarter hour per item per monthly review (roughly eight items), and says to replace it with the first month's actual time",
        "Flags that publishing only after at least two internal review cycles with decided statuses conflicts with the three-week deadline, and says how to resolve it",
        "Applies the same sales rules to the NDA briefings as to the page: disclaimer on slide one and a briefing log recording account, date, items and attendees",
        "Presents two or three candidate bundles with trade-offs and one recommendation, listing the dated-quarters candidate as ineligible with its missing condition",
        "Argues the decision on stated trade-offs for the competitor trigger, with no claimed ROI",
        "Notes that the weekly-triaged Discussions category promotes the interactive-board rung with DevRel as the named triage owner, while locked items linking to that category stay the default",
        "Names a single owner and a backup with the monthly hours, never 'product' collectively, and shows a last-reviewed date on the page"
      ]
    },
    {
      "id": 8,
      "prompt": "Sorrelton (observability API) is relaunching our GitHub roadmap repo and I'm settling the vocabulary. Draft: columns Now / Next / Later, which I'll credit to the book Product Roadmaps Relaunched in the README; 'Next' defined as 'within about two months'; a quarter label on every card including ideas we're still researching, since GitHub's own roadmap puts quarters on in-design items; card titles like 'Rate limiter v3', 'Auth revamp', 'Dashboard 2.0'; anything that won't happen gets removed to keep the board clean; cards get a 'beta' tag whenever engineering says a thing is in beta. And rather than keeping old cards around, each quarter I'll rewrite ROADMAP.md from scratch so it's always current. Sanity-check and finalize the vocabulary.",
      "expected_output": "A corrected vocabulary: Now/Next/Later credited correctly, buckets defined by engineering state, dates only from private preview with a phase attached, problem-first titles, a visible not-planned state instead of removals, beta mapped to a note until access rules exist, snapshots instead of a rewritten file, stable IDs, a Proposed label and a changelog close.",
      "files": [],
      "expectations": [
        "Credits Now / Next / Later to Janna Bastow (ProdPad), not to the book Product Roadmaps Relaunched",
        "Rejects defining Next as 'within about two months'; buckets are defined by engineering state (for example in build with a named owner) so no bucket smuggles in a date",
        "Removes quarter labels from research and in-design cards; dates appear only on items at private preview or later",
        "Caps every date that remains with a phase (for example 'Q1 - private preview')",
        "Acknowledges that GitHub dates in-design items by quarter column and states the stricter rule is this policy's deliberate choice",
        "Rewrites 'Rate limiter v3', 'Auth revamp' and 'Dashboard 2.0' as problem-first titles",
        "Rejects removing cards that won't happen; publishes a visible not planned or cancelled state with a reason, kept for at least one review cycle",
        "Treats the 'beta' tag as an informal flag: it maps to private preview only once access rules are written, and until then is a note on the card, not a phase",
        "Rejects rewriting ROADMAP.md from scratch each quarter; snapshots the roadmap at each review so promises can be compared with delivery",
        "Defines on the page, for each state, what a customer may rely on",
        "Adds a separate label (Proposed or equivalent) for community ideas so they never read as vendor plans",
        "Gives every card a stable ID that survives from exploring to GA",
        "Closes each shipped card with a changelog link (a shipped label or equivalent)"
      ]
    },
    {
      "id": 9,
      "prompt": "Head of product at Ashgrove, a contract-data API (private, about 180 enterprise customers on MSAs with the future-functionality clause, almost no self-serve). At our user conference last October the CEO said on stage that multi-region data residency would be live 'in the first half of the year', to about 300 attendees. It's November, it's not built, and nobody has said a word about it. Two renewals that closed since then reference residency in their order forms. The CEO now wants to repair the relationship by shipping a public roadmap page by the end of the month with residency shown as 'Next'. We don't run preview phases yet, we do have a changelog, no voting board, and I have about 6 hours a month for this. How do we get the page out?",
      "expected_output": "A plan that communicates the residency slip first as a launch precondition, tells the two order-form customers privately after a legal check, treats the keynote as a committed item, keeps residency undated on any page, adds a citation rule covering executives on stage, and bundles NDA briefings for the enterprise audience without promising the page rebuilds trust.",
      "files": [],
      "expectations": [
        "Sequences the communication of the residency slip before any roadmap page launches, as a launch precondition",
        "Treats the keynote statement as a committed item under the playbook's definition (customers were told to expect it), not as an informal remark",
        "Applies the slip steps to the pre-page commitment: a status (delayed / descoped / not planned), a one-paragraph reason, a workaround, notification of those who were told, and continued visibility",
        "Has the account owners tell the two renewal customers privately, days before any public statement, after legal checks the notice against their order-form terms",
        "States that adding a roadmap page before the slip is handled multiplies the next slip",
        "Rejects showing residency as Next with any date or GA implication while no release phase exists; if shown, it carries an engineering-state status and no timing",
        "Includes a citation rule covering executives on stage: no dates in keynotes unless the public page shows that date",
        "Makes no claim that the page will rebuild trust, arguing on stated trade-offs instead",
        "Tracks slip rate using the committed-item definition before any promotion to dated quarters",
        "Promotes NDA customer briefings alongside or instead of the page for the enterprise-heavy audience"
      ]
    }
  ],
  "trigger_queries": [
    { "query": "Should we publish a public roadmap for our API?", "should_trigger": true },
    { "query": "Our sales team keeps promising features that aren't built yet - how do we stop that?", "should_trigger": true },
    { "query": "Set up a GitHub roadmap repo like AWS containers for our platform.", "should_trigger": true },
    { "query": "Now/Next/Later or dated quarters for our developer roadmap?", "should_trigger": true },
    { "query": "Write the disclaimer for our roadmap page.", "should_trigger": true },
    { "query": "We told customers webhooks v2 would ship in Q3 and it's slipping - how do we announce it?", "should_trigger": true },
    { "query": "Customers keep asking what's coming next.", "should_trigger": true },
    { "query": "Should we let developers vote on roadmap items?", "should_trigger": true },
    { "query": "The CEO wants a roadmap 'like Stripe's'. Is that feasible for us?", "should_trigger": true },
    { "query": "What should never appear on a public roadmap?", "should_trigger": true },
    { "query": "Can sales reps cite our public roadmap in proposals?", "should_trigger": true },
    { "query": "Our roadmap page hasn't been updated in eight months - fix it or kill it?", "should_trigger": true },
    { "query": "Do we need to involve finance before publishing dated features?", "should_trigger": true },
    { "query": "How do we cancel a roadmap item we announced publicly?", "should_trigger": true },
    { "query": "A competitor just published their roadmap and leadership wants ours out in a month.", "should_trigger": true },
    { "query": "Should our roadmap live on a public GitHub project board or a web page?", "should_trigger": true },
    { "query": "Draft our public roadmap policy document.", "should_trigger": true },
    { "query": "We're open-core and our issues are already public - do we still need a roadmap page?", "should_trigger": true },
    { "query": "How do we move from a quarterly PDF roadmap to a continuous public one?", "should_trigger": true },
    { "query": "our enterprise prospects want to see the roadmap under NDA, how do we run those briefings", "should_trigger": true },
    { "query": "What vocabulary should our roadmap use: exploring, preview, GA?", "should_trigger": true },
    { "query": "Is it safe to put a quarter next to an item that's still in design?", "should_trigger": true },
    { "query": "Our roadmap voting board has 2,000 untriaged requests - freeze it, close it or keep it?", "should_trigger": true },
    { "query": "Reps are screenshotting our internal roadmap into deals.", "should_trigger": true },
    { "query": "Does the MSA's future-functionality clause cover self-serve customers who read our roadmap?", "should_trigger": true },
    { "query": "Write the sales one-pager on what reps can say about upcoming features.", "should_trigger": true },
    { "query": "How do we keep cancelled roadmap items visible without confusing people?", "should_trigger": true },
    { "query": "Should roadmap items be problem-first or feature-named?", "should_trigger": true },
    { "query": "What's the Osborne effect risk of announcing our v3 engine on the roadmap?", "should_trigger": true },
    { "query": "How often should we review the public roadmap, and who owns it?", "should_trigger": true },
    { "query": "We want transparency as a brand value - what does a public roadmap actually cost to maintain?", "should_trigger": true },
    { "query": "Which roadmap items should link to the changelog when they ship?", "should_trigger": true },
    { "query": "help, we deleted a roadmap item and customers noticed", "should_trigger": true },
    { "query": "Should we publish a direction page instead of a dated roadmap?", "should_trigger": true },
    { "query": "A feature in an enterprise order form is now not happening - how do we tell them and the public?", "should_trigger": true },
    { "query": "What do we measure to know the roadmap is being kept honest?", "should_trigger": true },
    { "query": "Support gets fifty 'when will X ship' tickets a month - would a roadmap help?", "should_trigger": true },
    { "query": "How much of our internal Jira roadmap can go public?", "should_trigger": true },
    { "query": "Our roadmap says 'beta' on three items but we have no beta program - what do we show?", "should_trigger": true },
    { "query": "A partner integration is on our internal roadmap; can we list it publicly before they announce?", "should_trigger": true },
    { "query": "How do we say 'not planned' on a roadmap without looking dismissive?", "should_trigger": true },
    { "query": "Plan the migration from our old UserVoice-style board to a locked GitHub roadmap.", "should_trigger": true },
    { "query": "Should we show our public roadmap page to investors in the data room?", "should_trigger": true },
    { "query": "Triage this week's feature requests and reply to each requester.", "should_trigger": false },
    { "query": "Dedupe our feature-request backlog across support, Discord and sales.", "should_trigger": false },
    { "query": "Write the deprecation notice for sunsetting /v1 next June.", "should_trigger": false },
    { "query": "How much notice do we owe integrators before a breaking change?", "should_trigger": false },
    { "query": "Add Sunset headers to our legacy endpoints.", "should_trigger": false },
    { "query": "Write the release notes for this week's deploy.", "should_trigger": false },
    { "query": "What should the changelog entry say for the new rate limits?", "should_trigger": false },
    { "query": "Define what 'private preview' promises customers: SLA, change notice, data terms.", "should_trigger": false },
    { "query": "Design the beta allowlist for the new endpoint.", "should_trigger": false },
    { "query": "When does a public preview graduate to GA?", "should_trigger": false },
    { "query": "Where should the roadmap link sit in our developer portal navigation?", "should_trigger": false },
    { "query": "Draft the joint roadmap with our technology partner for the integration.", "should_trigger": false },
    { "query": "Write this month's build-in-public update for our devlog.", "should_trigger": false },
    { "query": "Post a status page update for the ongoing API outage.", "should_trigger": false },
    { "query": "Announce planned maintenance for Saturday's database migration.", "should_trigger": false },
    { "query": "Prioritize our internal roadmap for next quarter using RICE.", "should_trigger": false },
    { "query": "Help me run quarterly planning with the engineering leads.", "should_trigger": false },
    { "query": "Build the OKRs for the platform team.", "should_trigger": false },
    { "query": "Which SDK languages should we build first?", "should_trigger": false },
    { "query": "Write the migration guide from REST v1 to v2.", "should_trigger": false },
    { "query": "Design the retry and dead-letter policy for our outbound webhooks.", "should_trigger": false },
    { "query": "Move our npm publishing from long-lived tokens to trusted publishing.", "should_trigger": false },
    { "query": "Should we build an official VS Code extension?", "should_trigger": false },
    { "query": "Write our open-source library's release policy: SemVer vs CalVer, LTS branches.", "should_trigger": false },
    { "query": "Plan our product launch on Product Hunt.", "should_trigger": false },
    { "query": "Draft the press release for our new API.", "should_trigger": false },
    { "query": "Our GitHub stars are flat - what do we do?", "should_trigger": false },
    { "query": "Set up Discussions on our SDK repository.", "should_trigger": false },
    { "query": "Negotiate SLA credits and penalties into the enterprise MSA.", "should_trigger": false },
    { "query": "Review our terms of service for GDPR compliance.", "should_trigger": false },
    { "query": "Plan a 12-week engineering roadmap in Jira for the mobile team.", "should_trigger": false },
    { "query": "Build a Gantt chart for the engineering roadmap.", "should_trigger": false },
    { "query": "Write a roadmap for my career to become a staff engineer.", "should_trigger": false },
    { "query": "Create a learning roadmap for a junior developer picking up Go.", "should_trigger": false },
    { "query": "Draw the technology roadmap slide for the board deck.", "should_trigger": false },
    { "query": "Design a customer advisory board program.", "should_trigger": false },
    { "query": "Set up a feature-flag system for gradual rollouts.", "should_trigger": false },
    { "query": "Write the public postmortem for last week's outage.", "should_trigger": false },
    { "query": "How do we price the new enterprise tier?", "should_trigger": false },
    { "query": "Draft the email announcing our pricing change to customers.", "should_trigger": false },
    { "query": "Design the error response body for our API.", "should_trigger": false },
    { "query": "Our Stack Overflow tag is full of unanswered questions.", "should_trigger": false },
    { "query": "Create a roadmap template in Notion for our product team.", "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: 471kUpdated 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