Prompt Bloat
Every bug fix adds a sentence to the system prompt — nothing ever gets removed — until the prompt is unmaintainable and full of contradictions.
Intent & Description
🎯 Intent
Treating the system prompt as a scratch pad for bug fixes — appending forever, removing never, because removing a line feels riskier than leaving it.
📋 Context
The agent has been live for months. Each complaint adds an instruction. Nobody owns the prompt as a whole. A year later it’’s 2,000 lines, no single person understands it end to end, and the model is resolving contradictory instructions at random.
💡 Solution
Treat the prompt like code — PR review, eval gate on length, quarterly pruning sprints. Lift recurring procedures into agent-skills. Move stable rules into a constitutional charter. See prompt-versioning, agent-skills.
Real-world Use Case
- Never use this; treat unbounded prompt growth as a process failure, not normal maintenance.
- Use prompt-versioning and eval gates on length to keep prompts in budget.
- Lift recurring procedures into agent-skills and stable rules into a constitutional charter.
Source
📌 TL;DR
Treat your system prompt like source code — review it, prune it quarterly, and lift recurring procedures into skills.
Disadvantages
- Token cost per turn rises monotonically
- Every prompt edit blows the KV-cache
- Contradictory instructions accumulate — and the model picks one at random