undefined | Better HN

0 pointsmusebox351mo ago0 comments

I am exploring ways to document the design for the agent to read and update. What makes it difficult is the lack of structure. Spec writing is not my core skill. Schemas and APIs are easier, there are declarative ways to document them. Runtime concepts and workflows have less structure and writing prose seems so unstructured for my taste. Formal languages are too rigid. But I could not find a better way.

0 comments

2 comments · 1 top-level

tssge1mo ago· 1 in thread

For me writing manpages as a spec worked well. While the format is unintuitive and tedious (at least to me), I used AI to format the manpages from my descriptions and rendered to PDF to review. Though it's been mainly useful for CLI utilities.

Once I got the manpages ready and the way I wanted, I just stored those in an empty project folder and told the agent to implement as specified in a language of my choosing.

Maybe for other development scenarios like GUI there is some "native" way to spec the project in a common format like this.

musebox35OP1mo ago

Thanks, that sounds like a good direction to try.

j / k navigate · click thread line to collapse