Comment by try-working
16 hours ago
that's why you need a recursive workflow that creates its own artifacts per step that can later be used for verification.
16 hours ago
that's why you need a recursive workflow that creates its own artifacts per step that can later be used for verification.
Sounds interesting, can you elaborate on your thinking? Got me curious.
how do you verify the work that was just done in the current stage? verify against the output artifacts from the previous stages. for example, if you have a requirement doc, then you can analyse the codebase for current state, and store as a doc. then generate the implementation plan based on the delta between requirements and current state. after implementation, create an implementation summary doc. to verify the implementation in the next stage, compare the implementation summary against the implementation plan, the previous codebase analysis and the original requirements doc, as well as codebase diffs.
so, every stage outputs a source of truth for that stage, which can be used by later stages for verification, alone or together with other artifacts. if you want to read more, here's the recursive-mode development workflow I built: https://recursive-mode.dev/introduction