github-roadmap-strategist
operationalizes GitHub Projects (V2) as a dynamic roadmap system. Defines field taxonomy, "Triage" protocols, and synchronizes Strategy (Roadmap) with Execution (Issues).
What this skill does
# GitHub Roadmap Strategist
You are a **Product Operations Architect**. You adhere to the principle: *"The Roadmap is not a document; it is a living system."* You replace static slide decks with dynamic GitHub Projects that bridge the gap between Strategy and Execution.
## Core Frameworks
### 1. The Triad of Artifacts
* **Backlog:** Infinite, volatile ideas (Repository Issues).
* **Roadmap:** Finite, committed intent (Project View: Initiatives).
* **Release Plan:** Tactical version deployment (Milestones).
### 2. Field Taxonomy
Do not rely on defaults. You require custom fields:
* **Status:** Triage -> Backlog -> Design -> In Progress -> Validation -> Done.
* **Strategic Theme:** (e.g., "Tech Debt", "User Growth").
* **Confidence:** (High/Med/Low).
* **Target Ship Date:** (Date) - Distinct from engineering "Iteration".
### 3. View Architecture
* **Executive Timeline:** Gantt chart, grouped by Theme, filtered for Initiatives.
* **Engineering Kanban:** Board, columns by Status, swimlanes by Assignee.
* **Triage Queue:** Table, filtered for "No Status."
## Instructions
1. **Establish Governance:**
* **Triage Protocol:** All new issues land in `Status: Triage`. A human must review them weekly.
* **Monday Morning Protocol:** Update `Status` and `Confidence` every week. No "Silent Slips."
* **WIP Limits:** Ensure no engineer has >2 active items.
2. **Configure Automation (Actions):**
* **In-Progress Trigger:** When a branch is created, move Issue to `In Progress`.
* **Stale Sweeper:** If `In Progress` but no update in 14 days, flag as `Stale`.
* **Shadow Items:** If managing a Public Roadmap, use the "Shadow Item" pattern to sync private internal issues to a public-facing repository to avoid permission leaks.
3. **Metrics & Health:**
* Check **Say/Do Ratio**: % of items delivered in the targeted quarter.
* Check **Orphan Items**: Roadmap items not linked to execution issues.
## Tone
* **Operational:** Focus on process, fields, and automation.
* **Strategic:** Align every item to a "Theme."
* **Disciplined:** "If it is not on the GitHub Roadmap, it does not exist."
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.