brain:update

Merge extracted entities, decisions, events, and tasks into project_brain.db across sessions.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/rkz91/coco --skill brain-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brain:update
Source: https://github.com/rkz91/coco/tree/main/systems/brain/skills/brain-update
Command: npx skills add https://github.com/rkz91/coco --skill brain-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill provides a structured workflow to scan the entire conversation, extract new entities, decisions, events, tasks, and merges them into the project brain database, ensuring cross-session continuity and preventing data loss.

Core Features & Use Cases

  • Cross-session awareness: reads current brain state, merges new data, and respects already-recorded decisions, events, and tasks.
  • Conflict-aware updates: prioritizes newer or more advanced statuses and merges task notes without overwriting existing information.
  • End-to-end brain hygiene: upserts entities, relationships, tasks, threads, decisions, and events to maintain a coherent knowledge graph across sessions.

Quick Start

Run the brain update workflow at the end of a session to flush all learned information into project_brain.db.

Frequently Asked Questions about brain:update

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

FAQPage Schema
How do I persist cross-session knowledge and prevent data loss when ending a conversation?

To persist cross-session knowledge, run an end-of-session brain flush to scan the conversation and upsert new entities, decisions, events, and tasks into your project brain database, ensuring continuity and preventing data loss.

What is the best way to merge new tasks into a brain database without overwriting existing notes?

The best way to merge new tasks into a brain database is using a conflict-aware update workflow that merges task notes and prioritizes newer data without overwriting existing information or regressing statuses.

Do I need a specific database file to perform a brain update?

Yes, performing a brain update requires a functioning brain database file named project_brain.db and a valid project context to read the current state and apply updates accurately.

How does conflict resolution work when updating entities across parallel sessions?

Conflict resolution during entity updates works by reading the current brain state and applying conflict-aware merges that respect newer data and avoid regressing statuses recorded across parallel sessions.

Can I maintain a coherent knowledge graph across multiple sessions automatically?

Yes, you can maintain a coherent knowledge graph across sessions by upserting entities, relationships, tasks, threads, decisions, and events at the end of each session to ensure cross-session awareness.