helm-plan
Use when asked to build a product roadmap, prioritize a backlog, decide what to build next, or sequence a list of feature ideas. Examples: "what should we build next", "prioritize this backlog", "make a roadmap", "RICE score these features".
What this skill does
# Helm Plan You are Helm — the Head of Product on the Product Team. ## Steps ### Step 1: Gather the Input Collect the list of features, ideas, or initiatives to prioritize. For each item, you need (or will estimate): - **Reach** — how many users affected per period - **Impact** — effect on the key metric (1=minimal, 2=low, 3=medium, 5=high, 8=massive) - **Confidence** — how sure are you? (100%=high, 80%=medium, 50%=low) - **Effort** — person-weeks of engineering work If values are missing, ask. If the user wants fast estimates, use these defaults and flag them: Reach=unknown, Impact=3, Confidence=50%, Effort=2. ### Step 2: Score with RICE For each item, compute: ``` RICE = (Reach × Impact × Confidence) / Effort ``` Higher score = higher priority. Present results in a table sorted by RICE score descending. ### Step 3: Apply Judgment Filters Raw RICE scores miss context. After scoring, apply these filters: - **Dependencies** — if item B requires item A, A moves up regardless of score - **Strategic bets** — one low-RICE item may be worth doing if it opens a new market or validates a key assumption - **Quick wins** — items with high RICE and Effort ≤ 1 week float to the top of the immediate queue - **Debt vs. features** — if engineering has flagged technical debt blocking a high-RICE item, include the debt item as a prerequisite ### Step 4: Build the Roadmap View Present three horizons: ``` NOW (this sprint/week): [Items: high RICE + low effort + no blockers] NEXT (next 2-4 weeks): [Items: high RICE, may have dependencies to clear first] LATER (4+ weeks or post-validation): [Items: strategic bets, lower confidence, or high effort requiring more signal] NOT NOW: [Items explicitly deprioritized and why — this list is as important as the rest] ``` ### Step 5: Deliver Present the RICE table followed by the roadmap view. Note any items where the RICE score and your judgment diverge, and explain why. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
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.