Skip to content
terragucciDocs

Plan grouping

llms.txtlists every page for an agent

A shared module change can reach two hundred roots with near-identical plans, and a reviewer scrolling for the odd one out can miss a destroy.

Grouping

Section titled “Grouping”

terragucci normalizes each root’s changes and groups the roots whose changes are the same.

180 roots: identical change (update aws_iam_role.app, tags)


 15 roots: the same, plus replace aws_lambda_function.worker


  5 roots: read these individually


destroys: prod-eu/db (delete aws_db_instance.main)

The reviewer reads the shared change once, then the 20 roots that differ.

The top of a plan report for a shared-module change with a destroy beside it: the destroy named on its own, two outliers to read first, and ten identical roots folded into one groupThe top of a plan report for a shared-module change with a destroy beside it: the destroy named on its own, two outliers to read first, and ten identical roots folded into one group

Rules by change

Section titled “Rules by change”
Change In the report
destroys, replacements, refusals, imports, forgets named, never grouped; a forget is not counted as a destroy
roots that differ from every group open
IAM and security group changes open
KMS and DNS changes open
groups of identical changes folded
updates to tags or descriptions only folded
values known after apply folded
roots with no changes folded

Each root and group links to its full plan in text and JSON. Approvals bind the plan digests, taken before redaction or rendering, so the summary’s wording never changes what was approved.

Next

Section titled “Next”

terragucci

These docs count page views and clicks with PostHog. They set no cookies, store nothing in your browser, and send nothing when your browser asks not to be tracked.