Backlog
- 74 installs
- 1 repo stars
- Updated August 3, 2026
- davidlee/doctrine
Creates, surveys, triages, tags, and transitions Doctrine backlog items (issue, improvement, chore, risk, idea) via the doctrine backlog CLI.
About
Drives the Doctrine backlog CLI to capture and manage latent work as typed items with status lifecycle, tags, and hard/soft dependencies. A developer uses it to intake, triage, and promote work items into slices.
- Kinds issue/improvement/chore/risk/idea with a status lifecycle
- needs (hard dep) vs after (soft ordering) dependency verbs
Backlog by the numbers
- 74 all-time installs (skills.sh)
- Ranked #1,481 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/davidlee/doctrine --skill backlogAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 74 |
|---|---|
| repo stars | ★ 1 |
| Last updated | August 3, 2026 |
| Repository | davidlee/doctrine ↗ |
What it does
Creates, surveys, triages, tags, and transitions Doctrine backlog items (issue, improvement, chore, risk, idea) via the doctrine backlog CLI.
Files
Backlog
The backlog is the work-intake home — latent work intent captured as issue, improvement, chore, risk, or idea items, triaged and promoted into slices.
needs = hard dependency. after = soft ordering (suggestion).
The CLI is the source of truth for exact flags: doctrine backlog --help
Creating new backlog items:
- [ ] Determine kind membership / validity
- [ ] Survey backlog for potential duplicates / neighbors
- [ ] Prefer expanding / improving an appropriate existing item
- [ ] Choose a clear, concise title
- [ ] Create the new backlog item
- [ ] Read & fill its template
- [ ] Tag it appropriately and consistently
- [ ] Record any dependencies and appropriate sequencing priorities
Verbs
| intent | verb |
|---|---|
| capture a new item | doctrine backlog new <kind> [title] |
| survey items | doctrine backlog list [--kind …] [--status …] [--tag …] [--all] |
| inspect one item | doctrine backlog show <ID> |
| transition status | doctrine backlog edit <ID> (prompts) |
| add/remove tags | doctrine backlog tag <ID> <tag> … [--remove <tag>] (adds positional; --remove/-d repeatable) |
| record a hard dep | doctrine backlog needs <ID> <DEP-ID> [<DEP-ID> …] |
| record soft ordering | doctrine backlog after <ID> <PREDECESSOR-ID> |
Kind membership
- issue — a bug or defect
- improvement — a tooling/UX gap or enhancement (no new feature)
- chore — housekeeping, tech-debt, refactor
- risk — unresolved work-risk (uncertain future harm needing mitigation,
acceptance, or expiry); NOT a general epistemic note
- idea — a speculative proposal, not yet scoped or committed
The work-intake membership test ([[mem.concept.backlog.work-intake-membership]]): a candidate that does not fit the work-status lifecycle (open|triaged|started|resolved|closed) is not a backlog item.
Status lifecycle
open → triaged → started → resolved → closed
- Terminal statuses (
resolved,closed) require a resolution (prompted). - Non-terminal statuses forbid a resolution (re-opening auto-clears it).
doctrine backlog edit <ID>walks the transition in-place.
Tags
Lowercased, [a-z0-9_:-]. Colon namespacing (e.g. area:backlog). Adds are positional, removes use --remove/-d — both in one call: doctrine backlog tag <ID> area:cli --remove stale.
Dependencies
- `needs` — hard prerequisite; validates every ref exists, refuses a closing
dependency cycle (names the members; nothing written). Use for "X blocks Y."
- `after` — soft sequencing preference; validates target exists, never rejects
a cycle (evicted at order time). Use for "do X before Y if convenient."
Rules
- The id prefix (
ISS-,IMP-,CHR-,RSK-,IDE-) auto-selects the kind —
no need to pass --kind to show/edit/tag/needs/after.
- A risk admitted to the backlog must be unresolved work-risk, not a general note.
- Don't hand-edit backlog TOML — use the verb. Prose (
*.md) is hand-edited. - A terminal item is hidden from
listby default; use--allor--status closed
to reveal.
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493k