The scenario
The repository has manifests, scripts and documentation that can be inspected. Unknown setup details should remain explicitly unknown.
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
The generator is constrained to evidence and useful rules rather than generic policy boilerplate.
A concrete outcome
Draft concise repository instructions using only verified project facts and existing conventions.
The result can be assessed against an observable task rather than prompt length or confidence.
Boundaries and a method
Identify essential commands, boundaries and review expectations. Reuse good existing guidance, remove duplication and keep detailed procedures in appropriate references. Add no permissions or credentials.
This leaves implementation judgment while constraining the changes that would exceed the task.
Evidence that can disagree
Check every proposed command against a source. Distinguish commands actually tested from those only found in configuration, and show the proposed diff.
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.