fulcra-agent-continuity

Snapshots agent objectives, decisions, and next actions into structured JSON for deterministic session resume.

10|1|Updated May 21, 2026
One-click install
npx skills add https://github.com/ashfulcra/fulcra-tools --skill fulcra-agent-continuity-ashfulcra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fulcra-agent-continuity
Source: https://github.com/ashfulcra/fulcra-tools/tree/main/skills/fulcra-agent-continuity
Command: npx skills add https://github.com/ashfulcra/fulcra-tools --skill fulcra-agent-continuity-ashfulcra

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Long-running agents lose their working context when a session ends, a cron job fires, or context compaction occurs, forcing the next session to re-read freeform prose and guess what mattered. This Skill replaces that guesswork with a structured continuity snapshot and a deterministic resume brief. ## Core Features & Use Cases - Structured snapshots: Capture objective, decisions, next actions, open questions, artifacts, and context-used percentage to a versioned JSON schema (coord.teams.continuity.v1) via coord-engine continuity snapshot. - Deterministic resume: On wake, coord-engine continuity resume folds snapshots to the newest and prints a brief, with --max-age freshness checks and machine-readable error_code values. - Session-exit parking: continuity park snapshots every held role and sets each role doc's checkpoint_ref, failing loudly with CHECKPOINT NOT WRITTEN when nothing was saved. - Use Case: An agent working a reviewer role on a Fulcra team snapshots its progress before context runs out; a fresh cron session later runs resume and immediately sees the objective, open questions, and next actions without re-reading prose logs. ## Quick Start Ask the agent to run coord-engine continuity resume for your team and agent name to load the latest snapshot brief before starting new work.

Frequently Asked Questions about fulcra-agent-continuity

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

FAQPage Schema
How do I save agent state before a session ends?

Run coord-engine continuity park with your team and agent name before the session exits. It snapshots every role you hold a fresh lease on and points each role doc's checkpoint_ref at the snapshot, exiting non-zero with CHECKPOINT NOT WRITTEN if nothing was saved.

How do I resume agent work after a cron wake or new session?

Run coord-engine continuity resume with your team and agent name before taking new work. It prints a deterministic brief with objective, next actions, open questions, and decisions, folding to the newest snapshot across your tasks.

Does continuity resume support freshness checks on snapshots?

Yes, the --max-age flag accepts durations like 30m, 12h, or 2d and exits with code 2 when the snapshot is missing, has unknown age, or exceeds the bound. JSON output distinguishes these via error_code values invalid-max-age, checkpoint-age-unknown, and checkpoint-stale.

What is the difference between continuity snapshot and freeform progress files?

Freeform progress.md files require a fresh session to re-read prose and infer what mattered. Continuity snapshots use the structured coord.teams.continuity.v1 JSON schema, so resume output is deterministic and machine-checkable rather than interpretive.

Why does continuity park fail with CHECKPOINT NOT WRITTEN?

Park exits with code 2 when you hold no fresh role leases, or code 1 when role state is unreadable rather than empty. Retry the unreadable case before ending the session, since a successful park is the only proof at least one checkpoint was written.