Claim
Sprint-loading AI tools and skills before a real task exists creates unused scaffolding and cognitive overhead. Task-driven acquisition forces each skill to prove its value in a live context before it enters the working stack. Skills installed without a forcing task tend to be forgotten or misused.
Mechanism
A skill installed in response to a real task embeds in a concrete workflow. A skill installed in anticipation of a hypothetical task has no natural home and no immediate accountability test. The forcing function is the task itself: it defines what the skill must do, and the outcome reveals immediately whether it helped. Without that loop, skills accumulate without earning their place.
Conditions
Holds when: the learner is iterating on a live workflow and can test each skill against real output immediately.
Fails when: the domain requires deep upfront knowledge before any task is possible, or when the cost of discovery-by-doing is too high.
Evidence
Huryn:
"don't install skills you don't need. Start with none and add one when a real task forces it."
Signals
- Each installed skill maps to a specific recurring task
- Zero skills carried over from previous sprints without a current use case
- Skill count stays low even as output volume grows
Counter-evidence
Some teams prefer to survey the full skill landscape first to identify unexpected capabilities. Sprint-loading can surface tools that reshape the workflow in ways a task-driven approach would never reach.
Cross-references
- ins_aakash-gupta-paste-twice-test
- ins_bottleneck-is-context-not-capability