ralph-specum-triage
This skill should be used only when the user explicitly asks to use `$ralph-specum-triage`, or explicitly asks Ralph Specum in Codex to triage a large effort into multiple specs.
What this skill does
# Ralph Specum Triage You are a **coordinator, not a triage analyst** -- delegate decomposition work to a `triage-analyst` sub-agent. ## Contract - Epic data lives under `specs/_epics/<epic-name>/` - Track the active epic in `specs/.current-epic` - Do not guess on ambiguous epic or spec names - Triage produces a plan for multiple specs. It does not implement them ## Action 1. Check `specs/.current-epic`. If an active epic exists, summarize status and offer resume, details, or a new epic. 2. Resolve or create the epic directory and initialize `research.md`, `epic.md`, `.progress.md`, and `.epic-state.json` as needed. 3. **Delegate** triage work to a `triage-analyst` sub-agent. The sub-agent runs the four-stage triage flow: - exploration research on seams, constraints, and existing boundaries - brainstorming and decomposition into specs - validation of dependencies, contracts, and scope - finalization of epic outputs Do NOT decompose or generate epic content yourself. 4. Assemble `epic.md` by aggregating and formatting the sub-agent's output (without altering substantive content) into: - vision and scope - spec list with goals and size - dependency graph - interface contracts and sequencing notes 5. Persist `.epic-state.json` with each spec, its status, and dependencies. 6. Set `specs/.current-epic` to the active epic name. 7. Show the next unblocked spec and route back to `$ralph-specum-start` for per-spec execution. ## Output Shape The result should make it clear: - what belongs in each spec - which specs can start now - which specs are blocked by dependencies - what contracts must stay stable across specs ## Stop Behavior - **Without `--quick`**: STOP HERE. Display the epic summary and approval prompt. Do NOT continue to the next spec until the user explicitly approves or requests changes. - **With `--quick`**: Continue directly to the first unblocked spec. ## Response Handoff - After writing `epic.md`, name `epic.md` and summarize the epic plan briefly. - End with exactly one explicit choice prompt: - `approve current artifact` - `request changes` - `continue to the next spec` - Treat `continue to the next spec` as approval of `epic.md`.
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.