How do I install the Backlog Update skill?

Run npx skillmds add majiayu000/backlog-update in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Backlog Update safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Backlog Update?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Backlog Update free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Backlog Update?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Backlog Update by majiayu000 — Agent Skill

Name: Backlog Update
Rating: 4.2 (5 reviews)
Author: majiayu000

Backlog Update

Reminder to update backlog.org before commits or when finishing significant work. Use before committing changes, after completing implementation from plan mode, or when wrapping up a work session. This skill ensures the project's task tracking in backlog.org stays current with actual progress. Trigger when about to commit, exiting plan mode, or when user says "done", "let's commit", "wrap up", or similar.

majiayu000 638e471 2 files · 3.5 KB Updated Sep 9, 2026 567 repo stars

File contents

Backlog Update Reminder

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.

When to Offer This Workflow

Trigger conditions:

About to run git commit or create a commit
Exiting plan mode after completing implementation
User says "done", "finished", "let's commit", "wrap up"
Completing a significant piece of work

Initial check: Before proceeding with the commit, read backlog.org's Current WIP section to see what's in Active.

Workflow

1. Check Active Tasks

Read the * Current WIP > ** Active section in backlog.org.

Look for tasks related to the work just completed.

2. Update Progress Notes

If work relates to an Active task, add progress notes under that task:

*** TODO [PROJECT-NNN-XX] Task title
:PROPERTIES:
:SOURCE: [[file:...][...]]
:END:

Previous notes...

[YYYY-MM-DD] What was done, what remains.

3. Assess Task Status

After adding notes, consider:

Still in progress? Leave as TODO/WIP, notes are sufficient
Blocked? Suggest running /task-hold <id> <reason>
Complete? Suggest running /task-complete <id> [version]

Do NOT mark complete automatically - that's an explicit user action via /task-complete.

4. Check CHANGELOG.md

If significant user-facing changes were made:

Read CHANGELOG.md if it exists
Check if the change is already documented under ## [Unreleased]
If not, suggest adding an entry:
- Added - New features
- Changed - Changes to existing functionality
- Fixed - Bug fixes
- Removed - Removed features

5. Update Handoff Notes

If stopping work mid-task:

Update :HANDOFF: property with context for next session
Include: what was tried, where stuck, what to try next

6. Then Commit

Only after backlog.org and CHANGELOG.md are updated, proceed with the commit.

Related Commands

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

Example

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)"

---name: backlog-updatedescription: Reminder to update backlog.org before commits or when finishing significant work. Use before committing changes, after completing implementation from plan mode, or when wrapping up a work session. This skill ensures the project's task tracking in backlog.org stays current with actual progress. Trigger when about to commit, exiting plan mode, or when user says "done", "let's commit", "wrap up", or similar.--- # Backlog Update Reminder 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. ## When to Offer This Workflow **Trigger conditions:** - About to run `git commit` or create a commit - Exiting plan mode after completing implementation - User says "done", "finished", "let's commit", "wrap up" - Completing a significant piece of work **Initial check:** Before proceeding with the commit, read backlog.org's Current WIP section to see what's in Active. ## Workflow ### 1. Check Active Tasks Read the `* Current WIP` > `** Active` section in backlog.org. Look for tasks related to the work just completed. ### 2. Update Progress Notes If work relates to an Active task, add progress notes under that task: ```org *** TODO [PROJECT-NNN-XX] Task title :PROPERTIES: :SOURCE: [[file:...][...]] :END: Previous notes... [YYYY-MM-DD] What was done, what remains. ``` ### 3. Assess Task Status After adding notes, consider: - **Still in progress?** Leave as TODO/WIP, notes are sufficient - **Blocked?** Suggest running `/task-hold <id> <reason>` - **Complete?** Suggest running `/task-complete <id> [version]` Do NOT mark complete automatically - that's an explicit user action via `/task-complete`. ### 4. Check CHANGELOG.md If significant user-facing changes were made: - Read `CHANGELOG.md` if it exists - Check if the change is already documented under `## [Unreleased]` - If not, suggest adding an entry: - **Added** - New features - **Changed** - Changes to existing functionality - **Fixed** - Bug fixes - **Removed** - Removed features ### 5. Update Handoff Notes If stopping work mid-task: - Update `:HANDOFF:` property with context for next session - Include: what was tried, where stuck, what to try next ### 6. Then Commit Only after backlog.org and CHANGELOG.md are updated, proceed with the commit. ## Related Commands | 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 | ## Example ``` 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)" ```

Frequently asked questions