I tried something new: writing a loose spec, and having Thaura turn it into a more solid spec.

I wanted a toolkit to help make workflows in folders. So I found a project that was old, and used it as a use case. Then I wrote a Markdown file that:

• Told Thaura to look at this project and two other more current projects as use cases.
• Wrote a very sparse and not-very-good spec about the kinds of patterns I expect to support. Things like routing input files into different folders.
• Then I wrote instructions telling Thaura to write a critique, and then stop. I added a second instruction to write specs, and then stop.

Once it wrote the critique, it asked if I wanted to update the Revision document. I did, and the result is below.

After revision, it produced the specs, and then the code itself.

Some observations:

• Having prior art to study seems to help constrain the design (which is a good thing).
• The critiques of my spec seemed to reflect the prior art, as well as general principles of software design.

Here’s what Thaura Work wrote: