Set up Skopos once. Then talk to your coding agent normally.
Start with a conversation, use commands when you need precision, and inspect every important decision before it becomes project truth.
Open the quickstart01Choose how you are starting
02Prompt by outcome
03Use commands for precision
Your first step can be a conversation.
You do not need to memorize the CLI before Skopos becomes useful. Tell the agent what kind of project this is and require it to preserve existing truth before changing anything.
Follow every quickstart step“Set up Skopos in this repository. First inspect the source, existing documentation, project instructions, and working commands. Do not restructure or overwrite anything yet. Show me what is canonical, what conflicts, what is missing, and the proposed Project Memory structure before applying changes.”
Choose the path that matches your project.
Each path starts with the outcome, shows what to say, explains what Skopos handles, and keeps exact commands close by.
Add Skopos to an existing project
Preserve current code, docs, commands, and conventions before proposing a clearer Project Memory structure.
Start carefullyStart a new project
Create a clean repository-owned foundation for purpose, Scope, decisions, work, and project checks.
Start cleanContinue current work
Recover the active Task, relevant project knowledge, remaining checks, and the next safe action.
Continue workUnderstand the product model
See how discussion, Project Memory, bounded work, Actions, Evidence, and Readiness form one loop.
Follow the loopWork with your agent in plain English.
Start with the result you want. Skopos supplies the project context, boundary, checks, and continuation state that the conversation alone cannot guarantee.
Go deeper only when you need to.
The public guide keeps common work approachable. Canonical Markdown remains available for exact architecture, configuration, and reference details.
Start
Installation, guided setup, host context, and first verification.
Concepts
Understand why the product behaves this way.
Configure
Connect the tools, rules, expertise, and agent environments your project already uses.
Reference
Use the canonical source when exact commands and contracts matter.
Help
Recover safely when setup, work, checks, or coordination do not behave as expected.
Begin with one repository and one honest review.
Installation is short. Trustworthy setup begins by understanding the project you already have.