<feed xmlns='http://www.w3.org/2005/Atom'>
<title>claudomator.git/docs/superpowers/plans/2026-07-09-story-fix-and-reevaluate-loop.md, branch main</title>
<subtitle>claudomator — task automation server
</subtitle>
<id>https://git.terst.org/claudomator.git/atom?h=main</id>
<link rel='self' href='https://git.terst.org/claudomator.git/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://git.terst.org/claudomator.git/'/>
<updated>2026-07-09T01:42:13+00:00</updated>
<entry>
<title>docs: add implementation plan for story fix-and-re-evaluate loop</title>
<updated>2026-07-09T01:42:13+00:00</updated>
<author>
<name>Peter Stone</name>
<email>thepeterstone@gmail.com</email>
</author>
<published>2026-07-09T01:42:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.terst.org/claudomator.git/commit/?id=c5d7adadf25cbb97e3f3e7cb3bf8f0593b010412'/>
<id>urn:sha1:c5d7adadf25cbb97e3f3e7cb3bf8f0593b010412</id>
<content type='text'>
Closes the recursive-story-decomposition design spec's "fix-and-
re-evaluate loop has to become real" gap -- today NEEDS_FIX is a dead
end requiring manual human intervention. Design decision (re-point
story.RootTaskID at a fresh fix-attempt task, vs. spawning as a
dependent of a fixed root) made with user input before writing this
plan.
</content>
</entry>
</feed>
