workflow-tracer

Workflow Tracer Command

Trace a complete end-to-end workflow through the codebase, showing exactly what happens step-by-step from a business perspective.

Objective

Given a workflow name, feature, or user action (e.g., "user registration", "checkout process", "order approval"), trace the complete execution path through all layers of the codebase and explain what happens at each step in business terms.

Step 1: Workflow Identification

If User Provided a Workflow Name

• Search for relevant API endpoints, event handlers, or functions matching that name
• Identify the entry point (API endpoint, CLI command, scheduled job, event handler)

If No Workflow Specified

• List common workflows found in the codebase:
  • User authentication/registration
  • CRUD operations for main entities
  • Payment/transaction processing
  • Data import/export
  • Approval/review workflows
  • Notification/alert processes
  • Scheduled batch operations

Ask the user which workflow to trace.

Step 2: Entry Point Analysis

Document how the workflow is initiated:

## Workflow: [Workflow Name]

### Entry Point
**Trigger**: [API call / User action / Scheduled job / Event / etc.]
**Location**: `file_path:line_number`

**For API Endpoint**:
- **Method**: [GET/POST/PUT/DELETE]
- **Path**: `/api/path/to/endpoint`
- **Authentication**: [Required/Optional]
- **Request Format**:
```json
{
  "field1": "value",
  "field2": 123
}

For Event:

• Event Name: [event.name]
• Event Source: [Where event is published from]
• Event Payload: [Data structure]

For Scheduled Job:

• Schedule: [cron expression or frequency]
• Trigger Conditions: [When it runs]

## Step 3: Step-by-Step Trace

Follow the execution path through all code layers:

### Tracing Methodology
1. Start from entry point
2. Follow function calls
3. Track data transformations
4. Identify decision points
5. Note database operations
6. Track external API calls
7. Follow to completion or error states