Stats

Actions

Tags

Help us improve

Share bugs, ideas, or general feedback.

claude-tasks-sync | backlog

Skill

claude-tasks-sync

Cross-references Claude Tasks in backlog.org under Current WIP section when creating tasks, spawning subagents, or completing multi-step work. Requires existing backlog.org file.

developer-tools

$

npx claudepluginhub farra/dev-agent-backlog --plugin backlog

Popularity

Parent stars

24

Parent forks

2

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/backlog:claude-tasks-sync

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

This skill ensures Claude Tasks are cross-referenced in backlog.org. The backlog is the universal hub - humans read it directly, agents follow links to their native primitives.

SKILL.md

137 lines · ~968 tokens

Similar Skills

backlog-resume

24

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.

backlog

68

Manages tasks-plans/ workspace by adding actionable items to backlog, ideas for exploration, or dated references. Organizes files by topic into subfolders, processes queued work via subcommands.

secondbrain-task

11

Creates sequential tasks with priority, status, due dates in secondbrain's .claude/data/tasks YAML shards. Activates on 'create task', 'add todo', or similar requests.

1 file

Stats

LanguageEmacs Lisp

Parent stars24

Parent forks2

MaintenanceExcellent

Last CommitMar 1, 2026

Actions

View Source View Plugin View on GitHub View README

Tags

Help us improve

Share bugs, ideas, or general feedback.

Claude Tasks Sync

This skill ensures Claude Tasks are cross-referenced in backlog.org. The backlog is the universal hub - humans read it directly, agents follow links to their native primitives.

Prerequisites

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 - Claude Tasks can still be used normally, they just won't be synced to a backlog.

Core Principle

Sync means cross-references, not content replication.

When Claude creates a Task, ensure backlog.org has an entry with :CLAUDE_TASK: link
Don't duplicate task descriptions - just ensure the link exists
Humans read backlog.org; agents follow links to Claude Tasks

When to Trigger

Trigger conditions:

Creating Claude Tasks (via TodoWrite or task management)
Spawning subagents that will create their own Tasks
After /queue-design-doc creates a Task List
When completing work that involved Claude Tasks

Workflow

1. When Creating Claude Tasks

After creating one or more Claude Tasks:

Read backlog.org's * Current WIP > ** Active section
For each Claude Task created:
- Check if a matching backlog entry exists (by task ID or title)
- If exists: add :CLAUDE_TASK: property if missing
- If not exists: create minimal backlog entry with link

Minimal backlog entry:

*** TODO Task title
:PROPERTIES:
:CLAUDE_TASK: <task-list-id>/<task-id>
:EFFORT: M
:HANDOFF:
:WORKED_BY: claude-code
:END:

2. When Tasks Have Design Doc Origin

If the task originated from a design doc (has :DESIGN: property), preserve it:

*** TODO [DAB-012-08] Create sync skill
:PROPERTIES:
:DESIGN: [[file:docs/design/012-claude-tasks-integration.org::*Tasks][DAB-012-08]]
:CLAUDE_TASK: <task-list-id>/<task-id>
:EFFORT: M
:END:

Both links coexist - :DESIGN: for the spec, :CLAUDE_TASK: for agent coordination.

3. When Subagents Create Tasks

If spawning subagents:

Note the Task List ID being used
After subagent completes, check for any new Tasks created
Ensure each new Task has a corresponding backlog entry

4. Link Format

The :CLAUDE_TASK: property format:

:CLAUDE_TASK: <task-list-id>/<task-id>

Or for referencing just the Task List:

:CLAUDE_TASK_LIST: <task-list-id>

What NOT To Do

Don't copy task descriptions from Claude Tasks to backlog
Don't mirror status changes automatically
Don't create duplicate entries - one per task
Don't remove :DESIGN: or other existing links

Example

Claude: [Creates Task "Implement authentication" via TodoWrite]

[Skill triggers]

Claude: "I've created a Claude Task for this work. Let me ensure
it's tracked in backlog.org...

Added to backlog.org Active section:
*** TODO Implement authentication
:PROPERTIES:
:CLAUDE_TASK: abc123/task-001
:EFFORT: M
:WORKED_BY: claude-code
:END:

The task is now visible to both humans (via backlog) and agents
(via Claude Task)."

Related Skills

Skill	Relationship
`backlog-update`	Updates existing entries; this creates new ones
`backlog-resume`	Reads `:CLAUDE_TASK:` links on session start

Related Commands

Command	Relationship
`/task-start`	Creates Claude Task at execution time
`/queue-design-doc`	Creates Task List for all design doc tasks