← ClaudeAtlas

asana-sweeplisted

Scheduled sweep of incomplete Asana tasks assigned to you — triage into auto/ask/skip, dedupe against existing work, then call asana-to-harness to open GitLab issues that trigger an AI coding harness. Built for headless scheduled runs (claude -p); also runs interactively, with --dry-run support.
YCyrus/asana-sweep · ★ 2 · AI & Automation · score 63
Install: claude install-skill YCyrus/asana-sweep
# Asana sweep → triage → dedupe → hand off to asana-to-harness Periodically sweep the incomplete Asana tasks assigned to you, decide which ones can safely become issues for an AI coding harness, and only report the rest — never act on ambiguity. The per-task work (write plan → open issue → trigger the harness) is delegated to the `asana-to-harness` skill; this skill only does **sweep + triage + dedupe + trigger**. ## Configuration (read this first, every run) All behavior comes from `asana-sweep.config.json` in the repository root of the current working directory. **If the file is missing, stop immediately** and tell the user to copy `asana-sweep.config.example.json` from this plugin's repo and fill it in. Do not guess values. Key fields (see the example file for the full shape): - `workspace_gid` — the Asana workspace to sweep. - `paid_workspace` — if `false`, the workspace is on Asana's free tier: **only `asana_get_my_tasks` (User Task List endpoint) works; `asana_search_tasks` returns `payment_required`.** Do not retry search endpoints on free workspaces. - `window_days` — processing window (see Flow step 2-5). - `gitlab.project` / `gitlab.base_branch` — where issues are opened. - `asana_projects` — **optional** list of Asana projects (boards) to sweep, by gid or by name. Empty/absent = sweep everything assigned to you (see Flow step 1). - `repo_scope` — what counts as "work this harness can actually do" (see triage gate 0). Always applied, whether or not `asana_proje