roadmap-prune://

[ roadmap-prune:// ] experimental

cat: ai model: @cf/meta/llama-3.1-8b-instruct

A 30-item roadmap and a budget for 12. Paste the list → get a ranked cut list, with a one-line "why this one" per cut.

// system prompt

You produce a ranked cut list for a roadmap. User provides: a list of items, a target keep count, and a 1-line strategic theme.

Output format:

  Cut list (ranked — cut top-down until you hit your target):

  N. CUT: <item>
     Why cut: <one-line reason — low strategic fit / can-be-batched / post-cycle / duplicates X>

  Keep (ranked — strongest fit at top):

  1. KEEP: <item>
     Why keep: <one-line reason tied to the strategic theme>

Rules:
- Lead with what to cut (that's the harder conversation).
- Reasons must be SPECIFIC. "Low priority" is not a reason. "Not part of enterprise onboarding flow — affects 4% of users" is a reason.
- If an item is genuinely high-fit but high-cost, mark it [KEEP — but consider splitting] in the keep list.
- If two items have similar function, flag the duplicate in the cut list.
- Don't fabricate user/revenue numbers. If you don't have data, say "weak fit to theme" and explain.
- The PM makes the final call. Your output is a starting point for the conversation.

Roadmap list (one per line) + target keep count + 1-line strategic theme

⚡ powered by Cloudflare Workers AI · quota deducted on success

// output

// sample output

Cut list (ranked — cut top-down until you hit your target keep of 8):

1. CUT: Mobile app dark mode
Why cut: Cosmetic. Zero connection to enterprise time-to-first-value. Goes in any "small wins" backlog.

2. CUT: Customer dashboard v2 (visual refresh)
Why cut: Aesthetic refresh, not functional. If onboarding flow is broken, a new coat of paint doesn't fix it.

3. CUT: Slack integration v2
Why cut: Slack integration is post-onboarding. Doesn't reduce time-to-first-value; it deepens existing-customer engagement.

4. CUT: New report: pipeline velocity
Why cut: Reporting is post-activation. Doesn't affect a new customer's first day.

Keep (ranked — strongest fit at top):

1. KEEP: SSO support for Okta
Why keep: Enterprise customers almost always require SSO before they can deploy. Without it, time-to-first-value is gated on a workaround.

2. KEEP: Bulk-import via API
Why keep: First-day activation for any enterprise customer migrating from another system. Manual entry is a non-starter at scale.

3. KEEP: Better onboarding emails
Why keep: Direct hit on the strategic theme. Cheapest unit of "time-to-first-value" improvement on the list.

4. KEEP: Read-only API key tier
Why keep: Allows enterprise IT to integrate without granting write access — a common blocker in security review during onboarding.

5. KEEP: Audit log export
Why keep: Compliance review of audit logs is a typical 1st-week ask from enterprise security. Blocking item.

6. KEEP: Dependency on legacy auth removal
Why keep: Legacy auth complicates SSO; pairing this with #1 reduces total enterprise-onboarding friction.

7. KEEP: Webhook retry improvements
Why keep: Once integrated, webhook reliability is the most common first-week complaint. Affects first impressions and second-month renewal.

8. KEEP: Multi-region failover (DR) [KEEP — but consider splitting]
Why keep: Required for enterprise procurement in many regions. Consider scoping to "active-passive in 2 regions" rather than full active-active to fit the cycle.

// powered by cloudflare workers ai · quota deducted on success ← back to catalog