roadmap-planning
Create outcome-based roadmaps using Now/Next/Later instead of Gantt charts. Use when asked to create a roadmap, plan quarterly, organize milestones, or figure out what to build over the next few months. Anti-date, anti-feature-list, pro-outcome.
What this skill does
Build roadmaps organized by outcomes, not feature lists. A roadmap answers "what problems are we solving and in what order?" — not "what features will we ship and when?" Dates on a roadmap beyond 6 weeks are fiction. Treat them that way. ## Now / Next / Later Three time horizons, decreasing in certainty: ### Now (Committed — this cycle) - Currently in progress or about to start - Fully shaped: problem defined, solution scoped, appetite set - Team assigned, expected to ship this cycle - 1-3 items maximum ### Next (Shaped — next 1-2 cycles) - Problem validated, solution partially shaped - Not yet assigned to a team - May change based on what we learn from "Now" items - 3-5 items maximum ### Later (Raw — ideas worth exploring) - Problems we believe are real but haven't validated - No solution shaped yet - Will be promoted to "Next" when evidence supports it, or killed - No limit, but prune quarterly ## Roadmap Items Are Outcomes, Not Features Each roadmap item is framed as a problem to solve or an outcome to achieve: **Bad (feature-list roadmap):** - Build team collaboration features - Add CSV export - Redesign settings page **Good (outcome-based roadmap):** - Reduce time-to-first-value for team signups from 15 min to under 5 min - Enable users to get their data out without contacting support - Reduce settings-related support tickets by 50% The solution emerges during shaping, not during roadmap planning. ## Shape Up Cycle Planning For teams using Shape Up cycles: 1. **Betting table:** Leadership reviews shaped pitches and bets on what to build next cycle. Not everything gets picked. 2. **Cool-down:** 1-2 weeks between cycles for bug fixes, exploration, and shaping future work. 3. **No carry-over:** Work that doesn't ship in a cycle is not automatically carried over. It must be re-pitched. ## Presenting the Roadmap Keep it to one page or one screen. If your roadmap needs scrolling, it's too detailed. Format as a simple table: | Horizon | Outcome | Evidence | Status | |---------|---------|----------|--------| | Now | Reduce onboarding drop-off to under 30% | 5 interviews, 60% current drop-off | In progress, week 2/3 | | Next | Enable self-serve data export | 12 support tickets/month | Shaped, needs team | | Later | Multi-workspace support | 3 enterprise prospects requested | Unvalidated | ## Guidelines - CRITICAL: NEVER put dates on roadmap items beyond 6 weeks. You don't know and pretending you do erodes trust. - NEVER build a feature-list roadmap. Organize by outcomes and problems. - ALWAYS limit "Now" to 1-3 items. If you're working on 8 things, you're finishing none of them. - NEVER let "Later" items skip to "Now" without shaping and evidence. - ALWAYS prune "Later" quarterly. Kill items that haven't gained evidence in 3 months. - ALWAYS review and update the roadmap at the start of every cycle, not just quarterly. - NEVER present a roadmap without evidence for each item. A roadmap without evidence is a wish list. --- *Built on Shape Up (Basecamp) cycle planning and the Now/Next/Later framework. Skills from [productskills](https://github.com/assimovt/productskills).*
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.