The scenario
The checkout may contain intentional uncommitted work and incomplete checks.
Required context: a selected repository matching this scenario, relevant task evidence, and access to its instructions and checks. Use redacted or synthetic data where appropriate.
Adapt the complete prompt
Edits stay in this browser tab. Saving bookmarks the original example; export your edited version to keep it elsewhere.
Why this is a strong example
It preserves actionable state while warning the next session which facts can become stale.
A concrete outcome
Prepare a handoff so a new session can continue the current task safely.
The result can be assessed against an observable task rather than prompt length or confidence.
Boundaries and a method
Record objective, branch/commit, relevant files, decisions, actual evidence, unresolved issues and the next bounded action. Exclude secrets and unrelated conversation history.
This leaves implementation judgment while constraining the changes that would exceed the task.
Evidence that can disagree
Separate stable decisions from facts the next session must refresh, especially working-tree state and test results tied to older code.
These checks describe what would make acceptance justified; asking for them does not mean they ran.
A safe way to encounter uncertainty
If the repository contradicts these assumptions, required access is unavailable, or a consequential product decision is missing, explain the conflict and pause the dependent work. Preserve unrelated changes.
Consequential uncertainty stays visible rather than being converted into an invented requirement.