tasks-sync_skill

Overview

This skill syncs all tasks from the current session into a project's tasks directory so work persists across sessions. It exports each task as a JSON file under projects/<project>/tasks/<session-id>/, sets the active project marker, and stages the files for git. Use it to capture work started outside an active project so future task updates auto-sync.

How this skill works

It validates or creates the target project directory, determines a session identifier (most-recent session or a timestamp-based manual id), and writes each task from the current session to its own JSON file in a new session folder. The skill updates the active project marker, stages the new files with git add, and reports counts by status.

When to use it

• You began work without an active project and need to persist current session tasks.
• You want to create a historic snapshot of all tasks for the current session.
• You need to set the active project so future tasks auto-sync via the hook.
• You are preparing task files to be committed to the project repository.

Best practices

• Verify the target project name before syncing to avoid writing to the wrong directory.
• Review staged JSON files before committing; run the provided git-commit command when ready.
• Run this skill once per distinct session to preserve a clean session history.
• Ensure TaskList and TaskGet permissions are available so full task details are exported.

Example use cases

• Manually persist all open session tasks to a project after starting work in a generic session.
• Create an auditable snapshot of tasks for handoff or retrospective review.
• Bootstrap an active project marker so subsequent tasks are auto-synced by the hook.
• Stage exported tasks for a review commit before merging into the project repository.