A readable project specification makes generated changes easier to review. The project file still matters, but regeneration should be intentional and reproducible.

Spec change → Generator → Project diff → Build
  1. 1Spec change
  2. 2Generator
  3. 3Project diff
  4. 4Build

Work through the example

Prompt: Explain the target change in project.yml, regenerate with the documented tool, then show the resulting project diff.

One practical example

Use the prompt above on one small, named part of your app. Before accepting an edit, ask the agent to point to the source or configuration that supports its answer. If it cannot locate that context, resolve the missing input before expanding the task.

In the diagram, each arrow represents a handoff you can inspect. Keep the intermediate result rather than jumping directly to the final claim. For example, a reported finding should retain its location, and an executed check should retain its outcome. This gives the next attempt a concrete starting point and makes a misleading completion message easier to challenge.

Apply it to your project

Prompt: Explain the target change in project.yml, regenerate with the documented tool, then show the resulting project diff. Then compare the resulting diff with the original request. If it changed a neighboring concern, ask why that change was necessary. Save the result only after the relevant check has run, and record any part that remains unverified.

Evidence and limits

Do not regenerate with an unrecorded tool version or overwrite unrelated manual changes.

This is an educational guide. Its presence in the series does not certify a completed client-specific lab. The series evidence record separates executed checks from exercises and blocked environments.

Inspect the source used in this lesson.

What to do next

Next: Use `#available` audits before every beta upgrade