Skopos — Project memory for coding agents

Project context, intent, rules, and proof stay in the repository—so work can continue without depending on one coding agent or conversation.

npm · @unisane/skopos@latest

Agent setup brief

Set up Skopos from the npm package @unisane/skopos@latest. Follow Skopos’s guidance one decision at a time, and stop whenever it asks for my input.

01Understand
02Clarify
03Review
04Apply
05Verify

Coding agents

Give every coding agent the same project context.

Codex
Claude Code
Cursor
GitHub Copilot

Example workflow · Checkout recovery

example/atlas-commerce

See what happens after you ask your coding agent.

The agent writes the code. Skopos recovers the project context, keeps the change bounded, runs the project-approved checks, and shows why the Task is ready to close.

Follow the complete request-to-proof loop

You ask

Fix the checkout recovery bug. If payment succeeds but order confirmation is interrupted, retrying must not charge the customer or create the order twice. Keep the payment provider unchanged and add focused tests for the recovery path.

01Your coding agent works.

02Skopos keeps the loop grounded in the repository.

11 of 4 · Load project context

Example Task · T-7f3a91c2

Checkout recovery after payment interruption

Status: Active
Scope: checkout
Owner: @payments-team

Memory

What Skopos found

The checkout can process the same payment twice when confirmation is interrupted. The recovery path is missing.

docs/scopes/checkout/overview.md
docs/decisions/D-012-checkout-reliability.md
docs/patterns/PAT-007-idempotent-finalization.md
docs/work/tasks/T-7f3a91c2-checkout-recovery.md

Task

What the agent should change

Add the recovery endpoint

apps/storefront/src/checkout/recovery.ts

Resume the interrupted checkout, finalize a pending payment exactly once, and confirm the order safely.

Boundary

What must not change

Preserve the accepted payment architecture

Do not replace the payment provider or rewrite unrelated checkout flows.

Proof · Evidence + Readiness

What proves completion

Blocked

The recovery tests must cover the new path before this work can finish.

One payment creates one order
Interrupted checkout can resume safely
Type check remains valid

Supporting detailView technical checks and proof details

Evidence & Action ledger

Focused Actions and source-bound Evidence for the example checkout recovery Task
Type	Description	Source	Status	Receipt
Test	Recovery flow returns exactly-once confirmation	`tests/checkout/recovery.test.ts`	Blocked	`Waiting for checkout.recovery-tests`
Test	Idempotent finalize prevents duplicate orders	`tests/checkout/finalize.test.ts`	Blocked	`Waiting for checkout.recovery-tests`
Build	Type check and build	`quality.typecheck`	Passed	`run-3427`
Lint	Lint changed checkout paths	`quality.lint`	Passed	`run-3427`
Docs	Update the work dossier	`docs/work/tasks/T-7f3a91c2-checkout-recovery.md`	Updated	`source-bound`

TestRecovery flow returns exactly-once confirmationtests/checkout/recovery.test.tsBlocked
TestIdempotent finalize prevents duplicate orderstests/checkout/finalize.test.tsBlocked
BuildType check and buildquality.typecheckPassed
LintLint changed checkout pathsquality.lintPassed
DocsUpdate the work dossierdocs/work/tasks/T-7f3a91c2-checkout-recovery.mdUpdated

Remember

Continue the work, not the conversation.

Skopos restores the decision, Task intent, and tracked project context so a new agent can continue precisely where the last one stopped.

Explore Project Memory

Coordinate

Use your project’s rules. Share one view of the work.

Skopos exposes project-approved Actions, applies Guards, and gives cooperating Sessions one auditable view of ownership, checks, and changes.

Actions do. Guards decide. Evidence proves.

See the working loop

Prove

Done needs evidence.

Skopos checks a Task’s acceptance criteria against fresh, source-bound Evidence, then explains what still blocks closure.

See how proof works