Initech is handing small tasks to a coding agent, and the team's conventions live in senior engineers' heads and old PR comments. Your call: do you ask for a rules file before the agent starts, and what goes in it?
Key idea: A coding agent follows what it can see, like where migrations go, but it can't know the decisions your team made and never wrote down: tests beside the file, money in cents, text through t(). One page of rules is the cheapest fix, and CI is how you make sure the rules that matter hold.
Finish a run to see what a PM takes away from this lesson.
Conventions followed vs. words in the rules file
Plan the tasks to plot the run here
Things to try
- Run it as it starts: Fast, no rules file. Which conventions did it follow, and which did it break?
- Switch Rules file to Short AGENTS.md and run it again. What changed?
- Switch to Rules with examples. Do the examples help?
- Switch the agent to Smart and run Rules with examples, then Short AGENTS.md. What does it still skip?
- Set Rules file back to None, still on Smart. Does a bigger model guess the team's rules?