Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From backlog
Guides backlog.org updates before git commits: adds progress notes to active tasks, assesses status, checks CHANGELOG.md entries, verifies design doc completion.
npx claudepluginhub farra/dev-agent-backlog --plugin backlogHow this skill is triggered — by the user, by Claude, or both
Slash command
/backlog:backlog-updateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill reminds you to update backlog.org before commits or when finishing significant work. The backlog should reflect reality BEFORE the commit is made.
Checks backlog.org for WIP tasks on session start or resume queries, surfaces handoff notes, progress updates, Claude tasks, and flags inconsistencies for quick resumption.
Validates backlog section completion in BACKLOG.md, generates milestone summaries and release notes from CHANGELOG.md, optionally squashes commits and creates git tags with auto-versioning.
Updates plan.md progress logs and checks off completed implementation steps. Use after finishing tasks, making feature commits, or indicating work done. Always asks before editing.
Share bugs, ideas, or general feedback.
This skill reminds you to update backlog.org before commits or when finishing significant work. The backlog should reflect reality BEFORE the commit is made.
Before triggering, check that backlog.org exists in the project root.
If backlog.org does not exist, do NOT trigger this skill. The project hasn't been
set up with the backlog system yet. Silently skip - don't suggest setup or explain
why the skill isn't running. Just proceed with the commit normally.
Trigger conditions (only if backlog.org exists):
git commit or create a commitInitial check: Before proceeding with the commit, read backlog.org's Current WIP section to see what's in Active.
Read the * Current WIP > ** Active section in backlog.org.
Look for tasks related to the work just completed.
If work relates to an Active task, add progress notes under that task:
*** TODO [PROJECT-NNN-XX] Task title
:PROPERTIES:
:DESIGN: [[file:...][...]]
:END:
Previous notes...
[YYYY-MM-DD] What was done, what remains.
After adding notes, consider:
/task-hold <id> <reason>/task-complete <id> [version]Do NOT mark complete automatically - that's an explicit user action via /task-complete.
If significant user-facing changes were made:
CHANGELOG.md if it exists## [Unreleased]If the work relates to an Active task with a :DESIGN: link:
:DESIGN: link to the source design doc#+STATUS: of that document* Tasks section for remaining ** TODO or ** WIP entries** DONE:
#+STATUS: to Complete?"docs/design/README.org indexThis catches completed design docs even when /task-complete wasn't used formally.
If stopping work mid-task:
:HANDOFF: property with context for next sessionOnly after backlog.org and CHANGELOG.md are updated, proceed with the commit.
| Command | When to suggest |
|---|---|
/task-complete <id> | Task is fully done |
/task-hold <id> <reason> | Task is blocked |
/task-queue <id> | Need to add a task to Active |
User: "Let's commit these changes"
Claude: "Before committing, let me check backlog.org...
I see [DAB-001-01] is in Active. We just implemented the directory
structure. Should I:
1. Add progress notes (still more to do)
2. Mark complete with /task-complete DAB-001-01
3. Proceed without updating (unrelated work)"