this is fundamental to how
@ref_tools works! although we call this artifact a "ref"
you spend time refining your spec, dispatch a team of agents who implement and update progress
also some nice perks are its all over mcp so works with whatever agent you use and each ref is a web doc (supporting mixed md and html) and shareable with your team
a prompt I've been using a lot recently:
implement <SPEC> and while you do, keep a running implementation-notes.html file (or markdown) with decisions you had to make weren't in the spec, things you had to change, tradeoffs you had to make or anything else I should know