Issue Template: Nit-Bundle
Issue Template: Nit-Bundle
Use this template for QA nits from an approved PR that aren't blockers. Nits are bundled into a single Forgejo issue per PR rather than scattered as individual items. The bundle lands on the project board's backlog for triage — Betty Sue can segment into separate issues later if individual nits warrant their own scope.
When to Use
- QA approved a PR with nits (findings that don't block merge)
- Post-merge, during
/update-docs, nits need tracking - Multiple minor findings from a single review that relate to the same body of work
Nit-Bundle vs Bug vs Feature
| Signal | Type |
|---|---|
| QA approved but flagged non-blocking improvements | Nit-Bundle |
| Something that worked before is now broken | Bug |
| A new capability we want to add | Feature |
| We don't know what's wrong or how to scope it | Spike |
Forgejo Issue Template
Lifecycle
- Created during
/update-docs— Betty Sue creates the nit-bundle issue on the relevant repo after merge - Auto-syncs to project board backlog — via board sync, like any Forgejo issue
- Plan Epilogue gets a reference — not the nits themselves, just: "Nits from PR #X tracked in repo #Y"
- Triage — Betty Sue reviews during board triage, segments if needed, moves to todo when scoped
- Dispatch — follows normal kanban flow (todo → next_up → agent → PR → merge)
Why Bundle?
Individual nits are too small to be useful tickets. Bundled nits share context (same PR, same review, same area of code). The bundle gives Betty Sue a single item to triage rather than 5 separate items cluttering the backlog. If a nit turns out to be significant, it gets split during triage — that's what the Segmentation Notes section is for.
Related
template-issue-feature— feature varianttemplate-issue-bug— bug varianttemplate-issue-spike— spike varianttemplate-issue— canonical issue design principleconvention-todo-lifecycle— triage rulesglossary— nit definition