backlog-md
/backlog-md
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.
- Author
- NickCrew ↗
- Repository
- Claude-Cortex ↗
- Licence
- MIT
- Last repository change
- 28.06.2026
Assessment and security
- Files in this package
- 5
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 28.06.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author description
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.
How it works
- Three Primary Use Cases
- Absolute Rules
- Implementation Plans: When Required
- Priority System (See references/priority-labels.md for details)
- Task Completion Checklist
- Essential Commands
SKILL.md preview
--- name: backlog-md description: '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.' keywords: - task tracking - backlog CLI - project management - issue filing - agent workflows - backlog - backlog md --- # 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 optional**, can be multiple: synapse-pingora, signal-horizon-ui, signal-horizon-api, etc. 5. **Custom labels allowed** as agent-useful (priority-review, performance, security, etc.) ## Implementation Plans: When Required | Scenario | Include Plan? | Reason | |----------|---------------|--------| | Deferred review issues | ✅ YES | You have audit/review context now | | Reporting found issues | ❌ NO | Implementer will plan when they work it | | Explicitly asked to plan work | ✅ YES (detailed) | Required per instruction | | Regular task work | After claiming, before coding | Don't add at creation, add after starting | **Never update an existing plan unless explicitly instructed.** ## Priority System (See references/priority-labels.md for details) - **P0**: Critical problems, major breakage - **P1**: Legitimate bugs impacting users - **P2**: Bugs, edge cases - **P3**: Nice-to-have improvements, features we want - **P4**: Backlog, future ideas Unsure about P0-P1? Label with `priority-review` and let user decide. ## Task Completion Checklist 1. Status: "In Progress" + assign self 2. Read: All fields, attached documentation 3. Plan: Add implementation plan (if not deferred from review) 4. Work: Code implementation, mark AC as you complete each 5. Notes: Append progress notes as you go 6. Summary: Add final summary (PR-style) 7. DoD: Check all definition-of-done items 8. Done: Set status "Done" ## Essential Commands ```bash # Create issue (required: title, type label, priority) backlog task create "Title" -d "Description" -l bug -p 2 --ac "AC 1" # Work a task backlog task edit 42 -s "In Progress" -a @myself backlog task 42 --plain # Read everything backlog task edit 42 --check-ac 1 # Mark AC complete backlog task edit 42 --append-notes "Progress here" backlog task edit 42 --final-summary "PR description" backlog task edit 42 -s Done # Search and filter backlog task list -s "To Do" --plain backlog search "topic" --plain ``` See `references/cli-reference.md` for complete command reference. See `references/priority-labels.md` for priority and labeling guidelines. See `references/issue-creation-guide.md` for detailed issue creation patterns.
Files in this package (5)
- SKILL.md 4 KB
- references/cli-reference.md 8 KB
- references/issue-creation-guide.md 8 KB
- references/priority-labels.md 4 KB
- references/task-workflow.md 4 KB
Versions
The database has no other skills named backlog-md.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 9011dc4a9d3c (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100ctask
Manages tasks using the ctask CLI wrapper over a local SQLite database. Use when tracking work items, creating tasks, managing dependencies, adding comments, labeling, or reviewing task status. Triggers on task tracking, ticket management, work planning, backlog management. - 95backlog
Read, work, and maintain a repo's deferred-work items in docs/backlog/, one file per item. Use when the user says "backlog", "check backlog", "what's on my backlog", "work the backlog", "address the backlog", "add to backlog", "clean up backlog", or when a review or task… - 90Backlog Management
This skill should be used when the user asks to 'add to backlog', 'update backlog', 'check backlog', 'list backlog items', 'prioritize backlog'. Provides conventions for managing the project backlog in .s2s/BACKLOG.md. - 100issue-tracking
Use when user mentions issue, bug, task, ticket, feature, backlog, tracking, or work items. Suggests using Trekker for tracking. - 100backlog
Manage this workspace's Markdown tasks through Backlog.md. Use when creating, splitting, selecting, tracking, or closing tasks, or when the user mentions the backlog, task IDs, acceptance criteria, or a Definition of Done. - 85Backlog.md
Expert guidance for Backlog.md CLI project management tool including task creation, editing, status management, acceptance criteria, search, and board visualization. Use this when managing project tasks, creating task lists, updating task status, or organizing project work.