← ClaudeAtlas

blocked-sweeplisted

Scan all project mirrors for blocked or stalled tasks. For each blocker, reads the latest comments to check if already resolved, then optionally posts a clarification request to Asana via bainbot. Designed to run at the start of a session or on Hermes schedule.
markbaindesign/bain-studio · ★ 0 · AI & Automation · score 63
Install: claude install-skill markbaindesign/bain-studio
# Blocked Sweep Scan all active project mirrors for blocked or stalled tasks. Read comments to see if the blocker was already answered. Post clarification requests via bainbot where needed. ## Steps ### 1. Discover all project mirrors Read `/media/data/dev/bain-studio/studio/projects.json` to get the list of active project paths. For each path, check if `{path}/.claude/asana-mirror.md` exists. ### 2. Parse each mirror for blocked tasks A task is blocked if ANY of the following: - `Section: STALLED` - `Blockers:` field is non-empty and not a "none" variant (see matching rules below) - Task is in `DOING` or `IN PROGRESS` section and is stale (see stale rules below) **Blocker matching rules:** Strip punctuation and lowercase the Blockers field before comparing. Treat the following as "no blocker": - `none identified` - `none` - empty string So `"None identified."`, `"None."`, `"None Identified."` all count as no blocker. **Stale rules:** A task is stale only if it is in `DOING` or `IN PROGRESS` section AND the Progress field contains a date that is 7+ days old. Exclude auto-stamps: if Progress starts with `"Checked "` it is a bainbot audit stamp, not a real progress note — do not use it to calculate staleness. If Progress is empty or only contains a Checked stamp, the task is not considered stale unless it has been in DOING for an unusually long time (use Modified date if available). **Exclude DONE section tasks entirely.** Tasks in DONE are complete — never flag them