prepare-prompt

# Prepare prompt Write for a session holding only this text — no chat history, no memory of what was meant — and make it as short as that reader allows: nothing it needs is cut for brevity, nothing else stays. The reader is a fresh interactive session the user pastes it into; a subagent brief only when the invocation asks for one, under the same rules. ## Input The user's goal, in a line, plus this session. Draft at once; ask only what neither settles — typically whether the next session may change things or only report — one question at a time, with a recommended answer. ## Content A suggested order, every part optional: a part is never filled to exist, and two lines are a complete prompt when two lines cover the case. 1. **Situation** — what exists that the next session builds on, and what is open or was missed, each with its identifier (ticket URL, branch, commit, PR, task ids). 2. **Task and deliverable** — what to do, and in what form to report or produce it (a chat report with a given structure, a file, a code change). 3. **Latitude and boundaries** — what it may decide alone, when deviating is fine, what it must not touch (read-only, no git or tracker writes, files to ignore). 4. **Facts it cannot derive** — paths, the planning directory, docs to read, tool quirks with the workaround, a command that saves time. The deliverable form and the write boundaries are the usual gaps: check whether the case needs them. What stays and what goes: - A fact the...