finding-to-issue-planner

To convert CodeBuddy review findings, you provide a finding source and output directory to generate grouped issue candidates with titles, evidence, and acceptance criteria as markdown and JSON files. This enables review and handoff without mutating trackers.

Yes, you can group multiple code review findings into cohesive issue candidates. The process enforces an explicit approval boundary to stop before tracker creation or repository mutation, ensuring safe planning without premature ticket generation.

Generating issue candidates requires specifying the finding source, mode, and policy. These inputs enforce policy-controlled grouping, evidence extraction, and approval boundaries to produce the output files under the artifact root.

Planning CodeBuddy findings produces issue_candidates.md and issue_candidates.json files under the artifact root. These formats support structured review, governance handoff, and potential operator action boundaries.

Yes, planning review findings enforces policy-controlled grouping, evidence extraction, and approval boundaries. This ensures that related findings are safely grouped into reviewable issue candidates for governance before any tracker mutation occurs.