Claude Code workflow self-heals PRDs

The interesting part not just PRD generation, but the control loop: spec, split, execute, review, repeat. That makes it closer to a lightweight autonomous SDLC system than a prompt template.

• –GitHub issues become the planning substrate, which keeps the workflow visible and reviewable instead of burying state in chat
• –Splitting work into separate files and only advancing after each part reduces context drift and makes failures easier to isolate
• –The Codex review pass is the real “self-healing” layer, because it can uncover defects the original PRD missed
• –This is strongest for codebases that already have enough structure for agentic planning; on messy projects it could amplify churn if the review loop keeps generating scope
• –The repo reads like an open-source workflow framework more than a product, so adoption will hinge on how much setup overhead teams will tolerate