team-coordinator
Multi-teammate orchestration. Maintains shared TaskList, assigns work by file-ownership glob, synthesizes findings, blocks Stop on incomplete tasks.
What this skill does
# team-coordinator Skill that backs `/shannon:team`. Lead-side orchestration. ## Behavior contract 1. Parse team charter (markdown): extract roles, file-ownership globs, dispatch dependencies. 2. Create TaskList entries per role + per task via `TaskCreate`. 3. Spawn N teammates via `Task` tool. Each spawn fires `subagent-governance-inject` (PreToolUse:Task) — IRON RULE delivered to teammate stderr at startup. 4. Poll TaskList: track in_progress, completed, blocked. 5. On teammate completion: read teammate report under `plans/reports/`, integrate into running synthesis. 6. On file-ownership violation (detected via post-edit grep against ownership glob): refuse and re-assign. 7. On Stop event: `stop-task-semantics` hook blocks if any teammate task still `in_progress`. ## When to use - 3+ independent workstreams that can parallelize - Tasks with clear file-ownership boundaries (no overlap) - Need shared TaskList visibility across teammates ## When NOT to use - Single workstream → use `/shannon:cook` - Workstreams share files heavily → sequential is safer - Exploratory / unknown decomposition → use `/shannon:plan` first ## File ownership rule (LOAD-BEARING) Every task description must include `File ownership: <glob>`. Teammates refusing to honor ownership are halted by lead and re-tasked. No exceptions. ## Iron rules - No partial verdicts. Wait for ALL teammates before final synthesis. - Verdict writer reads ALL evidence, not just inventories. - Contradictions escalate to lead; lead resolves with citation, never invents.
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.