xc-breakdown-problem
Breaks problems and goals into independent parts that can be tackled separately. Use this whenever the user states a problem or goal that has multiple dimensions or parts.
What this skill does
# Introduction ## Goal Break a complex problem or goal into sub-parts for clearer understanding. Focus on what the problem IS, not how to solve it. ## Method Propose a breakdown, then iteratively validate and refine using a context-blind agent until success criteria are met. Expect multiple passes. ### Success Criteria - **MECE** — Sub-parts are mutually exclusive and collectively exhaustive - **Uniformity** — Sub-parts are at the same level of abstraction - **Precision** — Each sub-part is well-defined - **Problem-focused** — Sub-parts describe problems or goals, not solutions - **Actionable** — Each sub-part can be worked on independently ## Part 1: Evaluate - Think about whether this skill actually applies to the current situation. If it doesn't, skip silently and move on. - If it does, suggest it to the user conversationally. Briefly explain why you think it's relevant. Wait for confirmation before proceeding. ## Part 2: Workflow - Across all steps, focus on what the problem or goal IS, not how to solve it. ### 1. Propose breakdown - Think about the problem or goal the user has shared. Use conversation history for relevant details and clues. Do not look for additional context in files or memory. - Propose a breakdown into sub-parts. Self-critique against the success criteria. Describe what you observe, not why it happens — stay far from causal or solution framing. ### 2. Validate - Spawn a context-blind agent (Haiku task agent). Name it: "Validate breakdown". Provide the agent with the original problem/goal and your proposed breakdown. Ask the agent to validate against the success criteria and surface any gaps or inconsistencies. ### 3. Revise - If the validator surfaced issues, revise the breakdown. Make the smallest changes that address the issues. Preserve the structure of the original breakdown. Do NOT rewrite from scratch. - Send the revised breakdown back to the validator (step 2). Repeat until the validator passes all success criteria. ## Final output - Present breakdown: Present the sub-parts to the user naturally in conversation. For each sub-part, provide a brief description of what it covers. - Direct conversation: Ask the user whether the breakdown looks right and wait for next steps. ## Related skills - **xc-clarify-framing** — If the problem or goal is ambiguous, run xc-clarify-framing first to clarify before decomposing.
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.