What problem does it solve?
Progress updates shared in conversation often get lost between sessions, making it hard to resume interrupted work or track pending requirements. This Skill converts natural-language progress descriptions into durable task state files stored in the project's .codex/tasks/ directory.
Core Features & Use Cases
- Task State Persistence: Records tasks with statuses like in-progress, interrupted, blocked, or pending into .codex/tasks/ and archives finished work.
- Multi-Task Splitting: Splits a single message containing multiple task subjects into separate task records instead of one vague summary.
- Interruption Checkpoints: Adds checkpoint entries to a main task when short fixes interrupt it, preserving recovery entry points and next steps.
- Use Case: You tell the assistant "the routing dialog work is still in progress, but the new log-filter feature hasn't started and I got interrupted by a fix" — the Skill writes two separate task files with correct statuses and a checkpoint on the main task.
Quick Start
Use cc-task-state to record my current progress, note the interrupted main task, and save the not-yet-started feature as a pending requirement.
