sync

Sync sprint READMEs with current ticket file states.

1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Olino3/anvil --skill sync-olino3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync
Source: https://github.com/Olino3/anvil/tree/main/plugins/anvil/skills/sync
Command: npx skills add https://github.com/Olino3/anvil --skill sync-olino3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync drift between sprint README and the actual state of its ticket files to maintain accurate project artifacts.

Core Features & Use Cases

  • Ensures README status tables reflect current ticket metadata across sprints.
  • Keeps bidirectional dependency references in sync between tickets and their docs.
  • Useful for teams needing accurate sprint health reporting and artifact hygiene.

Quick Start

Run the sync operation to align the sprint README with the latest ticket states.

Frequently Asked Questions about sync

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

FAQPage Schema
How do I keep my sprint README in sync with ticket status?

To keep your sprint README in sync with ticket status, this automation aligns status tables and dependency references with current ticket files. It dispatches a syncer agent to update sprint folders and generates a final consistency report.

What is sprint README drift and how does synchronization work?

Sprint README drift occurs when documentation status tables diverge from actual ticket metadata. Synchronization works by locating the sprint folder, dispatching a syncer agent to align progress markers, and generating a report to restore artifact consistency.

How do I automate sprint documentation updates for project management?

You automate sprint documentation updates by running a sync operation that targets sprint folders under docs/anvil/sprints/. This process automatically aligns bidirectional dependency references and ticket statuses to maintain accurate project artifacts.

Does sprint synchronization work with ticket files outside the docs/anvil/sprints/ folder?

No, sprint synchronization applies specifically to sprint folders located under docs/anvil/sprints/. It relies on this directory structure to locate ticket files and align their statuses, dependencies, and progress markers with the README.

What is the best way to maintain accurate sprint health reporting across tickets?

The best way to maintain accurate sprint health reporting is to run regular sync operations that update bidirectional dependency references and ticket statuses. This ensures your sprint README accurately reflects the current state of project artifacts.