Tasks.md Sprint Sync

Sync TASKS.md current phase and in-progress checklist from the active PLAN.md phase to keep sprint execution aligned.

Security Scan

The skill does what it claims (extracts the IN PROGRESS phase from a PLAN.md and syncs the TASKS.md project section); its requirements and instructions are proportionate and there are no hidden network calls or extra credentials requested.

Purpose & Capability

Name/description, required binaries (bash, python3), and the included script all match the stated goal of reading PLAN.md and updating TASKS.md. There are no unrelated credentials, binaries, or config paths requested.

Instruction Scope

The SKILL.md and script limit operations to the provided PLAN_FILE and TASKS_FILE and the specified PROJECT_NAME. In apply mode the script will overwrite the given TASKS_FILE, so ensure you only point it at files you intend to modify. The matching is strict (exact project heading, exact '**Status: IN PROGRESS**' marker and strict section regexes), which may cause false negatives if your markdown formatting differs.

Install Mechanism

Instruction-only skill with no install spec and a small bundled script; nothing is downloaded or written to system locations by an installer.

Credentials

No environment variables, secrets, or external credentials are required. The optional inputs are file paths and a project name appropriate for the task.

Persistence & Privilege

The skill is not always-enabled and does not request any persistent privileges or modify other skills or system-wide settings.

Assessment

This skill is coherent with its purpose, but take these precautions before using 'apply': run it in report (dry-run) mode first to confirm detected drift; test with the provided fixtures; ensure PROJECT_NAME exactly matches the heading in TASKS.md; do not point TASKS_FILE at sensitive system or config files because apply mode will overwrite the target file; review formatting of your PLAN.md (the script expects '**Status: IN PROGRESS**' and a '### Work' section) and be aware the regexes are strict and may miss differently-formatted sections.

Use this skill to keep a project's TASKS.md section aligned with whatever phase is marked IN PROGRESS in that project's PLAN.md.

What this skill does

• Reads the active phase from PLAN.md (phase with **Status: IN PROGRESS**)
• Extracts bullets from that phase's ### Work section
• Finds the target project section in TASKS.md
• Reports drift between plan work items and ### In progress tasks
• Optionally updates TASKS.md to match plan phase + work items

Inputs

Required:

• PROJECT_NAME (the exact heading in TASKS.md, e.g. ClawHub Skills)

Optional:

• PLAN_FILE (default: PLAN.md)
• TASKS_FILE (default: TASKS.md)
• SYNC_MODE (report or apply, default: report)

Run

Dry-run drift report:

PROJECT_NAME="ClawHub Skills" \
PLAN_FILE=projects/clawhub-skills/PLAN.md \
TASKS_FILE=TASKS.md \
bash skills/tasks-md-sprint-sync/scripts/sync-tasks-phase.sh

Apply sync to TASKS.md:

PROJECT_NAME="ClawHub Skills" \
PLAN_FILE=projects/clawhub-skills/PLAN.md \
TASKS_FILE=TASKS.md \
SYNC_MODE=apply \
bash skills/tasks-md-sprint-sync/scripts/sync-tasks-phase.sh

Run against included fixtures:

PROJECT_NAME="Demo Project" \
PLAN_FILE=skills/tasks-md-sprint-sync/fixtures/PLAN.sample.md \
TASKS_FILE=skills/tasks-md-sprint-sync/fixtures/TASKS.sample.md \
SYNC_MODE=apply \
bash skills/tasks-md-sprint-sync/scripts/sync-tasks-phase.sh

Output contract

• Exit 0 when report/apply completes
• Exit 1 on invalid inputs, missing sections, or no active phase
• In report mode: prints missing/extra task drift, no file changes
• In apply mode: updates Current phase + replaces In progress list for the target project section