Ir al contenido

Scaffolding

De Scrum Manager BoK
Esta página es una versión traducida de la página Scaffolding. La traducción está completa al 100 %.
⏱ 3 min  ·  📅 2026
Scaffolding is the automatic generation of the basic structure of a software project or module: the directories, files, components, configurations, and boilerplate code needed to start working. Its name comes from the metaphor of construction scaffolding: a temporary structure that supports the work without becoming part of the final building.

Scaffolding has existed in software development since long before generative AI—frameworks such as Ruby on Rails, Angular, and Django have included scaffolding generators since their earliest versions—but AI has transformed its scope and capability: where scaffolding once produced predefined, generic structures, AI agents can generate customized, context-aware scaffolding from a natural language description.

Types of scaffolding

  • Project scaffolding: the complete initial structure of a new project: directories, configuration files, base dependencies, CI/CD pipeline, README.
  • Component scaffolding: generating a new component following the patterns of the existing project: file structure, base tests, imports.
  • API scaffolding: generating the endpoints, data models, and base documentation from a specification.
  • Test scaffolding: generating the test structure (describe/it blocks, setup/teardown) for a module or component.

Scaffolding with generative AI

Coding agents have turned scaffolding into one of the highest-return tasks in the fast lane:

  • Starting from a high-level description, the agent generates the complete structure of the project or component in minutes.
  • AI-generated scaffolding can follow the patterns and conventions of the existing project if it is given the right context through context engineering.
  • The spec is the most effective mechanism for guiding scaffolding: specifying the expected structure, naming conventions, and dependencies enables the agent to generate scaffolding that is much more closely aligned with the actual project.

Scaffolding and technical debt

Automatically generated scaffolding can introduce technical debt if it is not critically reviewed:

  • The scaffolding's conventions may not match those of the project.
  • The base code may include unnecessary dependencies or insecure default configurations.
  • The generated structure may not be the most suitable for the specific use case.

Human review of the scaffolding—before building on it—is especially important because problems in the project's base structure become more costly to fix the later they are detected.

Common mistake

Accepting AI-generated scaffolding without reviewing it because "it's just the base structure." The base structure determines how everything that comes after it is organized: naming conventions, separation of concerns, and security configuration. Scaffolding with incorrect decisions in authentication configuration or secrets management introduces vulnerabilities that will be inherited by every module built on top of it.

See also

Want to advance in agility? You can search for course and exam calls or go at your own pace by becoming a member of the Agile Club. This membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills at your own pace.