name: cad-distress-annotation description: Delineate evidence-based road distress or demolition areas in existing CAD drawings, with closed boundaries, combined-structure quantities, category hatches, length/count callouts and legends. Use for road treatment, demolition and revisions; do not infer treatment or invent extents from target totals.

Road Distress and Demolition Annotation — v0.1.0-rc.1

Convert confirmed engineering scope into editable native CAD outcomes. Reuse the existing metre-road rules; distress severity, treatment depth and field observations cannot be inferred from demolition history. 中文规则. Read engineering examples when these cases apply and capability limits before native execution.

Start or resume

Confirm DWG, units, model/layout space, existing frame/legend, survey/design versions, quantity-table version and current revisions. Resume the authorized drawing without rebuilding its frame or replaying earlier batches. Keep analysis sources read-only; preserve an appropriate pre-edit backup. Explicit source-edit authorization governs whether to use the original or a working copy.

Inspect actual connected tools and schemas. A CAD year or file on disk does not prove an MCP connection. Identify the target process/document/backend and supported entity semantics. Use bounded diagnostics. After an uncertain write, query the original request and existing handles; never switch tools to duplicate it. Old 2022 access details do not establish a 2026 route.

Record boundary, hatch, text, leader, original and archived handles for every group. Resume from native state and latest approved changes; do not restore ranges cancelled by the user.

Evidence, extents and classification

• Locate areas using existing conditions, terrain/distress surveys, latest design boundaries and explicit user evidence. Tables identify items/structures and compare quantities; they do not supply spatial evidence. Satellite imagery is optional. Specify missing boundary evidence and progress with confirmed portions.
• New treatment symbols can indicate affected old surfaces only after checking the treatment method; new assets are not old assets. Match old drainage inlets by surveyed shape/layer/location and unique correspondence rather than counting every same-name block in the drawing.
• Preserve real offsets and one-sided work. Do not center a range or include an unaffected side to match a total.
• Use native closed polylines and hatches for area ranges, including junctions. Preserve true arc bulges, holes and retained regions. Do not assume an open line is a closed demolition area. Genuine small defects remain evidence.
• Count each surface once and label its combined structure, such as surface plus base. Separate categories by splitting/union where necessary. Removing multiple layers does not create multiple planar surfaces at the same location.
• When continuous demolition contains local demolition at posts, measure the geometric union and suppress duplicate local depictions within it; keep local areas outside it. New posts do not establish the old shoulder line.

Quantities and details

• Native closed boundaries determine area; dedicated polylines determine length; deduplicated existing facilities determine counts. Volume requires explicit thickness and measurement meaning. Cumulative layer area is not another planar region. Displayed numbers must agree with native readback.
• Resolve evidenced structure attribution before comparing totals. Never widen/move boundaries or invent items to fit a table. Report legitimate differences; one project's permission to exceed a table is not a universal acceptance rule.
• Put stepped demolition details in the existing pavement-structure detail location and cite that sheet from the plan. Do not fill an arbitrary blank in the plan. If the structure sheet is outside authorized scope, prepare calculations/proposed changes and complete independent plan work first.
• When dimensions are needed, use native DIMENSION objects with dimension/extension lines and approved fonts. After scaling or cross-drawing copying, read actual text height and scale properties independently; geometric scaling does not prove final lettering. Respect this project's approved style instead of assuming a universal yellow-line rule. This requirement does not mean Foundation exposes dimensions.
• Distinguish ditch line length from developed brickwork area. New utility paths can inform impact, but demolition geometry must follow the old ditch and authorized station interval. Unknown width/depth/wall structure cannot be uniquely recovered from a total area. Length-only labelling requires the task's agreement.

Callouts, legend and small fragments

Use colors/hatches with one-to-one category legend entries. Linear items use dedicated measurement polylines, point items use counts, and neither uses area units.

For ordinary single-line text, yellow dot, associated LEADER/MTEXT and finite placement, load the installed sibling cad-callout-pair-layout/SKILL.md; public rules. This Skill owns scope, not callout geometry. Preserve explicitly requested multiline notes.

Summarize tiny fragments and inspect origin before treating them as clipping/numerical remnants. Prefer merging confirmed remnants into an adjacent same-category face, never across structures. If the user authorizes label-only hiding, hide text and associated leader together while retaining boundaries/hatches/quantities. A historical strictly-less-than-0.1-square-metre threshold is case-specific, not a minimum valid distress size or a threshold for other drawing units.

Lay out new/affected labels using their own remaining finite budget; old groups are fixed obstacles. Report unresolved positions after the budget. Existing objects alone do not prove collision-free appearance.

Read back new objects and associations before hiding old labels. Archive only the identified objects, including obsolete labels/leaders/duplicate legends, to an off/frozen/non-plot layer. Preserve restoration and do not turn off a shared layer such as layer 0.

Delivery

Check affected closure, hatch path/native area, structure text, associated handles, duplicates/omissions and visibility. Separate area accuracy from path/position: equal area does not prove coincident geometry. Routine area comparison within 0.001 square metres is acceptable for this workflow; choose positional/width/length tolerances separately for their engineering effect, not from the area threshold.

Record save state/DBMOD, file digest and exact checked scope. Save and reopen are separate evidence; do not claim reopen when it did not happen. Report engineering differences, manual visual items and backend issues separately. Do not expand a requested partial handoff into unrequested whole-drawing acceptance. If asked to close CAD, save authorized writable targets, close references/targets normally and verify exit.

This public rules package includes no native CAD writer, automatic installer or engineering fixtures. Foundation provides supported operations and execution governance; other verified task-authorized routes can execute additional operations but do not automatically share its journals/fences. The full historical workflow is not certified using Foundation v1 alone. See installation and validation.

CAD Distress Annotation — Road Distress & Demolition Skill for AI Agents

中文 · Install · Compatibility · Validation · Release v0.1.0-rc.1

Evidence-based road distress and demolition annotation rules for AI agents working with AutoCAD. The first public rules preview preserves existing professional decisions and revision practices. It guides boundaries, combined-structure quantities, category hatches, length/count labels and legends; it does not determine distress treatment without engineering evidence.

• Locate affected old surfaces/facilities from confirmed surveys/designs; retain one-sided and offset ranges.
• Count each surface once, preserve arcs/holes and separate surface area, cumulative layer area, length, counts and volume.
• Compare native quantities with engineering tables without changing extents to match totals.
• Resume from handles and approved revisions; archive superseded objects and distinguish save from reopen evidence.
• Use the independently maintained callout Skill for ordinary LEADER/MTEXT styling and finite placement.

This is an installable Agent instruction package, not a CAD plugin, geometry engine or MCP server. No Python runtime is needed to read this Skill. Actual CAD execution needs verified native tools. Foundation supplies supported bounded operations via MCP/CLI; its current profile does not cover the complete demolition workflow. Other backends require explicit capability/identity checks and task authorization.

Metre-road rules and historical multi-tool AutoCAD 2026 evidence are documented separately from this publication. AutoCAD 2022 and complete Foundation-only execution are not certified. Read the synthetic decision examples and existing anonymous visual case; neither is a replay dataset or new native acceptance.

Download the release ZIP and follow manual installation. English SKILL.md and Chinese SKILL.zh-CN.md are included; keep resource folders together. Maintainer: capskov. Owned rules/documentation: Apache-2.0, see NOTICE.

Related terms: AutoCAD, CAD annotation, road distress, pavement demolition, civil engineering, engineering quantities, AI agent Skill. Independent project; no Autodesk endorsement.