Use Wicked Ticket to map plans from Claude Code and Grok Build to your existing SLDC tools, keeping stakeholders, project managers, and product managers in the loop while you employ agentic harness,..
Interesting approach... and will follow your progress. Have you seen spec-kitty? It solves similar problems...but, prefers to keep all the tracking artifacts in the repo next to the code. One benefit of that is that agents can load all ADRs, bugfixes, etc. into context for better comprehension of project history and iterations (why a decision was made etc). Doesn't solve for your PM, QA persona...but, provides significant benefits. Good luck with the project
Also ticket systems can be a vector into the todo.json file. This way, the stakeholders can use the tools they are familiar with to help drive the direction of the project.
Interesting approach... and will follow your progress. Have you seen spec-kitty? It solves similar problems...but, prefers to keep all the tracking artifacts in the repo next to the code. One benefit of that is that agents can load all ADRs, bugfixes, etc. into context for better comprehension of project history and iterations (why a decision was made etc). Doesn't solve for your PM, QA persona...but, provides significant benefits. Good luck with the project
Also ticket systems can be a vector into the todo.json file. This way, the stakeholders can use the tools they are familiar with to help drive the direction of the project.
See above. Same. Stores near code but exports different views to SLDC systems to maximize visibility with stakeholders
Ah, I see that now. Nice, will try it out.
This stores the artifacts next to the code as well. Then exports them to where stakeholders can interact.