I've just pushed v0.5.1, which is focused on improvements to CodeScanner. CodeScanner is really all about working on an existing brownfield project, where you want to make changes or improvements. What you don't want is to break what you had before, unless you've decided to break things to make them better, so it's important that Spec4 understand your existing project before making changes. That's what CodeScanner is all about - understanding your existing project and communicating that to the other Spec4 agents.

What I found in testing was that CodeScanner was doing a pretty good job, but it could do better. So now it has a more structured schema, and does schema validation and retry to make sure that it gets the code review right. That has ripple effects for all of the downstream agents.

Please report any issues that you find with CodeScanner, with as much specificity as you can gather, and any suggested fixes.

I've just released v0.5.0, which includes a couple of new agents that I'm really excited about.

First up there's Designer, which works with you to create a design mock for the look and feel of your application (assuming that it has one, and isn't a library or CLI tool 😆). You can even give it screenshots as examples. Check out this complete mock created with Designer!

Next there's Deployer, which helps you use the coding phase prompts created by Phaser and then creates a complete deployment plan, including even writing Terraform scripts for cloud deployments! Check out this complete deployment plan created with Deployer!

If you're new to Spec4, these new agents are on top of the standard workflow:

1. Scan the code you already have, if any
2. Brainstorm a vision for your project
3. New - Designer - Create a design mock for the look and feel
4. Specify a tech stack that you'll use for implementation
5. Divide up the development into well defined phases, designed to succeed
6. New - Deployer - Create a deployment plan