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 backlogThis skill uses the workspace's default tool permissions.
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.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
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)"