Run any Skill in Manus with one click

consolidate-state

Stars18

Forks1

UpdatedJuly 16, 2026 at 22:07

Keep BUILD_STATE.md lean and self-consistent. Use when BUILD_STATE.md has grown large, Now exceeds one screen, logs sprawl, git/test reality contradicts Now, a workspace Components table drifts, or three shipped slices have accumulated since the last archive. Mirrors consolidate-memory, but for the agent working state.

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

dnlbox

dnlbox/ai-protocol

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	consolidate-state
description	Keep BUILD_STATE.md lean and self-consistent. Use when BUILD_STATE.md has grown large, Now exceeds one screen, logs sprawl, git/test reality contradicts Now, a workspace Components table drifts, or three shipped slices have accumulated since the last archive. Mirrors consolidate-memory, but for the agent working state.

Consolidate State

BUILD_STATE.md is append-prone: over a long project the logs sprawl and the Now block drifts out of sync with what actually happened. This skill is the cure. Prevention lives in the execution protocol (every slice replaces Now and adds one terse log line); this skill is the periodic deep clean.

When it runs

Manually, when you notice rot.
Automatically, when the start protocol in AGENTS.md finds the file over budget or self-contradictory.
As a closeout hygiene trigger after three shipped slices since the last archive.
Whenever git log, validation state, or a workspace Components dashboard contradicts Now.

Procedure

Reconcile Now against reality: git log --oneline -20, the test state, and the running app. Rewrite Now so it matches what is actually true and points at one clear next step. Resolve contradictions in favour of reality, not the stale text.
Compact the logs: collapse completed milestones in Decisions and Session log into a one-line summary each, moved to Archive. The full detail already lives in git, so do not preserve it here.
If Now is carrying several future slices, ordered phases, or go/no-go gates, do not compress that plan into state. Move it to an existing ROADMAP.md, or flag that /plan-implementation should create one, then leave BUILD_STATE.md pointing at the active roadmap position.
Verify the budget: Now is at most a screen; Decisions and Session log hold only the current milestone's lines; any older finished work has a one-line Archive entry.
Present the before/after as a diff and get approval before writing.

Rules

Never invent history. If git and the file disagree, git wins.
Keep one line per archived milestone, not per slice.
Do not touch the protocol files (that is sync-protocol).
This is housekeeping, not progress: do not change the planned next step except to correct it against reality.

More from this repository

same repository

concept-intake

dnlbox/ai-protocol

Extract and organise an early product or project idea through short executive-level conversation rounds before canonical docs/concept/ files or implementation plans exist. Use when the user invokes concept intake, starts a new project from an unstructured idea, wants to think aloud or dictate rough ideas, or needs a durable intake document without prematurely planning architecture or implementation.

2026-07-1618

plan-implementation

dnlbox/ai-protocol

Create or revise an approved mechanical execution contract from accepted docs/concept/ by choosing and verifying the stack, defining validation gates, updating AGENTS.md Project Specifics and BUILD_STATE.md, and conditionally creating or revising DESIGN.md and ROADMAP.md. Use for initial operational planning, explicit re-planning of an operationally planned project, or when new architecture, phases, slices, roadmap order, or release gates must be resolved without writing product code.

2026-07-1618

shape-concept

dnlbox/ai-protocol

Create or revise coherent canonical docs/concept/ documents through short proposal, drafting, research, and refinement rounds without creating implementation plans or modifying mechanical protocol files. Use after accepted concept intake, or when an operationally planned project must deliberately change accepted product intent before re-planning.

2026-07-1618

sync-protocol

dnlbox/ai-protocol

Reconcile an existing operational contract against accepted docs/concept/ and implementation reality after toolchain, validation, harness, command, runtime, or other project-specific behaviour changes. Use when the user says sync protocol, implementation may have drifted from AGENTS.md or DESIGN.md, or closeout requires a no-op protocol audit. Do not use for initial planning, roadmap creation, or BUILD_STATE.md generation.

2026-07-1618

name	consolidate-state
description	Keep BUILD_STATE.md lean and self-consistent. Use when BUILD_STATE.md has grown large, Now exceeds one screen, logs sprawl, git/test reality contradicts Now, a workspace Components table drifts, or three shipped slices have accumulated since the last archive. Mirrors consolidate-memory, but for the agent working state.

Consolidate State

When it runs

Manually, when you notice rot.
Automatically, when the start protocol in AGENTS.md finds the file over budget or self-contradictory.
As a closeout hygiene trigger after three shipped slices since the last archive.
Whenever git log, validation state, or a workspace Components dashboard contradicts Now.

Procedure

Reconcile Now against reality: git log --oneline -20, the test state, and the running app. Rewrite Now so it matches what is actually true and points at one clear next step. Resolve contradictions in favour of reality, not the stale text.
Compact the logs: collapse completed milestones in Decisions and Session log into a one-line summary each, moved to Archive. The full detail already lives in git, so do not preserve it here.
If Now is carrying several future slices, ordered phases, or go/no-go gates, do not compress that plan into state. Move it to an existing ROADMAP.md, or flag that /plan-implementation should create one, then leave BUILD_STATE.md pointing at the active roadmap position.
Verify the budget: Now is at most a screen; Decisions and Session log hold only the current milestone's lines; any older finished work has a one-line Archive entry.
Present the before/after as a diff and get approval before writing.

Rules

Never invent history. If git and the file disagree, git wins.
Keep one line per archived milestone, not per slice.
Do not touch the protocol files (that is sync-protocol).
This is housekeeping, not progress: do not change the planned next step except to correct it against reality.