thrum-update-project

Merge session narratives and mechanical state into Thrum's project_state file.

28|5|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/leonletto/thrum --skill thrum-update-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: thrum-update-project
Source: https://github.com/leonletto/thrum/tree/main/codex-plugin/skills/thrum-update-project
Command: npx skills add https://github.com/leonletto/thrum --skill thrum-update-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update of the Thrum project context is streamlined by merging session narratives with the mechanical state into .thrum/context/project_state.md, ensuring continuity across restarts and environments while avoiding main-context bloat.

Core Features & Use Cases

  • Compose and consolidate a session summary describing progress, decisions, and next steps.
  • Spawn and run a general-purpose subagent to gather mechanical state and perform targeted edits in place.
  • Maintain a strictly controlled architecture health log and rolling session blocks to surface recent work and blockers.
  • Use worktree awareness to align agent identity with active Git worktrees and team output.

Quick Start

Run the thrum update-project workflow to refresh the project_state.md with your latest session summary and mechanical state.

Frequently Asked Questions about thrum-update-project

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

FAQPage Schema
How do I keep project state synchronized across multiple sessions and environments?

Session summaries and mechanical project state are merged into a dedicated project_state.md file. This deterministic state merging preserves progress across restarts and environments without bloat in the main context window.

How do I update project context after delegating tasks to subagents?

A general-purpose subagent gathers mechanical state and performs targeted edits in place. The workflow then consolidates delegated subagent work and session narratives into the project state file.

What is the best way to avoid context window bloat when tracking ongoing project updates?

Context bloat is avoided by maintaining rolling session blocks and an architecture health log in a dedicated project_state.md file. This structure surfaces recent work and blockers externally instead of consuming the main context window.

Does Thrum project state update work with Git worktrees for parallel team workflows?

Git worktrees are supported through worktree awareness features that align agent identity with active worktrees. This alignment ensures team output and project context remain synchronized across parallel branch workflows.

How do I automate the roll-forward of project context in a shared workspace?

Automating project context roll-forward involves running a structured workflow that composes session summaries and performs deterministic state merging. This automatically refreshes the project state file with recent progress, decisions, and next steps.

When should I not use automated project state merging for session management?

Automated project state merging should not be used for single-step, isolated edits that lack multi-step coordination or subagent delegation. It is specifically designed for complex workflows requiring structured rolling session blocks and architecture health tracking.