harness-continuity

What problem does it solve? Long-running agent work that spans multiple sessions often loses track of which task is active, leaves stale in-progress states, or commits changes without evidence. This Skill enforces durable task continuity so work can be resumed, blocked, or handed off cleanly between sessions. ## Core Features & Use Cases - One-Task-At-A-Time Rule: Locates feature state in feature_list.json, .specs/features/*/tasks.md, or session todos and ensures only one task is in_progress at any time. - State Transition Control: Enforces the not_started → in_progress → passing/blocked lifecycle, requiring an exact blocker reason for blocked tasks. - Clean-State Checkpoint: Verifies startup commands, observable evidence, scoped git diff output, and updated progress files before commits or handoffs. - Use Case: An agent session ends mid-feature. The next session reads the state file, finds the single in_progress task with its evidence, and continues implementation without duplicating or skipping work. ## Quick Start Ask the agent to check the current task state, pick the next eligible task, and run the clean-state checkpoint before committing.