You say
“Make checkout recover safely when the connection drops.”
Skopos keeps the outcome coherent from the first discussion through proof, Memory review, and the next Session.
01One continuous example
02Prompts and exact commands
03Developer review at every stage
Talk normally. Keep every important step reviewable.
Move through the seven stages below. The prompt establishes intent; the command path shows the same authority precisely.
01 · Discuss
Start with the outcome, not a command sequence.
Describe the behavior you want in ordinary language. Let the agent ask only the questions that change direction, risk, or public behavior.
“Make checkout recover safely when the connection drops. Before proposing code, inspect the current checkout flow and tell me what decisions, constraints, and unanswered questions materially affect the approach.”
npx skopos session context . --actor <id> --session-id <session-id> --host <host> --json
What Skopos handles
- Recovers current project and Session state
- Surfaces an existing Task when one already owns the outcome
- Keeps questions tied to meaningful product or engineering choices
What you review
- Does the agent understand the user-visible outcome?
- Are important payment or recovery choices still assumptions?
- Is this one feature or several independently ownable outcomes?
DONE MEANS
The feature works, the proof is fresh, and the project remembers why.
- Interrupted checkout resumes through one recovery path
- Payment finalization remains idempotent
- The customer receives one confirmed order
- Fresh project checks cover the new behavior
- The accepted recovery rule remains in Project Memory
NEXT GUIDE
Continue in a fresh SessionContinue the work in a fresh Session.
Learn how to move current intent and live project state without replaying or summarizing an entire old conversation.