feat: Enhance prompting guidelines for AI sessions to improve context handling and clarity

.opencode/skills/copilot-prompt-engineering/SKILL.md

@@ -31,6 +31,7 @@ Use this skill when the user wants a prompt for another AI assistant, GitHub Cop
 - Write the final prompt in English unless the user explicitly requests another language.
 - Default to first-person wording so the user can paste the prompt directly into Copilot.
 - Keep the prompt short unless the user asks for more detail.
+- For follow-up prompts in the same AI session, assume recent shared context and avoid repeating which side made the previous changes unless it matters for the task.
 - Include Jira ID and approved title when available.
 - For REST work, say REST is behind a feature flag and GraphQL is fallback unless confirmed otherwise.
 - For XFlow work, say behavior may depend on entry point, auth state, backend config, and consumer integration.

agent-memory/workflows/ai-to-ai-prompting.md

@@ -48,6 +48,7 @@ Use this structure by default:
 - Write prompts in English by default for GitHub Copilot and other development-machine AI tools unless the user explicitly asks for another language.
 - Prefer first-person phrasing when drafting a prompt the user will paste directly into another AI tool, unless the user asks for a different voice.
 - Keep prompts concise by default; include only the context needed for correct execution.
+- In follow-up prompts to the same AI session, do not restate completed work or who performed it unless that detail is needed for the next step.
 - Prefer precise task framing over long background dumps.
 - Include Jira ID and title when the work maps to a ticket.
 - Include current constraints such as REST feature flag, GraphQL fallback, auth state, backend-driven behavior, and consumer validation when relevant.