The project memory your coding agents can actually work from.
Skopos keeps architecture, decisions, plans, patterns, active work, and important lessons in a predictable, repository-owned structure. Each agent receives the truth relevant to the work—not the entire history of the project.
docs/architecture/docs/decisions/docs/work/tasks/docs/patterns/01Architecture
02Decisions
03Plans
04Patterns
05Active work
06Evidence
More than an instructions file.
Every familiar tool preserves one useful part of the project. Skopos connects those parts to the work that is happening now.
Remembers the conversation
The context stays tied to that chat and becomes noisy or incomplete over time.
Guides how an agent should behave
It does not own active Tasks, scoped retrieval, Evidence, or Memory lifecycle by itself.
Can personalize one host
The project cannot reliably review, version, or carry that memory to another agent.
Explains durable project knowledge
Documentation alone does not connect that knowledge to work state, checks, or closure.
Memory that belongs to the repository.
Durable truth stays in tracked, human-readable files. Your team can review it in a pull request, version it with the code, and carry it to another supported agent.
- Tracked truth
- Decisions, Plans, Patterns, Tasks, and other durable Memory live under the project’s declared Memory roots.
- Disposable local state
- Indexes, caches, and runtime projections can be rebuilt. Deleting them does not delete the project’s durable knowledge.
docs/ ├── architecture/ ├── decisions/ ├── domains/ ├── patterns/ ├── scopes/ │ └── storefront/ │ ├── overview.md │ └── work/tasks/ └── work/plans/
.skopos/generated · rebuildableOnly the context this work needs.
Skopos uses the current Scope and Task to assemble a compact working brief. It includes relevant inherited truth and current intent without pretending every document is equally useful.
- Project-wide truth that applies everywhere
- Local truth owned by the affected Scope
- Task acceptance, boundaries, and remaining proof
T-7f3a91c2DecisionPayment finalization stays idempotent
PatternRecovery follows the existing checkout boundary
Required proofFocused recovery tests and typecheck
Updated when project truth changes.
Skopos does not silently rewrite documentation after every edit. Before a Task closes, durable impact is reviewed and resolved explicitly.
Work changes the project
The agent implements the bounded Task and gathers fresh Evidence.
Durable impact is reviewed
Skopos identifies the Memory role that may need attention and requires an explicit review.
Memory updated
A canonical tracked document is updated because the project’s durable truth changed.
Reviewed—no change
The existing truth remains sufficient, and the reason is recorded instead of manufacturing documentation churn.
Bring the project you already have.
Skopos first discovers the repository and proposes how its existing knowledge should fit the Memory standard. Material documentation changes wait for approval.
- 01Discover
Read the repository, docs, commands, and declared project boundaries.
- 02Propose
Show exactly what stays, moves, merges, splits, rewrites, archives, or disappears.
- 03Approve
A developer reviews material restructuring before Skopos changes human-authored Memory.
- 04Verify readiness
Confirm the reviewed Memory is coherent and reconstructable before agents rely on it.
What changes when Memory becomes part of the project.
| Capability | Chat | Instructions | Private memory | Docs | Skopos |
|---|---|---|---|---|---|
| Owned and versioned by the project | No | Yes | No | Yes | Yes |
| Retrieves context for the current Scope and Task | No | Limited | Host-defined | No | Yes |
| Carries active work and acceptance | Informally | No | No | Sometimes | Yes |
| Connects completion to fresh Evidence | No | No | No | No | Yes |
| Portable across supported agents | No | Partial | No | Yes | Yes |
Let the next agent start with the project—not an empty chat.
Set up Skopos without overwriting the truth your repository already contains.