doc-fluxos

Trace code paths across files and layers into Markdown process documentation.

Updated May 18, 2026
One-click install
npx skills add https://github.com/AthosSchrapett/skills --skill doc-fluxos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-fluxos
Source: https://github.com/AthosSchrapett/skills/tree/main/doc-fluxos
Command: npx skills add https://github.com/AthosSchrapett/skills --skill doc-fluxos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of understanding complex application behavior by tracing execution paths across multiple files and producing accurate process documentation from existing code.

Core Features & Use Cases

  • Process Flow Mapping: Tracks execution chains from entry points such as screens, controllers, jobs, schedulers, handlers, and events through services, repositories, integrations, and databases.
  • Code-Based Documentation: Generates Markdown process documents that reflect the actual source code while avoiding assumptions about business rules or missing logic.
  • Legacy System Analysis: Helps developers understand unfamiliar features, endpoints, integrations, and routines before making changes.

Quick Start

Ask the doc-fluxos skill to document the execution flow of a specific endpoint, process, job, or feature by analyzing its entry file and related code.

Frequently Asked Questions about doc-fluxos

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

FAQPage Schema
How do I trace execution flows across multiple files in a legacy system?

Code-based documentation is generated by inspecting source code and tracing dependencies to produce structured Markdown output. This ensures the technical documentation accurately reflects the actual code paths without assuming missing business logic.

Can I document background jobs and event handlers from source code?

Yes, you can document background jobs and event handlers by tracing their execution paths from entry points through integrations and databases. This maps the complete process flow and generates accurate technical documentation for maintainability.

What is the best way to understand unfamiliar endpoint logic before making changes?

The best way to understand unfamiliar endpoint logic is process flow mapping, which tracks execution chains from controllers through services and repositories. This boundary detection clarifies behavior before you modify the source code.

Does code tracing documentation work for complex software architecture analysis?

Yes, code tracing documentation works for software architecture analysis by inspecting source code and detecting boundaries across multiple files. It produces structured Markdown that maps execution paths through various architectural layers.

Why does generated process documentation avoid assumptions about business rules?

Generated process documentation avoids assumptions about business rules to ensure accuracy when tracing legacy systems. By relying strictly on source-code inspection and dependency tracing, the structured Markdown output reflects actual execution paths without guessing missing logic.