← ClaudeAtlas

asana-to-harnesslisted

Turn one Asana task into an implementation plan for an AI coding harness, open a GitLab issue with the plan as its description, and leave a trigger comment (e.g. @claude). Used standalone ("turn this Asana task into a harness issue") or invoked by the asana-sweep skill.
YCyrus/asana-sweep · ★ 2 · AI & Automation · score 63
Install: claude install-skill YCyrus/asana-sweep
# Asana task → harness plan → issue + trigger comment Convert a single Asana task into a plan an AI coding harness can execute directly, then open a GitLab issue and trigger the harness. Usually invoked with a task number/keyword (interactive) or a resolved spec (from asana-sweep). ## Configuration Read `asana-sweep.config.json` in the repository root (same file the sweep skill uses): - `gitlab.project` — GitLab project path for issues. - `gitlab.base_branch` — branch new work starts from; state it in the plan. - `harness.trigger_comment` — the comment text that wakes the harness (e.g. `@claude please implement per the issue description above`). **Know your harness's trigger rule**: many harnesses (including GitLab webhook-based ones) only fire on **comments (notes)** — a mention inside the issue *description* does nothing. So the flow is always "create issue (description = plan) → post a separate trigger comment". - `plans_dir` — where local plan drafts are stored. ## Flow ### 1. Read the Asana task - Find the task by number/keyword and get its `gid` (on free workspaces use `asana_get_my_tasks` + filtering; search endpoints require a paid workspace). - Fetch it with `notes,html_notes,permalink_url` **plus its stories/comments** — client clarifications and links to prior MRs often live in comments, not the description. - Also fetch image attachments for the task (and its parent) with the plugin's bundled helper, then Read every path it prints: `asana-fetch-attachments <