agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/cat-agent-skills/submissions/engineering-change-bom/skills/bom-impact/SKILL.md

bom-impact

Skill95 starsChanged 6 days agoMITView on GitHub

Traces the change across the BOM with where-used and rolls up form/fit/function impact, interface violations, document updates and inventory disposition - deterministically. Use when the user says "what does this change affect", "run where-used", "impact analysis", or after ecr-ingest in a change run.

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After ecr-ingest in every change run.

    line 11
  2. Very specific:

    Run scripts/where_used.py --ecr ecr.json --bom bom.json --out traced.json

    line 16
  3. Very specific:

    Run scripts/bom_impact.py --traced traced.json --docs docs.json --inventory inventory.json --out impact.json

    line 17
  4. Distinctive:

    Every affected item cites its BOM link.

    line 22
  5. Distinctive:

    All tracing and classification happens in the engines.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

BOM Impact

Purpose

Deterministic impact: where_used traces every parent; bom_impact classifies impact (#1), applies the interface rule (#2), the document rule (#3) and inventory disposition (#4).

When to use

After ecr-ingest in every change run.

Inputs

ecr.json + bom.json + docs.json + inventory.json.

Steps

  1. Validate against the contract.
  2. Run scripts/where_used.py --ecr ecr.json --bom bom.json --out traced.json
  3. Run scripts/bom_impact.py --traced traced.json --docs docs.json --inventory inventory.json --out impact.json
  4. Quote the rollup verbatim. An INTERFACE VIOLATION escalation is never softened - a "cheaper tolerance" on a mated feature is a function change, whatever the ECR calls it.

Output

impact.json - the {impact} hop.

Grounding requirements

Every affected item cites its BOM link; every document row cites the register and rule #3.

Constraints

  • All tracing and classification happens in the engines; the model never re-classes an impact.

Escalation / uncertainty

Incomplete trace (#5), obsolete referencing documents (#3): engine escalates; the ECN stays blocked.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free