resonance-ops-update-roadmap

Synchronizes project state files with git history to reconcile roadmap drift.

Updated Dec 1, 2025

Search Tags:#git #workflow #project management #documentation #roadmap #reconciliation #state sync

Ready to run

npx skills add https://github.com/manusco/wolfgang --skill resonance-ops-update-roadmap-manusco

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: resonance-ops-update-roadmap
Source: https://github.com/manusco/wolfgang/tree/main/.agents/skills/ops/update-roadmap
Command: npx skills add https://github.com/manusco/wolfgang --skill resonance-ops-update-roadmap-manusco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project plans drift from reality: the roadmap says Step 1 while the code is already at Step 5. This Skill reconciles the documented project state with actual git history so the plan reflects what was really built. ## Core Features & Use Cases - Drift Detection: Compares the last 10 git commits against the state file to find unlogged work. - State Reconciliation: Marks completed tasks as done, adds constraints found in commit messages, and recalculates the immediate next step. - Reality-First Recovery: When the plan and code diverge, it updates the plan to match the code instead of reverting working code. - Use Case: After a long unlogged coding session, run the sync to bring the stale state file up to date with everything that was actually merged. ## Quick Start Run /update-roadmap to sync my project state file with the recent git history and recalculate the next step.

Frequently Asked Questions about resonance-ops-update-roadmap

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

FAQPage Schema

How do I sync my project roadmap with git history?▼

Run the update-roadmap command, which reads the last 10 git commits and compares them against the state file. It marks merged work as done, adds new constraints from commit messages, and recalculates the next step.

What happens when the plan and the code disagree?▼

The code wins. Git history is treated as the objective truth, so the state file is updated to reflect reality. The Skill never reverts working code just to match an outdated plan.

What files does the roadmap sync require?▼

It requires an existing .resonance/01_state.md file and a git history. If the state file is missing, the prerequisite check fails fast and the process aborts, suggesting project initialization first.

Can this Skill plan new features or rewrite the roadmap?▼

No. Planning new features is explicitly out of scope and delegated to a separate planning command. This Skill only reconciles the existing state file with what git history shows actually happened.

Why does the roadmap update abort immediately?▼

The most common cause is a missing .resonance/01_state.md file or absent git history. The prerequisites check runs first and stops execution before any reconciliation is attempted.