For a solo developer, working locally with an agent can remain a personal craft. For a team, the same arrangement becomes a systemic problem: the company can no longer see how results are actually produced.

Most engineering work used to happen inside issues, commits, and code review. Now a separate production process appears between the brief and the final code: an agent explores the project, builds a plan, writes the implementation, and runs checks; a person sends the result back, changes skills, switches models, adjusts the harness, and makes decisions. Yet the issue tracker still shows a single line: “task assigned to developer.”

This is why agentic development still scales in a peculiar way. Every person gets an increasingly capable personal factory, but the team does not gain shared production. It sees the product but not how it was made—and therefore cannot measure, compare, transfer, or improve that process. A company will not become AI-native while this work remains invisible and evolves by intuition.

What to know before reading

Agent stackThe agent’s complete working environment: model, harness, and interface. The harness, in turn, defines instructions, context, skills, tools, permissions, and execution rules.
HarnessThe program and rules around the model: they assemble context, provide access to tools, and manage the work cycle and approval points.
SkillA reusable instruction, body of knowledge, or procedure for a particular class of tasks that the harness makes available to the agent.
Token costThe cost of a model’s input and output tokens. To calculate the full cost of a result, add this—or a share of the subscription—to the cost of the developer’s active involvement.