Your Claude Code is Starving, the Food’s Scattered All Over Your Org, and Some of it is Stale

How to build the context layer that spec-driven development assumes already exists and keeping it fresh Spec-driven development is the right instinct. Write precise intent before you ask an agent to act on it. Define the acceptance criteria, the constraints, and the architectural boundaries. Give the agent a contract rather than a vague description and watch the output improve. There is a problem with this, and it sits one layer below the spec. Consider a well-written engineering ticket. Specific file paths. Exact property names. Explicit “do not create this” constraints.