Run any Skill in Manus with one click

business-analyst

Stars0

Forks0

UpdatedFebruary 12, 2026 at 08:32

Analyzes the codebase to extract and document Business Logic, Domain Models, and Workflows. detailed understanding of "What the app does".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

hadimiftahulf

hadimiftahulf/antigravity-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Management AnalystsBusiness and Financial Operations Occupations·SOC 13-1111

SKILL.md

readonly

name	business-analyst
description	Analyzes the codebase to extract and document Business Logic, Domain Models, and Workflows. detailed understanding of "What the app does".

Business Analyst (The Domain Expert 🧠)

Understand the Why, not just the How.

Workflow: Domain Discovery

1. Model Mapping

Goal: Understand the Nouns.

Scan: Read app/Models (Laravel) or prisma/schema.prisma (Node).
Map: Identify relationships (HasMany, BelongsTo).
Core Entities: Who are the main actors? (User, Customer, Admin).
Transactional Entities: What is being moved? (Order, Invoice, Transaction).

2. Logic Extraction

Goal: Understand the Verbs.

Scan: Read Services, Observers, or Controllers.
Invariants: Look for if statements throwing exceptions.
- Example: "If balance < logic, throw Error." -> Rule: "Balance cannot be negative."
State Machines: Look for status columns. What are the allowed transitions? (e.g., Pending -> Paid -> Shipped).

3. Output: Domain Knowledge Brief

Generate a summary:

Core Workflow: "User creates Order -> Admin approves -> System generates Invoice."
Business Rules: "Discount cannot exceed 50%."
Critical Paths: Payment processing, Data export.

More from this repository

same repository

arch-reviewer

hadimiftahulf/antigravity-skills

Enforces modularity, reusability (DRY), and high-level architectural patterns. Focuses on SOLID principles, Design Patterns, and Scalability.

2026-02-120

deep-audit

hadimiftahulf/antigravity-skills

Universal architectural auditor for any tech stack. Enforces Separation of Concerns, Clean Architecture, and best practices by identifying the project structure and detecting layer violations.

2026-02-120

skill-activation-policy

hadimiftahulf/antigravity-skills

Defines rules for skill activation, including input requirements, output contracts, conflict lists, and performance costs. Enforces Lean Execution mode by default.

2026-02-120

advanced-architecture

hadimiftahulf/antigravity-skills

Implementation of Enterprise patterns: CQRS, Event Sourcing, Domain-Driven Design (DDD).

2026-02-120

api-connector

hadimiftahulf/antigravity-skills

Generates robust, production-grade 3rd party API integrations with Retry, Rate Limiting, and DTOs.

2026-02-120

brainstorm-feature

hadimiftahulf/antigravity-skills

Workflow for deeply researching and architecting a new module/feature. STRICTLY NO CODE EXAMPLES. Use this for high-level technical design and research before implementation.

2026-02-120

name	business-analyst
description	Analyzes the codebase to extract and document Business Logic, Domain Models, and Workflows. detailed understanding of "What the app does".

Business Analyst (The Domain Expert 🧠)

Understand the Why, not just the How.

Workflow: Domain Discovery

1. Model Mapping

Goal: Understand the Nouns.

Scan: Read app/Models (Laravel) or prisma/schema.prisma (Node).
Map: Identify relationships (HasMany, BelongsTo).
Core Entities: Who are the main actors? (User, Customer, Admin).
Transactional Entities: What is being moved? (Order, Invoice, Transaction).

2. Logic Extraction

Goal: Understand the Verbs.

Scan: Read Services, Observers, or Controllers.
Invariants: Look for if statements throwing exceptions.
- Example: "If balance < logic, throw Error." -> Rule: "Balance cannot be negative."
State Machines: Look for status columns. What are the allowed transitions? (e.g., Pending -> Paid -> Shipped).

3. Output: Domain Knowledge Brief

Generate a summary:

Core Workflow: "User creates Order -> Admin approves -> System generates Invoice."
Business Rules: "Discount cannot exceed 50%."
Critical Paths: Payment processing, Data export.