specup
Bidirectional bridge between ClickUp and spec-kitty feature specs. Use when the user mentions ClickUp tasks, CU- IDs, spec-kitty features, creating tasks in ClickUp, importing ClickUp context into specs, or exporting spec-kitty specs to ClickUp. Provides /specup.setup, /specup.new, /specup.import, and /specup.export commands.
What this skill does
# specup — ClickUp + spec-kitty Bridge Bidirectional bridge between ClickUp task management and spec-kitty feature specifications. ## When to activate - User mentions ClickUp tasks, CU- IDs, or ClickUp URLs - User wants to create a task in ClickUp - User wants to turn ClickUp context into a spec-kitty feature spec - User wants to push a spec-kitty feature spec to ClickUp ## Prerequisites 1. **ClickUp MCP server** must be configured and authenticated (see [references/setup.md](references/setup.md)) 2. **spec-kitty CLI** must be installed: `pip install spec-kitty-cli` 3. Run `/specup.setup` first to verify connectivity and save the default ClickUp Space ## Available commands | Command | Description | |---------|-------------| | `/specup.setup` | Verify ClickUp MCP auth and save default Space for this project | | `/specup.new [description]` | Create a ClickUp task from a short interview | | `/specup.import <reference>` | Import ClickUp task/list context into a new spec-kitty feature spec | | `/specup.export [NNN]` | Export a spec-kitty feature spec to ClickUp as a folder with docs/lists/tasks | See the individual command files in `commands/` for full workflow details. ## ClickUp reference parsing Accept these references in command arguments: - Task ID: `CU-abc123`, `#abc123`, or `abc123` - Task URL: `https://app.clickup.com/t/abc123` - List reference: `list:123456` or list URL forms - Multiple references: comma- or space-separated Normalize task IDs before MCP calls: strip `CU-`/`cu-`/`#` prefixes, extract from URLs. ## ClickUp MCP tools - `clickup_get_task` — fetch task details - `clickup_create_task` — create task - `clickup_update_task` — update task status/metadata - `clickup_create_task_comment` — add comment - `clickup_create_folder`, `clickup_create_list` — folder/list creation (export) - `clickup_create_doc` — doc creation (export, fall back to tasks if unavailable) ## Project config `/specup.setup` saves ClickUp workspace info to `.specup.json` in the project root. Other commands read this file for the default Space and parent Folder. If `.specup.json` is missing when a command needs it, prompt the user to run `/specup.setup`. ## Export sync tracking `/specup.export` persists ClickUp IDs in `FEATURE_DIR/.specup-sync.json` for idempotent updates. ## Lane-to-status mapping (export) | spec-kitty lane | ClickUp status | |-----------------|----------------| | `planned` | to do | | `doing` | in progress | | `for_review` | ready for review | | `done` | complete |
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.