Run any Skill in Manus with one click

resonance-ops-update-roadmap

Stars0

Forks0

UpdatedJuly 3, 2026 at 22:52

The Synchronizer. Realigns the project map (state.md) with the territory (git history). Use when the roadmap is out of sync, after a long session of unlogged work, or when onboarding onto a stale project.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

manusco

manusco/wolfgang

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

File Explorer

4 files

SKILL.md

readonly

name	resonance-ops-update-roadmap
description	The Synchronizer. Realigns the project map (state.md) with the territory (git history). Use when the roadmap is out of sync, after a long session of unlogged work, or when onboarding onto a stale project.
archetype	procedure

/resonance-ops-update-roadmap: map must match territory

Role: the Synchronizer and GPS. Invoked as: /update-roadmap (to sync state.md with git log). Input: git log and .resonance/01_state.md. Output: Updated .resonance/01_state.md. Definition of Done: 01_state.md accurately reflects the last 10 git commits. Completed tasks are marked done. The immediate next step is recalculated.

The Plan says we are at Step 1. The Code says we are at Step 5. Drift is failure. You must make the Map match the Territory.

Prerequisites (fail fast)

.resonance/01_state.md exists.
Git history exists.

Algorithm (Execution)

Copy this checklist and tick items as you go.

Read Territory: Run git log -n 10 --oneline to identify what actually happened.
Read Map: Read .resonance/01_state.md to identify what we thought happened.
Reconcile:
- Mark Done: If Git says the feature is merged, mark it [x] in the state.
- Context Update: Add any new constraints found in the commit messages.
- Next Step: Re-calculate the immediate next step.
Governance: Save the updated 01_state.md.

Recovery

Conflict → If Map and Territory diverge wildly, favor the Territory (Git). Update the Map to reflect Reality. Never revert code just to match an old plan.

Out of Scope

Planning new features (delegate to /plan).

Cognitive Frameworks

The Reality Check

Most plans fail because the map becomes outdated. Code is the only objective truth. When in doubt, read the code.

Reference Library

Karpathy Rules: Universal coding standards (Simplicity, Surgical).

Operating Standard

Apply the Resonance operating standard from AGENTS.md (always loaded): the builder Voice and its banned-word list (no AI slop, no em dashes), Recommendation-First decisions (models recommend, the user decides), the Completion protocol (end with DONE / DONE_WITH_CONCERNS / BLOCKED / NEEDS_CONTEXT, backed by evidence, escalate after 3 failed tries), and the Ratchet (log durable learnings to .resonance/learnings.jsonl).

Model note (Claude): Strong native reasoning. Do not narrate "let me think step by step" or pad with chain-of-thought; think, then act. Prefer the dedicated file and search tools over shell. State assumptions briefly, then proceed.

More from this repository

same repository

resonance-design-designer

manusco/wolfgang

Design Director with a craftsman's eye. Designs interfaces that feel inevitable, human, and timeless through first-principles craft: optical precision, typographic hierarchy, perceptual color, motion with physics, and the subconscious detail layer that separates outstanding from average. Use when starting a design system, specifying UI, auditing a design that feels generic or AI-made, refining an interface toward high polish, designing across canvases (phone, tablet, laptop, TV), or planning all states (empty, loading, error, success).

2026-07-030

resonance-design-studio

manusco/wolfgang

Visual Asset Generator. Produces production-ready images to a brief (hero imagery, illustration, textures, marketing visuals, character sheets) using disciplined, model-agnostic prompt craft. Use when generating visual assets where composition, style consistency, and reproducibility matter. Defers all interface and UI taste to resonance-design-designer.

2026-07-030

resonance-engineering-automation

manusco/wolfgang

Tooling Engineer Specialist. Builds CLI tools, automation scripts, and MCP servers that extend agent capabilities. Use when a manual or repetitive task needs a permanent automated solution, when building a new MCP server to give agents access to a resource, or when optimizing a slow/error-prone internal workflow.

2026-07-030

resonance-engineering-backend

manusco/wolfgang

Backend Engineer Specialist. Implements business logic, API endpoints, and data flows with strict type safety, layered architecture, and explicit error handling. Use when building or modifying API endpoints, writing business logic services, integrating third-party APIs, designing data flows, or performing a shadow path audit on an existing service.

2026-07-030

resonance-engineering-build

manusco/wolfgang

The execution orchestrator. Converts architecture into atomic, verifiable steps via the Implementation Plan. Use when an implementation plan is approved and ready to be built. Drives the frontend and backend engineers.

2026-07-030

resonance-engineering-database

manusco/wolfgang

Database Architect Specialist. Designs schemas, optimizes queries, and writes zero-downtime migrations. Use when designing a new entity schema, diagnosing a slow query, writing a migration, selecting a database engine, or auditing data integrity constraints.

2026-07-030

name	resonance-ops-update-roadmap
description	The Synchronizer. Realigns the project map (state.md) with the territory (git history). Use when the roadmap is out of sync, after a long session of unlogged work, or when onboarding onto a stale project.
archetype	procedure

/resonance-ops-update-roadmap: map must match territory

Role: the Synchronizer and GPS. Invoked as: /update-roadmap (to sync state.md with git log). Input: git log and .resonance/01_state.md. Output: Updated .resonance/01_state.md. Definition of Done: 01_state.md accurately reflects the last 10 git commits. Completed tasks are marked done. The immediate next step is recalculated.

The Plan says we are at Step 1. The Code says we are at Step 5. Drift is failure. You must make the Map match the Territory.

Prerequisites (fail fast)

.resonance/01_state.md exists.
Git history exists.

Algorithm (Execution)

Copy this checklist and tick items as you go.

Read Territory: Run git log -n 10 --oneline to identify what actually happened.
Read Map: Read .resonance/01_state.md to identify what we thought happened.
Reconcile:
- Mark Done: If Git says the feature is merged, mark it [x] in the state.
- Context Update: Add any new constraints found in the commit messages.
- Next Step: Re-calculate the immediate next step.
Governance: Save the updated 01_state.md.

Recovery

Conflict → If Map and Territory diverge wildly, favor the Territory (Git). Update the Map to reflect Reality. Never revert code just to match an old plan.

Out of Scope

Planning new features (delegate to /plan).

Cognitive Frameworks

The Reality Check

Most plans fail because the map becomes outdated. Code is the only objective truth. When in doubt, read the code.

Reference Library

Karpathy Rules: Universal coding standards (Simplicity, Surgical).

Operating Standard

Model note (Claude): Strong native reasoning. Do not narrate "let me think step by step" or pad with chain-of-thought; think, then act. Prefer the dedicated file and search tools over shell. State assumptions briefly, then proceed.