task-backlog

Manage task creation, status tracking, and execution across agents in the journal-kernel system.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/elliottpolk/journal-kernel --skill task-backlog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-backlog
Source: https://github.com/elliottpolk/journal-kernel/tree/main/.agentic/skills/task-backlog
Command: npx skills add https://github.com/elliottpolk/journal-kernel --skill task-backlog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a structured approach to capturing, managing, and executing tasks across various agents within the journal-kernel system.

Core Features & Use Cases

  • Cross-Agent Task Capture: Record tasks from any session for deferred action.
  • Task Querying: List and prioritize tasks across different agents.
  • Task Execution: Mark tasks as in progress, completed, or dropped, with proper context management.
  • Use Case: For instance, during a session, the 'work' agent captures a task for future consolidation, and the 'personal' agent queries and executes tasks based on the user's requests.

Quick Start

To capture a task for the 'work' agent, simply use the command: 'Capture task for work: [description]'

Frequently Asked Questions about task-backlog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage cross-agent task tracking in an AI-assisted documentation system?

Cross-agent task tracking is managed by capturing tasks from any session, assigning contextual execution parameters, and updating task status across various agents within the journal-kernel system. It supports prioritization, status updates, and deferred execution.

Can I capture a task in one agent session for another agent to execute later?

Yes, you can capture a task for deferred action from any active session. For example, the 'work' agent can record a task, and the 'personal' agent can query and execute that task based on your requests using contextual assignment.

What is the best way to prioritize and update task status across multiple agents?

Prioritizing and updating task status across agents requires querying the existing task backlog, reordering by priority, and marking tasks as in progress, completed, or dropped while maintaining proper context management throughout the process.

Does contextual execution require specific dependencies for agent-based task management?

No specific dependencies are required for contextual execution in agent-based task management. The system operates standalone using scripts to handle task creation, status tracking, and context assignment within the journal-kernel environment.

How do I start tracking tasks across agents using the journal-kernel system?

To start tracking tasks across agents, use the command 'Capture task for [agent]: [description]' to record a task. The system then allows you to query, prioritize, and execute tasks across different agents with proper context management.

Are there limitations to cross-agent task management in an AI-assisted documentation environment?

Cross-agent task management is designed specifically for the journal-kernel system and focuses on task creation, status tracking, and execution. It is limited to collaborative task management within this AI-assisted documentation environment and does not support external platform integration.