We've got a rule of thumb inside Stamen that issue names must read like imperatives: "improve variable names", "delete blah functionality", "fix broken jimmy-jammers", etc. Nothing focuses the mind of the reporter like being asked to specify what exactly they'd like to see done, and it's much easier for a developer to scan a list with actual tasks right in the sentence construction.
Recent articles
- First impressions of Claude Cowork, Anthropic's general agent - 12th January 2026
- My answers to the questions I posed about porting open source code with LLMs - 11th January 2026
- Fly's new Sprites.dev addresses both developer sandboxes and API sandboxes at the same time - 9th January 2026