update-tears

customized for your needs.

13|3|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/jamie8johnson/cqs --skill update-tears
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-tears
Source: https://github.com/jamie8johnson/cqs/tree/main/.claude/skills/update-tears
Command: npx skills add https://github.com/jamie8johnson/cqs --skill update-tears

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing ongoing work across context switches is error-prone and time-consuming. This skill automatically records the current session state into the project continuity log and notes repository to ensure you never lose progress when you switch tasks or resume later.

Core Features & Use Cases

  • Session capture: snapshots task description, branch, in-progress changes, and open PRs into PROJECT_CONTINUITY.md.
  • Structured notes: logs session observations and surprises into docs/notes.toml for retrospective analysis.
  • Guided resumption: helps teams reconstitute context quickly after interruptions or restarts, preserving decisions and work-in-progress.

Quick Start

Update the current session state by running the Update Tears skill to refresh PROJECT_CONTINUITY.md and docs/notes.toml.

Frequently Asked Questions about update-tears

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

FAQPage Schema
How do I preserve session state for smooth task switching in software development?

Preserve session state by capturing your active task description, current git branch, and in-progress changes into a structured continuity log like PROJECT_CONTINUITY.md. This ensures work-in-progress survives context compaction and task switching without losing progress.

What is context compaction and how does it affect project continuity?

Context compaction reduces active session memory, risking the loss of open issues and parked tasks. Storing project continuity in files like PROJECT_CONTINUITY.md and docs/notes.toml records this state externally, allowing you to reconstitute context quickly after interruptions or restarts.

How do I log session observations and surprises for retrospective analysis?

Log session observations and surprises by writing structured entries into docs/notes.toml during task switches. Capturing unexpected issues and decisions in a structured format enables better retrospective analysis and guided session resumption later.

Does preserving session state enforce non-destructive updates to existing notes?

Yes, preserving session state enforces non-destructive updates to existing notes. The process checks git status for in-progress work and integrates with cqs_add_note if available, updating continuity logs without overwriting previous entries.

Why should I use a dedicated file for parked tasks and open issues instead of manual notes?

Using a dedicated file like PROJECT_CONTINUITY.md for parked tasks and open issues provides structured guided resumption. Unlike manual notes, it automatically snapshots your git branch and in-progress changes, reducing error-prone context reconstruction when switching tasks.