bip.epic.tuckin

Persist orchestrator state to durable storage before a context reset.

29|4|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/matsen/bipartite --skill bip-epic-tuckin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bip.epic.tuckin
Source: https://github.com/matsen/bipartite/tree/main/skills/bip.epic.tuckin
Command: npx skills add https://github.com/matsen/bipartite --skill bip-epic-tuckin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persist orchestrator state to durable storage before a context reset or session end to prevent loss of context and ensure continuity.

Core Features & Use Cases

  • Flush orchestrator state to durable storage before a context reset or session end.
  • Synchronize EPIC bodies and slot statuses across a session to keep project state coherent.
  • Update MEMORY.md and generate a concise report for the next session.

Quick Start

Execute the tuckin workflow to persist orchestrator state, update EPIC bodies and slot statuses, refresh MEMORY.md, and produce a final report.

Frequently Asked Questions about bip.epic.tuckin

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

FAQPage Schema
How do I persist orchestrator state before a context reset?▼

Executing the tuckin workflow synchronizes EPIC bodies and slot statuses across a session, updating .epic-status.json files and MEMORY.md to keep project state coherent and prevent data loss.

How do I update MEMORY.md and generate a final session report?▼

Running the tuckin workflow updates MEMORY.md and generates a concise final report, ensuring the next session has the necessary context and continuity for ongoing work.

When should I save orchestrator state to durable storage?▼

State persistence is needed before a context reset or session end to prevent loss of context, specifically for workflows that manage EPIC bodies, slot statuses, and MEMORY.md.

Does this state persistence workflow require external dependencies?▼

No, this state persistence workflow does not require external dependencies, allowing you to flush orchestrator state and update project files without additional environment setup.