continuity-management

Files (200)

• SKILL.md
• SKILL.md · agent-browser/
• SKILL.md · android/
• SKILL.md · android/compose/
• SKILL.md · android/debugging/
• SKILL.md · android/deployment/
• SKILL.md · android/gradle/
• SKILL.md · android/testing/
• LICENSE.txt · charts/
• SKILL.md · charts/
• _rules.md · charts/references/
• d3.md · charts/references/
• echarts.md · charts/references/
• matplotlib.md · charts/references/
• mermaid.md · charts/references/
• mindmap-css.md · charts/references/
• playwright-css.md · charts/references/
• radial-grid.md · charts/references/
• seaborn.md · charts/references/
• setup.sh · charts/
• SKILL.md · code-review/
• SKILL.md · coding-agent/
• _meta.json · coding-agent/
• criteria.md · coding-agent/
• execution.md · coding-agent/
• memory-template.md · coding-agent/
• planning.md · coding-agent/
• state.md · coding-agent/
• verification.md · coding-agent/
• SKILL.md · config-doctor/
• SKILL.md · database-design/
• schema-proposal.md · database-design/assets/
• SKILL.md · deep-research/
• tech-brief-template.md · deep-research/assets/
• SKILL.md · documentation/
• LICENSE.txt · docx/
• SKILL.md · docx/
• chart-templates.md · docx/references/
• common-rules.md · docx/references/
• decorations.md · docx/references/
• design-system.md · docx/references/
• docx-js-advanced.md · docx/references/
• docx-js-core.md · docx/references/
• faq.md · docx/references/
• math-formulas.md · docx/references/
• ooxml.md · docx/references/
• toc.md · docx/references/
• comment.md · docx/routes/
• create.md · docx/routes/
• edit.md · docx/routes/
• format.md · docx/routes/
• read.md · docx/routes/
• academic.md · docx/scenes/
• contract.md · docx/scenes/
• copywriting.md · docx/scenes/
• exam.md · docx/scenes/
• official-doc.md · docx/scenes/
• report.md · docx/scenes/
• resume.md · docx/scenes/
• __init__.py · docx/scripts/
• …and 140 more

SKILL.md (first lines)

# Continuity Management Skill

## Description

This skill converts the concept of "Continuity" from a static file into an active cognitive process. It dictates how the Scribe and Documentarian agents preserve context, maintain thermal maps of code, and serialize states for the Continuum Engine.

## Triggers

- **Session End:** When the current block of work is complete or the 2-week memory cycle approaches its limit.
- **Phase Transition:** When moving from one architectural phase (e.g., Phase 5) to the next (e.g., Phase 6).
- **Manual Invocation:** When the user requests a "Continuity Check" or "Strata Export".

## Workflow

1. **Episodic Compilation**: Use the `git` MCP to pull the diff of all uncommitted and recently committed changes. Summarize _why_ these changes were made.
2. **Semantic Knowledge Extraction**: Extract any new protocols, libraries, or architectural decisions (e.g., "Switched to `produce` for state mutation").
3. **Graph Injection**: Send the extracted entities and relations to the Knowledge Graph using `@itseasy21/mcp-knowledge-graph`.
4. **State Serialization**: Execute the local `tools/export-strata.js` tool to dump the current mental context, open files, and episodic summary into `./continuum/[date]-strata.json`.

## Best Practices

- **Do not write to a root CONTINUITY.md.** The state is living. Store it in the Knowledge Graph and JSON strata files.
- Always include the **Thermal Map**: List the top 3 most modified files in the current phase so the system knows what is "hot" upon resurrection.

From Zakarialabib/opencode, MIT.