skill-status-sync

Synchronize task status atomically between state.json and TODO.md.

3|1|Updated May 21, 2024
One-click install
npx skills add https://github.com/benbrastmckie/.dotfiles --skill skill-status-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-status-sync
Source: https://github.com/benbrastmckie/.dotfiles/tree/main/.claude/skills/skill-status-sync
Command: npx skills add https://github.com/benbrastmckie/.dotfiles --skill skill-status-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures atomic synchronization of task status between state.json and TODO.md, preventing drift and inconsistencies.

Core Features & Use Cases

  • Atomic updates: Consistently update both state.json and TODO.md in a single operation.
  • Workflow compatibility: Supports preflight and postflight transitions and artifact linking for standalone and workflow contexts.
  • Recovery & auditability: Provides traceable session identifiers and clear error handling for manual corrections or recovery operations.

Quick Start

Example: Run the skill-status-sync to perform a preflight_update for task #42 with target_status: researching and session_id: manual.

Frequently Asked Questions about skill-status-sync

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

FAQPage Schema
How do I sync task status between state.json and TODO.md to prevent drift?

You can atomically sync task status between state.json and TODO.md using jq-based updates to ensure consistent state mutation and prevent drift in a single operation.

What is the best way to automate preflight and postflight task transitions?

Automating preflight and postflight transitions is achievable by targeting tasks tracked in specs/state.json and specs/TODO.md, linking artifacts idempotently across standalone and workflow contexts.

Can I link artifacts idempotently during state.json and TODO.md synchronization?

Yes, idempotent artifact linking is supported during synchronization, allowing repeated operations without duplicate entries while maintaining clear error handling for recovery.

Does this status synchronization approach support manual recovery and auditability?

Yes, it provides traceable session identifiers and clear error handling to support manual corrections and recovery operations for task status synchronization.

Why does task status drift occur when updating state.json and TODO.md separately?

Updating state.json and TODO.md separately causes drift because non-atomic updates can leave inconsistencies between the two files if one operation fails midway.

Do I need jq to perform atomic updates on specs/state.json?

Yes, the skill uses jq-based updates for consistent state mutation, requiring jq to perform rigorous input validation and atomic updates on specs/state.json.