backlog
Manage the project's tactical work-item backlog under `docs/backlog/` — add new items, list/filter active items by status or priority, show full details, update status or priority, and archive done items into `_done/<version>/` at release time. Use this skill whenever the user wants to capture a bug/refactor/feature idea, check what's outstanding ("what's left in v1?", "what bugs are open?", "show me all p0/p1 work"), update an item's status, or otherwise interact with the backlog. Also use when the user says "/backlog", "加到 backlog", "记一下这个 bug", "看看 backlog", "what's in the backlog", or after fixing/shipping something to mark it done. Read `docs/backlog/README.md` once at the start of any session to load the current schema.
camtrik · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add camtrik/agent-trail --skill backlogAbout this skill
name: backlog
description: Manage the project's tactical work-item backlog under docs/backlog/ — add new items, list/filter active items by status or priority, show full details, update status or priority, and archive done items into _done/<version>/ at release time. Use this skill whenever the user wants to capture a bug/refactor/feature idea, check what's outstanding ("what's left in v1?", "what bugs are open?", "show me all p0/p1 work"), update an item's status, or otherwise interact with the backlog. Also use when the user says "/backlog", "加到 backlog", "记一下这个 bug", "看看 backlog", "what's in the backlog", or after fixing/shipping something to mark it done. Read docs/backlog/README.md once at the start of any session to load the current schema.
Backlog Workflow
Tactical work items live in docs/backlog/ as one markdown file per item, with YAML frontmatter for machine-readable fields. The slug (filename minus .md) is the stable ID.
Read docs/backlog/README.md once per session — it has the canonical schema and status semantics. The notes below are about how to operate on items, not what they look like.
Sub-actions
This skill exposes five sub-actions. Detect intent from the user's phrasing; if ambiguous, ask which one.
add— capture a new item from a natural-language descriptionlist— show outstanding items, grouped or filteredshow <slug>— print one item in fullupdate <slug>— change frontmatter fields (status, priority, type, title)archive <version>— move allstatus: doneitems to_done/<version>/(called by/ship-release; rarely invoked directly)
Action: add
Goal: capture a new item with minimum friction. The user is usually describing a problem mid-conversation — don't make them fill out a form.
Step 1 — Extract the essentials from what the user said
From the user's prompt, infer:
type— feat (new capability), fix (bug), refactor (restructure without behavior change), chore (deps/build/CI), docstitle— short, English, title case. If the user spoke Chinese, translate the title to English (the body can stay in whatever language they used)priority— guess from urgency cues ("生产挂了" → p0, "什么时候有空" → p3); default p2slug— derived from title, kebab-case, 2-4 words
If the type or priority is genuinely unclear, ask one focused question. Don't ask for everything; default reasonable values.
Step 2 — Check for duplicates
Before writing, check whether a similar item exists:
ls docs/backlog/*.md | xargs grep -l '<keyword>' 2>/dev/null
If something close already exists, tell the user and ask: append to existing, or create new anyway?
Step 3 — Write the file
Use the schema from docs/backlog/README.md. Fill in:
- Required frontmatter:
type,title,status: todo,priority,created: <today> - Empty
branch:/worktree:(populated later by/worktree-flow) - Body sections: at minimum
## Description. Add## Acceptance criteriaif you can plausibly write 2-3 checkboxes from the user's description; otherwise leave it for them to flesh out later.
Use today's date in YYYY-MM-DD format. The user's environment provides today's date.
Step 4 — Report
One line: "Added docs/backlog/<slug>.md (type, priority). To start work: /worktree-flow new <slug>."
Don't preview the whole file — the user can read the file if they want to.
Action: list
Goal: show what's outstanding at a glance. Default view is grouped by status, sorted by priority within group.
Step 1 — Collect
ls docs/backlog/*.md
For each file, parse frontmatter — at minimum: type, title, status, priority, branch. Treat _done/ and README.md as out of scope (don't include).
A simple parse with awk/grep works for these fixed fields. If a file's frontmatter is malformed, surface it as a warning at the end of the listing — don't crash.
Step 2 — Group and format
Default output: a compact table or grouped list. Aim for one line per item; the user is skimming.
WIP (1)
p1 feat filter-by-project feat/filter-by-project
TODO — p0 (0)
TODO — p1 (2)
p1 fix session-list-search
p1 refactor source-labels-centralization
TODO — p2 (3)
p2 fix qoder-cost-extraction
p2 fix qoder-updated-time
p2 refactor package-size-optimization
REVIEW (0)
DONE — pending archive (0)
Skip empty sections only when listing the full backlog; if the user filtered explicitly (/backlog list --priority p0), show "(none)" for transparency.
Step 3 — Filters
Honor common filters from natural language:
- by status: "show wip" / "what's todo" / "any done items pending archive"
- by priority: "p0 only" / "high priority"
- by type: "bugs" / "refactors"
- by source/area: search title + body (
grep -l)
Multiple filters AND together.
Action: show
cat docs/backlog/<slug>.md
Pretty-print: frontmatter as a small box, then the body markdown. Don't summarize — the user wants the full thing.
If the slug doesn't resolve, suggest near matches:
ls docs/backlog/ | grep -i <partial>
Action: update
Goal: change one or more frontmatter fields. Common transitions:
todo → wip— happens automatically via/worktree-flow new, rarely manualwip → review— manual when implementation is done but not mergedreview → done— manual or auto via/worktree-flow cleanup* → wontfix— manual decision; require a reason, add it to the body
How to edit
Use the Edit tool to change frontmatter values in place. Preserve the exact YAML formatting — don't reorder keys or change quoting style.
If transitioning to wontfix, append a ## Why not section to the body with the user's reason. If they didn't give one, ask.
If transitioning to done manually (not via worktree-flow), prompt the user to confirm the linked branch is merged. Don't silentl