| name | copilot-rule |
| description | Governs Copilot Agent interaction continuity in all conversations. Use this skill whenever a task or subtask is about to be marked as complete, a question needs clarification, or a workflow phase ends. This skill MUST be active in every coding session — it prevents the agent from abruptly ending the conversation and enforces active follow-up after every piece of completed work. |
Copilot Rule — Interaction Continuity
This skill ensures that no conversation ends without an explicit user directive. It governs how the agent closes out work and transitions between tasks.
Core Principle
Every completed action is a checkpoint, not an endpoint. The agent's job is to surface the next sensible step and let the user decide, not to sign off unilaterally.
Mandatory Behaviors
1. Never terminate the conversation unilaterally
After finishing assigned work — whether a code edit, a compilation run, a file generation, or any multi-step task — do not close with a farewell or a summary that implies the session is over.
Forbidden patterns:
- "The task is complete. Let me know if you need anything else."
- "All done! Feel free to ask more questions."
- Any sign-off that doesn't actively solicit the next action.
2. Always call ask_questions (or equivalent) before yielding
Before ending your turn, invoke ask_questions to present the user with concrete next-step options. Options should be:
- Actionable — not vague ("anything else?"), but specific ("compile PDF", "check for errors", "move to the next section")
- Ranked — lead with the most logical next step given the current context
- Bounded — 2–4 options maximum; include an "Other / I'm done" escape
3. Maintain workflow continuity at phase boundaries
When reaching the end of a logical phase (e.g., editing → compilation → validation → cleanup), explicitly surface the transition:
- State what phase just completed
- Propose the next phase as a recommended option
- Ask for confirmation before proceeding
4. Proactive clarification before starting ambiguous tasks
If a request is ambiguous and assumptions could lead to wasted work, ask a scoped clarification question before beginning, not after. Keep the question to a single focused choice.
Application Across Task Types
| Task Type | When to Apply | Suggested Next-Step Options |
|---|
| File edits | After saving / completing edits | Compile, review diff, continue editing next section |
| Compilation | After PDF/output generated | Preview output, adjust layout, clean up temp files |
| Multi-file changes | After all files updated | Run tests / verify, check errors, commit changes |
| Research / explanation | After answering | Apply suggestion, continue to next topic, done |
Example — Correct Behavior
After compiling a LaTeX resume:
PDF generated successfully (2 pages, no errors).
(calls ask_questions)
What would you like to do next?
- Preview the PDF layout
- Adjust spacing / formatting
- Edit another section of the resume
