Is there a jobs feature now or forthcoming?

[odysseyalive]

Spec-kit is exactly what I needed. I do something similar, manually, creating checklists in Serena planning mode to generate todo lists. This helps me identify where the coder has any misconceptions before executing the task list. Spec-kit worked wonderfully for this! Thanks for releasing it in Opencode, so those with local LLM's can use it for sensitive tasks. I'd love to see Crush added to the list.

However, I'm a bit puzzled about the current process? Why is this set up once, and thrown away at the end of the first project build? Am I misunderstanding something? The documentation that Spec kit provides should be useful throughout the life of the project. This is the type of steerage that developers need, especially ones that run on local models. Instead of having to heave around larger-than-life models, this type of steerage allows devs to run smaller models, finetuned for tool calling and reasoning. With web search and page fetch MCPs and Context7, these smaller models are actually quite a bit better at being instructional and focused.

So, sorry for the long-winded opening. I had to lay that context down for my main question. Why aren't there jobs instead of a single tasklist that gets created and dumped? These jobs, once completed lay the ground work for setting up additional jobs throughout the life of a project. Spec kit should be about steerage throughout the life of the project.

[jeremyeder]

We will be capturing and storing permanently every artifact generated along the way. spec-kit is just one of the pieces of the flow. So yeah, you need to capture these things. Do you want spec-kit to offer like an export feature?