backlog-routing-by-topiclisted

# Backlog Routing by Topic ## When to invoke - A "don't handle now but don't forget" idea comes up mid-discussion. - Tidying a meeting log and re-homing parking-lot items. - User asks "where does this idea go", "should backlog be split by file". ## Routing rules | Topic | Destination | |---|---| | **Product / gameplay / UX / feature proposal** | `docs/design.md §Backlog` | | **Tooling / packages / language features / CI / Secrets / L10n** | `docs/foundations.md §Backlog` | | **Implementation step / refactor / test coverage expansion** | `docs/plan.md §Backlog` | | **Collaboration mode / agent skill setup / review flow** | `docs/methodology.md §Backlog` | | **Unclassifiable / highly divergent** | Today's `meetings/{date}_*.md` §Open questions | ## Entry format One line each; if context is needed, attach the meeting log date as a sub-bullet: ```markdown - Adopt `XcodeSelectiveTesting` to only run impacted test targets in CI (2026-05-15) - Developers can reproduce GitHub Actions workflows locally via `nektos/act` - Note: act has limited macOS runner support; reconsider when designing §4 CI (2026-05-15) ``` - One line preferred; only add a sub-bullet when context is essential. - Date goes in parentheses at the end so you can trace back to the originating meeting log. ## Procedure 1. Identify the idea's **topic category** (using the table above). 2. **Don't** expand the discussion on the spot — write one line, continue the current task. 3. If ambiguous (product + tooli