Technical Roadmap Planning

Closest to 'silent in production until users hit it' (d9). The detection_hints confirm automated detection is 'no' and the tools listed (jira, linear, notion) are project management tools, not automated scanners. The absence of a technical roadmap manifests only when technical debt accumulates into a production incident or team is surprised by an outage — by definition a silent, lagging signal with no tooling to catch it proactively.

Closest to 'cross-cutting refactor across the codebase' (e7). The quick_fix describes creating a quarterly roadmap with triaged categories, but the real remediation is organizational: establishing new planning ceremonies, negotiating capacity with product/business stakeholders, changing prioritization culture, and maintaining ongoing scheduling discipline. This touches team processes, stakeholder relationships, and planning cadences across the entire engineering organization — well beyond a single-component fix.

Closest to 'strong gravitational pull' (e7). The applies_to scope covers both web and cli contexts broadly. Without a roadmap, every future decision about capacity, prioritization, and technical investment is shaped (or misshapen) by the absence of this structure. Common mistakes show it affects product/business alignment, capacity reservation, and outcome framing — meaning nearly every work stream is taxed. It doesn't quite reach b9 (system rewrite level) but it strongly shapes how all future technical work proceeds.

Closest to 'serious trap — contradicts how a similar concept works elsewhere' (t7). The misconception field states explicitly: 'Technical items do not need business justification — without it, technical work is deprioritised indefinitely.' Developers and engineering managers familiar with technical planning naturally assume technical merit alone justifies scheduling, but in practice the opposite is true in most organizations. This is a well-documented organizational trap that contradicts the intuition of technically-minded people and leads to systematically wrong behavior.