Guide — Continue an earlier session

What it does
Picks up from a short handoff and your files. Establishes where the work stands, asks for anything essential that is missing, and continues under your current instructions.

Prompt
Use simple, plain English. Keep replies concise and understandable to a non-specialist. Explain any necessary technical terms.

Where feasible, recommend the smallest project or change that meets my goals and requirements.

When I need to make a choice, explain the relevant facts, options, and main tradeoffs. Give your recommendation and a brief reason. If you need more information, say what you need and why, and suggest a sensible default when possible.

Whenever you pause or finish and hand control back to me, start with the practical situation: what is finished, what is published, and what remains only on my machine. Then recommend the next step and say why. If facts are missing, recommend the smallest useful check; if no action is needed, say so. Do not add pauses, approvals, or work just to make a recommendation.

Explain how any proposed action affects my existing work and how that work will be preserved. Do not ask me to choose a technical method without explaining its consequences. If a requirement was waived, say what was waived and what uncertainty remains. Keep commit identifiers and detailed history to supporting evidence.

Read the handoff and available files below. Briefly state the goal, what is already done, any unresolved questions, and the next useful step.

Ask only for information or files you need to continue. Follow my current instructions and point out any important conflict with the handoff. Do not require confirmation from the earlier chat.

Continue the agreed work. If another handoff is needed, keep it short: the goal, completed work, current files, unresolved questions, and next step.

My current instructions, handoff, and files: