agentleFS
Sign inStart free
dnlboxdnlbox/ai-protocol/.agents/skills/consolidate-state/SKILL.md

consolidate-state

Skill18 starsChanged 3 months agoMITView on GitHub

Repair BUILD_STATE.md when it becomes stale, contradictory, or difficult to scan.

The file

Show its rules and text

We split this skill into the rules it gives an agent

18 rules. About 0 are common, 13 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user requests state consolidation.

    line 8
  2. Very specific:

    Use this skill when BUILD_STATE.md contradicts verified reality.

    line 10
  3. Distinctive:

    Use this skill when the current state no longer fits one screen.

    line 12
  4. Distinctive:

    Do not invoke this skill on a fixed packet cadence.

    line 14
  5. Distinctive:

    Remove completed procedural detail.

    line 26
  6. Distinctive:

    Treat a declared runtime ledger as authoritative for live worker state.

    line 32
  7. Distinctive:

    Treat repository evidence as authoritative for implemented behaviour.

    line 33
  8. Very specific:

    Keep live worker telemetry out of BUILD_STATE.md.

    line 36
  9. Very specific:

    Keep Now within one screen.

    line 40
  10. Very specific:

    Keep one current objective in Now.

    line 41
  11. Very specific:

    Keep one next meaningful action in Now.

    line 42
  12. Distinctive:

    Keep only material current decisions.

    line 43
  13. Distinctive:

    Keep only material current blockers.

    line 44
  14. Distinctive:

    Keep the execution frontier compact when one exists.

    line 45
  15. Distinctive:

    Avoid changing accepted product intent.

    line 51
  16. Distinctive:

    Avoid changing execution strategy.

    line 52
  17. Distinctive:

    Avoid editing protocol files.

    line 53
  18. Distinctive:

    Avoid reporting consolidation as implementation progress.

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Consolidate state

Use this skill when the user requests state consolidation.

Use this skill when BUILD_STATE.md contradicts verified reality.

Use this skill when the current state no longer fits one screen.

Do not invoke this skill on a fixed packet cadence.

Reconciliation

  • Compare BUILD_STATE.md with recent git history.
  • Compare BUILD_STATE.md with current validation evidence.
  • Compare BUILD_STATE.md with the running product when practical.
  • Resolve current-state contradictions in favour of verified reality.
  • Preserve material unresolved findings.
  • Preserve the current approved objective.
  • Preserve active ownership.
  • Preserve the next meaningful action.
  • Remove completed procedural detail.
  • Rely on git history for completed implementation detail.
  • Move older milestone summaries to Archive only when they remain useful.

Runtime state

  • Treat a declared runtime ledger as authoritative for live worker state.
  • Treat repository evidence as authoritative for implemented behaviour.
  • Pause dispatch when runtime state contradicts repository evidence.
  • Reconcile the contradiction before updating durable state.
  • Keep live worker telemetry out of BUILD_STATE.md.

Result

  • Keep Now within one screen.
  • Keep one current objective in Now.
  • Keep one next meaningful action in Now.
  • Keep only material current decisions.
  • Keep only material current blockers.
  • Keep the execution frontier compact when one exists.
  • Apply the consolidation within the approved objective.
  • Report the resulting state boundary.

Boundaries

  • Avoid changing accepted product intent.
  • Avoid changing execution strategy.
  • Avoid editing protocol files.
  • Avoid reporting consolidation as implementation progress.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free