business-logic-orientation

Map existing business logic with file paths, line numbers, and mermaid diagrams.

6|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/exception-coder/team-standards --skill business-logic-orientation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: business-logic-orientation
Source: https://github.com/exception-coder/team-standards/tree/main/skills/business-logic-orientation
Command: npx skills add https://github.com/exception-coder/team-standards --skill business-logic-orientation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents unsafe code changes by forcing a structured, verifiable understanding of existing business logic before any refactor, rewrite, migration, or regression work begins. It captures scenario matrices, precise code locations, mermaid diagrams, and an AI-optimized index so engineers, product, and AI agents can reliably find authoritative implementation details.

Core Features & Use Cases

  • Structured Scoping: Confirm module name, scenario boundaries, and purpose to limit analysis scope and avoid drift.
  • Precise Code Indexing: Produce file and method tables with verified line numbers and core code snippets for quick navigation.
  • Visual Knowledge Maps: Generate mermaid-based sequence, flow, and swimlane diagrams plus entity/state/call graphs and an AI-ready compact index.
  • Use Case: Before refactoring a payments module, run this skill to produce a dated snapshot report, an AI index for agents, and a regression checklist tied to exact code lines.

Quick Start

Provide the module name, scope, and objective, and ask the assistant to generate a full business logic orientation document and AI index following the provided template.

Frequently Asked Questions about business-logic-orientation

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

FAQPage Schema
How do I map and document existing business logic before refactoring?▼

To map business logic for refactoring, generate a structured orientation document containing verified file paths, line numbers, mermaid diagrams, and a compact AI-ready index of your software module.

How do I create an AI-ready code index for a software module?▼

Create an AI-ready code index by reading source files to record precise file paths, method tables, and core code snippets, producing a compact index optimized for AI agents to find authoritative implementation details.

What is the best way to visualize business logic and code dependencies for regression review?▼

The best way to visualize business logic for regression review is generating mermaid-based sequence, flow, and swimlane diagrams, alongside entity, state, and call graphs tied to exact code lines.

Can I use this business logic documentation approach for both frontend and backend systems?▼

Yes, this business logic mapping approach applies across frontend, backend, and full-stack systems, verifying code by reading source files to produce a dated snapshot report for safe migration or onboarding.

How do I define scenario boundaries when documenting business logic?▼

Define scenario boundaries by applying structured scoping to confirm the module name, scenario limits, and purpose, which limits analysis scope and prevents drift during the documentation process.

Why do I need a structured orientation document for a code rewrite?▼

You need a structured orientation document for a code rewrite to prevent unsafe changes by forcing a verifiable understanding of existing business logic, capturing scenario matrices and precise code locations before work begins.