Prompt Repetition

When to use this skill

• The user is using a non-reasoning or lightweight model and accuracy drops when the important question appears late in the prompt.
• The prompt shape is long-context retrieval, options-first multiple choice, or position-sensitive lookup.
• The user wants a bounded decision rule for whether to duplicate the prompt 2× or 3×, not a vague promise that prompt engineering will help.
• The workflow needs a cheap experiment before changing models or building retrieval infrastructure.
• The request mentions things like the model forgot the question, missed the final instruction, lost the item at slot 25, got confused by a long options list, or performs worse on Haiku / Flash / mini models than on stronger reasoning models.

Do not use this skill as the main workflow when:

• The real problem is context selection, retrieval design, or noisy source stuffing → use broader context-engineering or RAG work.
• The real problem is reasoning depth and a reasoning-capable model is available.
• The prompt is tool-heavy / agentic / multi-step, where duplicating the full prompt may just multiply cost and confusion.
• The user needs a universal always-on middleware policy. This skill is for targeted use, not blanket auto-apply.

Core idea

Prompt repetition is a task-shape-specific intervention, not a universal prompting law.