create-agents-files

Hierarchical AGENTS.md files are generated by defining a target scope, gathering package evidence, and enforcing parent-child inheritance. Non-root files must declare Inherits and optional Overrides before writing to preserve policy authority.

An AGENTS.md hierarchy provides structured, evidence-based guidance for nested packages by enforcing consistent inheritance and policy. You need one when a domain requires formal guidance per package across a repository.

Child AGENTS.md files inherit parent policies by explicitly declaring an Inherits field. They can apply targeted scope updates by declaring optional Overrides or Additions, ensuring parent-child policy is preserved while allowing local customization.

Yes, AGENTS.md generation requires rigorous evidence gathering from package structure, dependencies, and call-site data. This evidence-driven approach ensures validation-ready output designed for downstream tooling to lint and validate the hierarchy.

The best way to maintain policy alignment is enforcing hierarchy integrity through linked parent and child AGENTS.md files. This ensures scope is defined per package and non-root files declare Inherits before writing, preserving authority across the repository.

Yes, you can update a single package by defining the targeted scope and declaring optional Overrides or Additions in the non-root file. The hierarchy enforces that the child file declares Inherits, preserving the parent policy authority.