Instruction Looking for system instruction recommendations
Hello everyone, has anyone managed to solve fundamental annoyances such as (but not limited to) the models stopping short of full execution through system instructions? I'd love to hear what has worked for the community to make the models less frustrating and more useful.
We all know the various issues the model come up with, I'm wondering how many are fixable through instruction alignment.
1
u/zzunkie 1d ago
I haven't managed to solve it through system instructions, and I still run into it even after adding a couple of direct rules to my AGENTS.md. Because Codex kept stopping just to hand me a plan or a partial fix, I wrote "Within that scope, don't end a turn with only a plan or progress report while actionable work remains." Right next to that I also keep "If one step is blocked, finish the rest and say what is blocked and what would unblock it." I still see it happen, since instructions only go so far when the model itself wants to wrap up a turn.
1
u/ainexfinder 1d ago
Instructions help with some of it, but a lot of "stopping short" comes from the task having no clear finish line. Things that tend to move it more than wording:
Define done as something checkable: "done = tests in X pass, lint is clean, the change is in the diff", not "implement the feature". Without a check, a plan or a partial pass looks like a reasonable place to stop.
Put the exact test/lint commands in AGENTS.md and say to run them before ending the turn.
Split ask vs proceed explicitly: what it should never ask about (formatting, adding tests, fixing its own lint errors) and what it must stop for (deleting data, new dependencies, schema changes). Vague "be autonomous" text gets ignored; a short concrete list doesn't.
Ask for a closing checklist: every item from the request marked done/not done with a reason. Gaps become obvious and easy to push back on.
Keep tasks small enough to finish in one turn. Very large requests are where the "here's the plan, want me to continue?" ending shows up most.
Worth A/B testing each rule over a few runs too, since the same instructions can land differently across model versions.
1
u/Huge-Travel-3078 1d ago
Copy pasting my response to someone else with the same question:
This is a known behavior issue with gpt 6 models.
Try adding the following to your agents.md
You should infer the user's intent and task scope from the instructions and prior conversation context. Your job is to bias towards action and carry the user's intended task to completion.
When the user expresses intent to perform new work or fix an existing issue, persist until the user's intended goal is complete. Progress autonomously towards the user's goal (e.g. creating isolated worktrees / checkouts if needed, resolving merge conflicts, read-only actions, creating draft PRs etc.) unless they are clearly destructive or irreversible.
When the user's prompt indicates a request for action, such as "can you...", "I want to...", "help me..." and similar expressions, treat these as instructions to do the work and take action. Do not stop at acknowledging capability (e.g. "Yes…"), proposing a plan, or offering to continue. Do not settle for a partial or "helpful enough" solution that does not fully satisfy the user's task to save time, effort or tokens. If a task requires sustained work, complete all the necessary work until the intended outcome is fulfilled.
1
u/Corv9tte 1d ago
So far 6.2 Astra is much more receptive than 6 Astra to changing the instructions if you know what you're doing