clickup-backfill

Included with Lifetime

$97 forever

Ensure every .orchestra/work/ item has a corresponding ClickUp ticket. Creates missing tickets and writes the ID back into the PRD frontmatter. Use when backfilling a repo's work items into ClickUp.

General

What this skill does


# ClickUp Backfill

Scan all work items in `.orchestra/work/` and ensure each has a corresponding ClickUp ticket. Create missing tickets and write the ID back into the PRD frontmatter. Do not modify ticket status.

## Step 1 — Resolve Credentials

Read the ClickUp API key:

```bash
grep 'api_key:' ~/.config/workspace/bench/config.yaml | awk '{print $2}'
```

If not found, check `CLICKUP_API_KEY` env var. If neither exists, stop and tell the user.

## Step 2 — Resolve List ID

Find the `clickupListId` for this repo:

1. Determine the repo name — use `$ARGUMENTS` if provided, otherwise infer from the current directory name
2. Read `config/projects/<repo-name>.json` (relative to BENCH_ROOT, typically `../..` from `apps/web/` or the monorepo root)
3. Extract `clickupListId` from the JSON

If no `clickupListId` is configured for this repo, stop and tell the user which field to add to `config/projects/<repo-name>.json`.

## Step 3 — Scan Work Items

Use Glob to find all work item folders:

```
.orchestra/work/*/
```

Skip `TEMPLATES` and any folder starting with `.`.

For each folder, find the primary document in this order: `prd.md`, `spec.md`, `README.md`, first `.md` file found.

Read the frontmatter of the primary document and extract:
- `ticket` — existing ClickUp ID (if present, skip this item)
- `title` — work item title (or extract from the first `# Heading` in the file)
- `status` — current status

## Step 4 — Identify Missing Tickets

Build two lists:
- **Already linked**: work items with a `ticket` field in frontmatter
- **Missing**: work items with no `ticket` field, or where the ticket field is empty

Report the count of each before proceeding.

## Step 5 — Create Missing Tickets

For each work item in the Missing list:

1. Extract the title and a short description (first non-heading paragraph of the PRD, or the Objective section if present)
2. Create a ClickUp task:

```bash
curl -s -X POST "https://api.clickup.com/api/v2/list/<LIST_ID>/task" \
  -H "Authorization: <API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "<title>",
    "description": "<description>"
  }'
```

3. Extract the `id` field from the response
4. Write the ticket ID back into the primary document's frontmatter:
   - If frontmatter exists: add or update the `ticket:` line
   - If no frontmatter: prepend a frontmatter block with `ticket`, `status`, and `created_on`

## Step 6 — Report

Print a summary table:

| Work Item | Action | Ticket ID |
|-----------|--------|-----------|
| folder-name | already linked | 86eXXXXXX |
| folder-name | created | 86eYYYYYY |
| folder-name | created | 86eZZZZZZ |

State how many tickets were created and how many were already linked. Do not modify ClickUp status.

Files: 1

Size: 3.1 KB

Complexity: 12/100

Category: General

Source: https://github.com/mpazaryna/agentic-factory/tree/main/skills/clickup-backfill

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce 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).

Generalscripts

relationship-science-coach

Included

Use 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.

Generalscripts

building-sf-integrations

Included

Salesforce 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).

Generalscripts

venue-templates

Included

Access 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.

Generalscripts

let-fate-decide

Included

Draws 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.

Generalscripts

net-ops

Included

Cross-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.

Generalscripts