dependency-driven-development

To stop stubbed behaviors during feature planning, you must enforce explicit dependency naming and reorder your roadmap to build missing primitives, schemas, and tooling before proceeding with dependent tasks.

Dependency-driven development is a feature planning process that mandates building missing prerequisites, such as non-existent commands or infrastructure, before allowing work to begin on dependent features.

You reorder a development roadmap by explicitly identifying missing infrastructure, schemas, or tooling required by a feature, then mandating the creation of those enablement primitives before starting the dependent task.

You need to enforce prerequisite creation during the development process when a planned feature relies on non-existent infrastructure, commands, or schemas, ensuring enablement work is prioritized to prevent incomplete code.

Building a new search feature requires an existing embedding model first, because dependency-driven development forces the creation of missing tooling and primitives rather than allowing incomplete or stubbed features to be developed.

Allowing features to start without explicit dependency naming leads to incomplete code and stubbed behaviors, because features are developed against non-existent infrastructure, commands, and schemas without prioritizing necessary enablement work.