Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/bitwikiorg/continuity/llms.txt

Use this file to discover all available pages before exploring further.

A state pack is a curated collection of state files that work together as a coherent system for one operating mode. Unlike copying a single template, a pack gives you every file an agent in that role actually needs — the task queue, the safety rules, the snapshot, the approval gates — already cross-referenced and ready to instantiate. Pick the pack that matches your agent’s role, copy the files into your project directory, replace the {{PLACEHOLDERS}}, and your agent has a complete state chain from day one.

​
Available packs

PackPurposeFiles
developerGeneral coding agentAGENTS, INIT, STATE, TODO, PLAN, SNAPSHOT, CHECKPOINT
backendAPIs, databases, auth, jobsAGENTS, STATE, TODO, WARNING, CHECKPOINT
frontendUI, routes, componentsAGENTS, STATE, TODO, CHECKPOINT
researcherLong-running researchAGENTS, STATE, TODO, MEMORY, KNOWLEDGE, LEARNINGS
judgeEvaluation and reviewAGENTS, RUBRIC, CLAIMS, EVIDENCE, DECISION, RISKS
securityRisk and secrets controlAGENTS, THREAT_MODEL, WARNING, CHECKPOINT, INCIDENTS
opsInfrastructure and productionAGENTS, INFRASTRUCTURE, RUNBOOK, WARNING, SNAPSHOT
orchestratorMulti-agent coordinationAGENTS, TASKS, PLAN, EVENTS, SNAPSHOT, BINDING.schema.json
docs-writerDocumentation systemsAGENTS, TODO, STRUCTURE, STYLE

​
Selection guide

If your agent…Use this pack
Writes code across the stackdeveloper
Owns APIs, databases, or backend servicesbackend
Owns UI, routes, or componentsfrontend
Gathers information over multiple sessionsresearcher
Evaluates, reviews, or approves workjudge
Manages security, secrets, or incidentssecurity
Manages infrastructure or productionops
Coordinates other agentsorchestrator
Writes or maintains documentationdocs-writer

​
How to use a pack

1

Choose a pack

Match your agent’s primary responsibility to the pack in the selection guide above. If the agent straddles two roles, pick the pack that covers the riskiest operations — you can always add files from a second pack afterward.
2

Copy the files

Copy all files from the pack directory into your project directory. Keep the filenames as-is — AGENTS.md is the universal entry point, and the state chain is wired by filename convention.
cp -r continuity/packs/developer/. ./my-project/
3

Fill the placeholders

Every pack file contains {{PLACEHOLDERS}} for values specific to your project. Replace them before pointing your agent at the files.
PlaceholderMeaningExample
{{PROJECT_NAME}}Project or service nameauth-service
{{DATE}}Date stamp2026-06-29
{{READY_OR_BLOCKED}}Status declarationREADY
{{BRANCH}}Current git branchmain
{{BLOCKERS_OR_NONE}}Active blockers or NoneNone
4

Point your agent to the entry file

The entry file is whatever your runtime loads first: AGENTS.md, CLAUDE.md, INIT.md, BOOT.md, or another adapter file. Configure your runtime to load that file at the start of each session.
5

Delete what you don't need, add what you do

Not every file in a pack will apply to every project. Remove files you won’t use. If you need something not in the pack — TOOLS.md, MEMORY.md, ARTIFACTS.md — add it. Packs are starting points, not locked configurations.

​
Combining packs

When an orchestrator agent coordinates multiple specialist agents, place the orchestrator pack at the root and each specialist pack in its own subdirectory. Each agent loads only its own state chain — agents never load sibling packs. 
/AGENTS.md     /TASKS.md     /PLAN.md        # orchestrator pack at root
├── backend/
│   ├── AGENTS.md
│   └── STATE.md                             # backend pack
├── frontend/
│   ├── AGENTS.md
│   └── STATE.md                             # frontend pack
└── research/
    ├── AGENTS.md
    └── MEMORY.md                            # researcher pack
The orchestrator reads its own TASKS.md to assign work. Each sub-agent reads its own AGENTS.md and follows its own state chain. Safety rules set at the root accumulate downward — a child pack cannot weaken a parent constraint.

​
Not a framework

Packs are markdown templates. They declare state; they do not enforce it. Your runtime, hooks, and review process handle enforcement. The pack gives you a wired starting point — the structure is in the files, not in code.
Continuity only requires that the agent loads the right state chain and writes back changed state. How that loading and writeback happens — via a hook, a system prompt, a custom runtime, or a simple file read at session start — is entirely up to your infrastructure.

​
Pack pages

Developer

Coding agents with INIT, STATE, TODO, PLAN, SNAPSHOT, and CHECKPOINT.

Backend

API and service agents with WARNING gates for data-destructive operations.

Researcher

Long-running research with MEMORY, KNOWLEDGE, and LEARNINGS layers.

Orchestrator

Multi-agent coordination with TASKS, EVENTS, and machine-readable BINDING contracts.

Other Packs

Frontend, judge, security, ops, and docs-writer packs.

Tiers

Understand required, recommended, and optional file tiers before customizing a pack.

Build docs developers (and LLMs) love

Get started for freeTalk to us