flow

Scan a repository and generate a Markdown flow document.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/andrelucassvt/verify_local_purchase --skill flow-andrelucassvt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flow
Source: https://github.com/andrelucassvt/verify_local_purchase/tree/main/.agents/skills/flow
Command: npx skills add https://github.com/andrelucassvt/verify_local_purchase --skill flow-andrelucassvt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maps and documents end-to-end feature flows by scanning the repository and generating a Markdown document describing the full flow — files involved, call order, layer responsibilities, and business rules. Use this to save and share a trace of how a feature works.

Core Features & Use Cases

  • Automatically generate a flow document describing entry points, layers, and data flow.
  • Output the document to ./flow/<flow-name>.md for persistence and review.
  • Helpful for onboarding, code reviews, and impact analysis across features like login, checkout, signup.

Quick Start

Describe the feature flow you want mapped and specify its name to generate ./flow/<name>.md.

Frequently Asked Questions about flow

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

FAQPage Schema
How do I map feature flows end-to-end in my codebase?

To map feature flows end-to-end, this Skill scans your repository to produce a Markdown document detailing files, call order, layer responsibilities, and data movement. You simply describe the feature and specify a name to generate the mapping file.

How do I automate documentation for a feature's call order and data flow?

Automating feature documentation is done by scanning repository entry points and layers. The Skill generates a Markdown file at ./flow/<flow-name>.md, automatically capturing business rules and how data moves through the system.

Does automated feature mapping work on any repository structure?

Automated feature mapping requires the repository structure to expose clear entry points, layers, and dependencies. It uses repository navigation tools to reference real files, so poorly structured codebases may lack the clarity needed to map correctly.

What is the best way to trace business rules across a feature's layers?

Tracing business rules across layers is best handled by generating a flow mapping document. This Skill scans your codebase to detail layer responsibilities and data movement, outputting a persistent Markdown trace for review and onboarding.

When should I not use automated codebase mapping for feature flows?

You should not use automated codebase mapping when your repository lacks clear entry points, layers, or dependencies. The process relies on navigating real files and class names, meaning unstructured codebases will not produce reliable flow documentation.