newton

Map change contracts and dependencies to classify impacts and recommend handling.

4|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/satsilem/claude-skills-pantheon --skill newton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: newton
Source: https://github.com/satsilem/claude-skills-pantheon/tree/main/skills/newton
Command: npx skills add https://github.com/satsilem/claude-skills-pantheon --skill newton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Map and predict how changes ripple through a system, identifying downstream effects and blast radius before and after changes.

Core Features & Use Cases

  • Define a change (old vs new contract) and identify direct dependencies (inbound/outbound/data/triggers/config).
  • Trace propagation across dependencies to classify impacts (breaking, behavioral, latent, none) and surface surprises.
  • Recommend handling for each impact (update before, update simultaneously, or communicate) and provide a full blast-radius report for planning.

Quick Start

Describe a proposed change, then map its direct dependencies and trace propagation to reveal the blast radius.

Frequently Asked Questions about newton

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze the blast radius of a proposed system change?

Mapping cause-and-effect ripples requires tracing propagation across dependencies down to at least two levels, classifying impacts as breaking, behavioral, or latent, and outputting a recommended handling per impact for pre-change planning.

How does dependency propagation tracing work for change management?

Dependency propagation tracing works by mapping inbound and outbound contracts, tracking triggers and data flows across at least two dependency levels, and classifying downstream impacts to predict system-wide effects before or after a change.

Can I use this to assess risk for organizational policy changes?

Yes, risk assessment applies to organizational policies and processes. By defining the old versus new policy contract, you trace downstream propagation to classify impacts and surface surprises across affected organizational structures.

What is the best way to map downstream effects before modifying software contracts?

The best way to map downstream effects is defining the old versus new contract, identifying direct inbound and outbound dependencies, and tracing propagation to generate a full blast-radius report for change planning.

Does blast radius analysis require tracing beyond direct dependencies?

Yes, blast radius analysis requires structured tracing down to at least two dependency levels to accurately classify downstream impacts and provide a recommended handling strategy for post-change diagnosis.