Agent System Authoring Checklist
This page is written for AI agents that author Brezel system drafts. It is not a product tutorial and not a replacement for the format references. Human developers can use it as a checklist, but the wording is intentionally operational.
When an agent builds a Brezel feature, the draft should contain the files that make the feature usable in preview, not only the first file that can be written. A feature draft often combines schema changes, layouts, navigation, permissions, workflows, templates, and preview configuration.
Required checks
Section titled “Required checks”- Inspect existing modules, layouts, menus, workflows, and related files before writing.
- Keep related module, layout, workflow, menu, role, policy, view, and test changes in the same draft.
- Write detail and index layouts for user-facing modules.
- Use targeted JSON patches for existing grouped files such as menus and roles.
- Provision or refresh the preview after the draft contains the requested pieces.
- Run relevant tests before requesting approval.
Draft consistency rule
Section titled “Draft consistency rule”Keep related files in the same draft so the preview represents the complete feature state. Splitting a module definition, its layouts, and its menu entry across different drafts makes the preview difficult to verify.
Use targeted JSON patches for existing grouped files such as menus and roles. Rewriting a whole grouped file for a single entry increases the risk of dropping unrelated resources.
When to stop
Section titled “When to stop”Continue through safe authoring steps after a feature request. Stop for missing permissions, destructive live changes, irreversible approval, or business requirements that cannot be inferred from the existing system.