arckit-impact

Traverse reverse dependencies to classify impact severity and recommend remediation commands.

2.1k|266|Updated Oct 14, 2025
One-click install
npx skills add https://github.com/tractorjuice/arc-kit --skill arckit-impact
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arckit-impact
Source: https://github.com/tractorjuice/arc-kit/tree/main/arckit-codex/skills/arckit-impact
Command: npx skills add https://github.com/tractorjuice/arc-kit --skill arckit-impact

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps enterprise architects understand the ripple effect of changes to requirements, decisions, or design documents by tracing dependencies backward through the project artifact graph.

Core Features & Use Cases

  • Reverse Dependency Tracing: Identifies all artifacts that reference a specific change source.
  • Impact Severity Classification: Assigns a severity level (High, Medium, Low) to impacted documents based on their type and governance role.
  • Automated Action Recommendations: Suggests relevant ArcKit commands for remediation based on impact severity.
  • Use Case: When a core business requirement changes, this Skill quickly shows which architecture decisions, security documents, and operational procedures are affected, allowing for targeted updates and re-assessments.

Quick Start

Analyze the impact of changing the requirement BR-003.

Frequently Asked Questions about arckit-impact

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

FAQPage Schema
How do I analyze the blast radius of changing a requirement or design document?

To analyze the blast radius of a requirement change, perform reverse dependency traversal on your project's artifact graph to identify all affected downstream documents and assess their impact severity.

How does reverse dependency tracing work for architecture governance?

Reverse dependency tracing for architecture governance works by traversing a pre-built dependency graph backward from a changed requirement to identify impacted artifacts up to a depth of 5.

Can I classify impact severity based on document type during change management?

Yes, you can classify impact severity by assigning High, Medium, or Low levels to impacted documents based on their specific document type and governance role within the architecture.

Do I need a pre-built dependency graph to assess change impact?

Yes, you need a pre-built dependency graph provided in your context, which enables the efficient reverse traversal required to determine the blast radius and recommend remediation commands.

What is the maximum depth limit for dependency tracing in impact analysis?

The maximum depth limit for dependency tracing in impact analysis is 5, ensuring efficient traversal through the project artifact graph while identifying all relevant upstream references.