tracking-tasks

Enforce task lifecycle states across coding sessions and context boundaries.

2|Updated Jan 29, 2026

Search Tags:#workflow #productivity #coding #task-tracking #session-resume #task-lifecycle #context-boundaries

Ready to run

npx skills add https://github.com/oryanmoshe/agent-skills --skill tracking-tasks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tracking-tasks
Source: https://github.com/oryanmoshe/agent-skills/tree/main/skills/tracking-tasks
Command: npx skills add https://github.com/oryanmoshe/agent-skills --skill tracking-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces disciplined task tracking across context boundaries. Use when starting any coding task, receiving a new user request mid-work, planning multi-step work, discovering sub-tasks or issues, before context compaction, switching between tasks, or resuming a previous session. Skip for purely informational questions with no code changes.

Core Features & Use Cases

Task lifecycle management: pending, in_progress, completed to maintain task history across sessions.
Deviation protocol: create new tasks for discoveries while keeping current work in progress.
Pre-compaction checkpoint: ensure all discovered work is captured before context compaction.

Quick Start

Start each session by creating an initial task for the user request and then advance tasks with TaskCreate, TaskUpdate, and TaskList as you work.

Frequently Asked Questions about tracking-tasks

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

FAQPage Schema

How do I keep tasks tracked across context boundaries during coding?▼

Task tracking across context boundaries is maintained by enforcing a task lifecycle with pending, in_progress, and completed states. You create tasks before starting work, update their status, and review them when resuming a previous session to ensure continuity.

What is the best way to manage task lifecycle when discovering sub-tasks mid-work?▼

When discovering sub-tasks mid-work, the deviation protocol requires recording discoveries as new pending tasks with context notes. This keeps your current in_progress task uninterrupted while ensuring new issues are captured for later resolution.

How do I prevent losing discovered work before a context compaction?▼

To prevent losing discovered work before context compaction, execute a pre-compaction checkpoint. This process ensures all newly discovered tasks and issues are explicitly captured and recorded before the context window is compressed.

Can I enforce only one in_progress task at a time for multi-step coding work?▼

Yes, you can enforce only one in_progress task at a time for multi-step coding work. The system prevents deleting tasks and requires advancing existing tasks to completion before moving a new pending task into the in_progress state.

Does task tracking apply to purely informational questions with no code changes?▼

No, task tracking does not apply to purely informational questions with no code changes. The system is designed to enforce disciplined tracking for coding tasks, planning multi-step work, and session resumes, skipping non-code inquiries.