backlog
/backlog
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.
- Author
- Archont561 ↗
- Repository
- qgis-agent-harness ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.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
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.
Original author description
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.
How it works
- Run the CLI in this workspace
- Non-interactive use
- Task workflow
- Shell quoting
SKILL.md preview
--- name: backlog description: 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. --- Backlog tasks live as Markdown under `backlog/`. Use the CLI for task metadata so IDs, dependencies, filenames, and status stay consistent. Do not invent tasks when the backlog has no matching work. ## Run the CLI in this workspace `backlog.md` is a root Bun workspace dependency. Run it through Pixi's separate Bun environment: ```sh pixi run -e bun bunx backlog.md <command> ``` Install the locked Bun workspace first if dependencies are missing: ```sh pixi run -e bun install-js ``` The current backlog is initialized at `backlog/config.yml` in filesystem-only mode. If the directory is absent in a fresh checkout, initialize it without Git integration: ```sh pixi run -e bun bunx backlog.md init "QGIS SDK Workspace" --no-git --defaults --integration-mode none --backlog-dir backlog ``` ## Non-interactive use Read commands can launch an interactive UI. In an agent or CI shell, always use `--plain` for reads and `--json` when parsing output. Avoid bare `board`, `browser`, or task-detail commands without a non-interactive flag. ```sh pixi run -e bun bunx backlog.md task list -s "To Do" --plain pixi run -e bun bunx backlog.md search "<query>" --plain pixi run -e bun bunx backlog.md task <id> --plain ``` ## Task workflow 1. Read the task and its acceptance criteria before implementation. 2. When work is approved, claim and plan it using `task edit`; record progress in notes rather than comments. 3. Verify each acceptance criterion with evidence. Do not mark an unproven criterion complete. 4. Close a completed task with the CLI and include a concise final summary. Archive cancelled or duplicate work rather than deleting its history. 5. After a merge, update task status only when the merge and required validation are confirmed. Create tasks with the CLI, for example: ```sh pixi run -e bun bunx backlog.md task create "Title" -d "Description" --ac "First,Second" -l area --priority high ``` For command syntax, use `pixi run -e bun bunx backlog.md <command> --help` and consult [`REFERENCE.md`](REFERENCE.md). ## Shell quoting - Quote arguments containing literal backticks to prevent command substitution. - For multi-line notes, pass actual newlines or append one line at a time; do not use shell-specific `$'...'` quoting. - Use comments only for review discussion; use notes and final summaries for execution progress.
Files in this package (2)
- REFERENCE.md 5 KB
- SKILL.md 3 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · Archont561/qgis-agent-harness | 100 | MIT |
| Ovid/paad | 100 | MIT |
| Ovid/paad | 100 | MIT |
| Ovid/paad | 100 | MIT |
| gtlpanda/PandaStack | 100 | MIT |
| SergioLizana/Dynamo | 100 | MIT |
| bitIO/wheelhouse | 100 | MIT |
| umputun/cc-thingz | 100 | MIT |
| Alter-ai/skill-lab | 100 | MIT |
Database snapshot: 13.11.2026 · package version 8705681ec66b (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
- 100task-planning
Plan and organize software development tasks effectively. Use when breaking down features, creating user stories, or planning sprints. Handles task breakdown, user stories, acceptance criteria, and backlog management. - 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. - 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. - 100om-backlog
Turns a product brief (its Scope and Key flows) or a spec's Phasing into a tracker backlog — epics, stories with acceptance criteria, tasks — with stable ids in titles, epic checklists, and Epic links, filing every issue through om-prepare-issue so dedupe, SDLC labels, and… - 100backlog-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. - 100taskplanner
Manage tasks stored in .tasks markdown files. Use when the user mentions tasks, backlog, planning, priorities, sprints, or asks to create, implement, update, list, or move TaskPlanner tasks. Prefer TaskPlanner MCP tools when they can access the active workspace and otherwise…