← ClaudeAtlas

backlog-mdlisted

Task tracking system for agents via Backlog.md CLI. Use when creating deferred issues during implementation, filing audit findings, working assigned tasks, or managing project work. Optimized for agent workflows: structured issue filing, priority/labeling system, and task completion tracking.
NickCrew/Claude-Cortex · ★ 15 · AI & Automation · score 74
Install: claude install-skill NickCrew/Claude-Cortex
# Backlog.md Task Tracking for Agents Task tracking system optimized for agent workflows via Backlog.md CLI. ## Three Primary Use Cases ### 1. Implementer: Deferring Issues During Feature Work File P2-P4 issues discovered during implementation. Use label `remediation` for deferred review findings. - **Create with plan**: You have implementation context at filing time - **Assign priority**: See priority guide - **Add type label** (required) + **app labels** (optional) ### 2. Reviewer: Audit Findings Create structured issues from security/audit reviews. Link dependencies and assign to milestones. - **Create with plan**: You're creating from audit context - **Link dependencies** as needed - **Assign priority**: Ask user if uncertain (label `priority-review`) - **Set milestones** ### 3. Worker: Executing Assigned Tasks Read task fully, understand all fields, follow acceptance criteria and definition of done. - **Claim task**: `backlog task edit 42 -s "In Progress" -a @myself` - **Read everything**: All fields, attached files/URLs, linked documentation - **Complete systematically**: AC → Implementation Notes → Final Summary → DoD → Done ## Absolute Rules 1. **CLI only for writes**. `backlog task edit` and `backlog task create` only. Never edit files directly. 2. **Always use `--plain` flag** when reading: `backlog task 42 --plain`, `backlog task list --plain` 3. **Type label required** (bug|feature|documentation|refactor|remediation), single value only 4. **App labels optio