fabric-process

Map external interactions and internal code execution chains into business process maps.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/adaw/skills --skill fabric-process
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fabric-process
Source: https://github.com/adaw/skills/tree/main/fabric-process
Command: npx skills add https://github.com/adaw/skills --skill fabric-process

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill creates and maintains a live map of business processes, detailing external user-system interactions and internal code-based process chains, crucial for understanding system functionality and impact analysis.

Core Features & Use Cases

  • External Process Mapping: Identifies and documents all user-system and system-system interactions.
  • Internal Process Tracing: Maps the causal chains of code execution from entry points to responses.
  • Cross-Mapping & Orphan Detection: Links external and internal processes, identifying undocumented or dead code.
  • Use Case: Before making a change to the scoring.py file, this Skill helps you understand which external user interactions and internal code chains it affects, preventing unintended consequences.

Quick Start

Use the fabric-process skill to map all external and internal processes within the codebase.

Frequently Asked Questions about fabric-process

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

FAQPage Schema
How do I map business processes and trace code dependencies in a Python codebase?

To map business processes and trace code dependencies, this Skill analyzes Python source code to map external user-system interactions and internal execution chains, generating a live process map for impact analysis.

What is code dependency tracing for change impact analysis?

Code dependency tracing for change impact analysis identifies the causal chains of code execution from entry points to responses, linking internal code changes to the external user interactions they affect.

How can I identify orphan code and undocumented processes during code analysis?

You can identify orphan code and undocumented processes by cross-mapping external user-system interactions with internal execution chains, highlighting dead code and undocumented processes for risk assessment.

Do I need defined process schemas to map system architecture and code execution chains?

Yes, you need defined process schemas and Python source code analysis to accurately map system architecture and trace internal code execution chains for risk assessment and change impact analysis.

What is the best way to assess risks before modifying a Python file?

The best way to assess risks before modifying a Python file is to map its internal code execution chains and cross-reference external processes, preventing unintended consequences to user interactions.