Agentic Skill Atrophy

Problem

Developers form judgment by struggling with architectural choices, debugging failure modes by hand, and accumulating the implicit feel for system weaknesses that the Norwegian source names 'utilsiktet kunnskap' (unintentional knowledge). When agents handle those decisions, the struggle stops and the implicit knowledge stops accumulating. After enough months, the team can no longer reliably review what the agent produces — they accept plausible-looking diffs because they lack the buried experience to spot wrong-shape solutions — and cannot recover the system when the agent fails or is unavailable. The Danish source names the same mechanism specifically for junior developers shipping code they themselves cannot explain.

Solution

Don't let the team's hands stop. Preserve agent-free time on architecturally important work; rotate juniors through debugging-by-hand and design-without-agent sessions. Pair this with rigor-relocation: name the artifacts where the team's discipline now lives (a context file the agent reads, lint and structural-test constraints the agent cannot override, continuous verification that compares output against original intent). Use eval-as-contract and decision-log to keep judgment externalised and reviewable even as individual practitioners' implicit knowledge shrinks. Treat skill atrophy as the team-shape counterpart of review-bottleneck-migration: the review side fails not just because of volume but because reviewers lose the implicit knowledge they once had.

When to use

• Never. Cite when reviewing a team's adoption plan for agentic coding tools.
• Demand explicit agent-free practice time and externalised review artifacts (context file, constraints, continuous verification).
• Track review-quality and recovery-capability metrics over time, not only throughput.