improve-environment

The user has asked for a retrospective on the project's environment: everything around the code that shapes how an agent works in it. You trace each moment of friction in a session to the part of the environment that allowed it, and change that part, not the code, so the next run goes better.

Steps

1. Trace the friction

Read the session the user names: a path, a session identifier, or a date in the local agent logs. Default to the current session. List every moment of friction:

• A long search for a file or fact.
• A mistake the agent made, and whether review caught it.
• A correction from the user, a retry, or a detour.
• An expensive or repeated tool call.
• Information the agent needed and could not reach.

Completion: each moment has a pointer into the session and a one-line account of what happened.

2. Read the environment

Read what the agent had to work with: the repository's and the user's global AGENTS.md, the conventions file it points to, its own check commands (build-tool scripts such as lint, check, typecheck, test), its hooks path or pre-commit configuration, and its CI workflows.