A common approach to working with coding agents is to hand them a prompt and hope for the best. Another is to first make a plan or specification. In both cases, unresolved ambiguities and assumptions often remain hidden until the code appears, and by then it is harder to change.
What if the spec becomes the source of truth, and we can incrementally improve it using specialised agents?
If you've spent any real time with coding agents, you've probably noticed: one-shotting a greenfield project is the easy part. The hard part is getting the agent to implement exactly what you had in mind. This is my latest attempt at solving that problem.
Always wanted your terminal to look and function like that of a professional developer? This post is my attempt at providing a concise guide to setting up a modern terminal, while explaining essential terminology and decisions made along the way.
To make for a truly slick experience, I have considered different terminals, shells, prompts and hotkeys, as well as command-line tools and plugins, including typeahead and fuzzy search.