torre-doc-sync

Synchronize TORRE project documentation files after work sessions.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/lfggarcia/dnd-app --skill torre-doc-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: torre-doc-sync
Source: https://github.com/lfggarcia/dnd-app/tree/main/.github/skills/torre-doc-sync
Command: npx skills add https://github.com/lfggarcia/dnd-app --skill torre-doc-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TORRE project documentation often becomes out of date after sprint work. This Skill ensures that PROJECT_PLAN.md, PROJECT_STATUS.md, HANDOFF.md, and CHANGELOG.md are updated to reflect the current state, reducing miscommunication and onboarding friction.

Core Features & Use Cases

  • Update and synchronize the main planning, status, handoff, and changelog files after a task or sprint.
  • Enforce consistency across documentation by applying a standard update procedure and timestamps.
  • Use case: after finishing a sprint, run this Skill to push all relevant changes into the docs and prepare a clean handoff.

Quick Start

Invoke this skill after completing work to synchronize PROJECT_PLAN.md, PROJECT_STATUS.md, HANDOFF.md, and CHANGELOG.md with the latest changes.

Frequently Asked Questions about torre-doc-sync

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

FAQPage Schema
How do I keep project documentation in sync after completing a sprint?

To keep project documentation in sync after a sprint, you can use this Skill to update PROJECT_PLAN.md, PROJECT_STATUS.md, HANDOFF.md, and CHANGELOG.md to reflect the latest completed work with deterministic timestamps.

What is the best way to update HANDOFF.md and CHANGELOG.md after work sessions?

The best way to update HANDOFF.md and CHANGELOG.md after work sessions is to run a synchronization procedure that applies a standard update process with proper timestamps and minimal manual intervention.

How does deterministic documentation synchronization work for project status files?

Deterministic documentation synchronization works by applying a standard update procedure to project status files, ensuring changes are idempotent and produce identical outputs when run multiple times over the same completed work.

Do I need to manually edit PROJECT_PLAN.md before running a documentation sync?

You do not need to manually edit PROJECT_PLAN.md before running a documentation sync. The Skill is designed to require minimal manual intervention and automatically updates the files to match the current state.

When should I run a project documentation synchronization update?

You should run a project documentation synchronization update immediately after finishing a sprint or task, ensuring all relevant changes are pushed into the docs to prepare a clean handoff and reduce onboarding friction.

Why does project documentation become outdated after sprint work?

Project documentation becomes outdated after sprint work because manual updates are often skipped, leading to miscommunication and onboarding friction. Synchronizing files like PROJECT_STATUS.md and HANDOFF.md enforces consistency across the project.