A particular Jira issue increasingly becomes a benchmark for work the developer did in advance: configuring the harness, writing a skill, selecting tools, and formalizing project conventions.
When a task is completed in one shot, the person’s role is impossible to understand. Did they merely copy the issue title—or spend weeks turning project expertise into executable instructions? If the task is not completed in one shot, a strong developer usually does not begin writing it by hand. They debug the pipeline: why the agent called one tool twenty times, why it chose the wrong prefab, or which context the skill lacked.
Meanwhile, Jira says the person “built a prefab from a mockup,” even though they may never have opened the mockup. Their actual work was improving the UI layout skill and the harness that should solve the entire class of similar tasks. The tracker records the final instance but loses the creation of the production method.