bootstrap-repo

To keep AGENTS.md and PLANS.md consistent across a repository, use a guided workflow that validates impacted paths and propagates changes to nested files. This prevents drift in contributor processes and preserves the root contract.

Updating repo-wide scaffolding rules requires an auditable workflow that aligns root and nested guidance. You inspect existing conventions, apply changes spanning multiple directories, and record updates in the appropriate documentation files to preserve governance.

You need to coordinate changes across multiple AGENTS.md files when updates span multiple directories or shared targets. Coordinating these changes ensures alignment with existing repository conventions and preserves artifact contracts.

Validating impacted paths works by checking the root and nearest nested AGENTS.md files before applying changes. This ensures updates follow a defined workflow and maintains the integrity of the root contract during scaffolding adjustments.

Yes, you can use this workflow to manage documentation for changes spanning multiple directories. It automates the maintenance of scaffolding guidance and records changes in AGENTS.md and PLANS.md, ensuring updates follow a defined workflow.

Contributor process drift happens when root and nested guidance files like AGENTS.md are updated independently. Without an automated workflow to propagate and document changes, alignment with repository conventions and artifact contracts is lost.