Skip to content
Skopos
Documentation

Skopos works the way your project works.

Show it where project knowledge lives, which tools are trusted, what rules matter, and which coding agents you use.

Start with your project tools
01

Start with what you want Skopos to understand.

You do not need to learn the internal model first. Choose the part of your project you want agents to use more reliably.

01Connect your tools

Show Skopos how your project tests, builds, generates, previews, and verifies work so coding agents do not have to guess.

02Set project rules

Describe which checks apply, what agents may change, and when work must stop for approval instead of relying on every conversation to remember.

03Add expert guidance

Add focused guidance for design, architecture, security, or another domain without turning every prompt into a giant permanent instruction file.

04Connect coding agents

Use the certified Codex integration—or an explicitly described projection or manual workflow in another host—with the same Project Memory, Task lifecycle, and completion rules.

05Connect external services

Represent an approved provider operation as a governed project Action with explicit network, secret, service, approval, and effect boundaries.

02 · A real request

“Make checkout recover safely when the connection drops.”

The developer states the outcome. Skopos combines remembered project truth with the tools and protections this repository has chosen.

  1. 01Remember

    Load the checkout architecture and earlier payment decisions.

  2. 02Bound

    Limit the Task to recovery behavior and the files that own it.

  3. 03Equip

    Make the approved checkout test and typecheck Actions available.

  4. 04Require

    Apply the recovery and payment-safety Guards.

  5. 05Prove

    Attach fresh results to the Task as Evidence.

  6. 06Continue

    Keep the decision, progress, and next action for a fresh Session.

03

Learn the name after you understand the job.

The documentation introduces technical vocabulary only when it gives you more control.

Your toolsActions

Approved ways to test, build, generate, inspect, or operate.

Your rulesGuards and Policies

Deterministic requirements and accepted project standards.

Your expertiseSkills

Focused guidance selected for a relevant Task.

Your agentsHost adapters and MCP

Different agent environments using the same Skopos authority.

THE BOUNDARY

Extend how Skopos helps. Not who owns the truth.

Custom tools, rules, Skills, adapters, and services can contribute context, operations, and proof. They cannot create a second Task lifecycle, bypass project Guards, or declare their own Readiness.