cqt-agent/expansion-packs/hubtel-workflow/tasks/business-context-provider.md

CQT Agent

# Business Context Provider

## ⚠️ CRITICAL EXECUTION NOTICE ⚠️

**THIS IS AN EXECUTABLE WORKFLOW - NOT REFERENCE MATERIAL**

When this task is invoked:
1. **BUSINESS CONTEXT ONLY** - Focus on business logic, user flows, and validation rules
2. **NO TECHNICAL QUESTIONS** - Domain, patterns, and integration are auto-determined from codebase
3. **PRECISE EXECUTION FOCUS** - Only gather information needed for successful implementation

## Overview

This workflow gathers business context missing from Azure DevOps tasks to enable precise implementation. Technical decisions (domain placement, coding patterns, integration approach) are automatically determined from codebase analysis.

## Input Parameters

### Required Parameters
- **task_ids**: Array of Azure DevOps task IDs requiring business context
- **raw_task_data**: Raw task information from Azure DevOps

### Optional Parameters
- **context_depth**: "minimal" | "standard" | "comprehensive" (default: "standard")
- **focus_areas**: Array of specific business areas to focus on

## Execution Steps

### Phase 1: Business Gap Analysis

```yaml
step: identify_business_gaps
description: Analyze Azure tasks for missing business context
actions:
  - analyze_task_descriptions: Review task content for business logic gaps
  - identify_user_flow_gaps: Find missing user experience details
  - detect_validation_gaps: Identify missing data validation rules
  - find_business_rule_gaps: Locate unspecified business logic requirements
gap_categories:
  - business_logic_missing:
    - calculation_rules: "How should calculations be performed?"
    - workflow_rules: "What business workflow rules apply?"
    - approval_processes: "Are there approval or workflow steps?"
    - state_transitions: "How do statuses and states change?"
  
  - user_experience_missing:
    - interaction_flow: "What's the expected user interaction flow?"
    - error_scenarios: "How should errors be presented to users?"
    - success_feedback: "What feedback should users receive on success?"
    - navigation_behavior: "How should navigation and routing work?"
  
  - validation_requirements_missing:
    - data_constraints: "What data validation rules apply?"
    - format_requirements: "What format requirements exist for inputs?"
    - business_constraints: "What business-specific validation is needed?"
    - cross_field_validation: "Are there dependencies between form fields?"
```

### Phase 2: Targeted Business Questions

```yaml
step: generate_business_questions
description: Create specific questions focused only on missing business context
question_generation:
  - task_specific: Generate questions specific to each task's business requirements
  - execution_focused: Only ask what's needed for successful implementation
  - no_technical_overlap: Avoid questions about technical implementation details
  - concise_format: Keep questions brief and actionable

question_categories:
  - business_rules:
    - when_to_ask: "When task mentions calculations, workflows, or business logic"
    - example: "What validation rules should apply to profile data?"
    
  - user_experience:
    - when_to_ask: "When task involves user interaction or interface changes"
    - example: "Should the editing be inline or on a separate page?"
    
  - data_handling:
    - when_to_ask: "When task involves data input, validation, or processing"
    - example: "What file formats and size limits for profile pictures?"
    
  - error_scenarios:
    - when_to_ask: "When task doesn't specify error handling approach"
    - example: "How should validation errors be displayed to users?"
```

### Phase 3: Engineer Consultation

```yaml
step: conduct_engineer_consultation
description: Gather business context from engineer through targeted questions
consultation_process:
  - present_task_context: Show engineer the specific tasks and identified gaps
  - ask_targeted_questions: Present only essential business context questions
  - record_responses: Capture engineer's business context input
  - validate_completeness: Ensure all critical business gaps are addressed

consultation_format:
  - context_presentation: "Show task details and auto-determined technical context"
  - focused_questions: "Ask only 2-4 business context questions per task"
  - actionable_responses: "Request specific, implementation-ready answers"
  - confirmation_step: "Confirm understanding of provided context"
```

### Phase 4: Context Synthesis

```yaml
step: synthesize_business_context
description: Combine engineer input with task data for complete context
synthesis_activities:
  - merge_contexts: Combine Azure task data with engineer business input
  - validate_consistency: Ensure business context aligns with task objectives
  - identify_implications: Determine implementation implications of business rules
  - prepare_handoff: Format context for task enhancement process

output_preparation:
  - business_requirements: Clear business logic and rules documentation
  - user_experience_definition: Detailed user flow and interaction requirements
  - validation_specifications: Complete data validation and constraint rules
  - error_handling_approach: Defined error scenarios and user feedback approach
```

## Output Format

### Business Context Report

```yaml
business_context:
  task_id: "AZ-123"
  task_title: "Implement user profile API endpoints"
  
  business_requirements:
    - validation_rules:
      - email_format: "Must be valid email format with domain validation"
      - phone_validation: "Support international format with country code"
      - required_fields: ["firstName", "lastName", "email"]
      - optional_fields: ["phone", "bio", "profilePicture"]
    
    - business_logic:
      - profile_updates: "Users can only update their own profile"
      - audit_requirements: "Log all profile changes with timestamp and user"
      - data_retention: "Maintain profile history for 90 days"
    
    - workflow_rules:
      - approval_process: "No approval required for profile updates"
      - notification_triggers: "Send email confirmation on email address change"
  
  user_experience:
    - interaction_flow: "Inline editing with auto-save after 2 seconds of inactivity"
    - success_feedback: "Show green checkmark next to saved fields"
    - error_presentation: "Display validation errors inline below each field"
    - loading_states: "Show spinner during save operations"
  
  data_constraints:
    - file_upload:
      - max_size: "5MB maximum file size"
      - allowed_formats: ["JPG", "PNG", "WEBP"]
      - image_processing: "Auto-resize to 300x300px, maintain aspect ratio"
    
    - text_limits:
      - bio_length: "Maximum 500 characters"
      - name_length: "Maximum 50 characters each"
  
  error_scenarios:
    - validation_errors: "Show field-specific errors with red border and text"
    - network_errors: "Show retry button with friendly error message"
    - file_upload_errors: "Display specific error based on failure type"
```

### Engineer Questions Asked

```yaml
engineer_questions_asked:
  - question: "What validation rules should apply to profile data beyond basic required fields?"
    response: "Email format validation, international phone format, bio max 500 chars"
    
  - question: "Should profile editing be inline or on a separate edit page?"
    response: "Inline editing with auto-save functionality after 2 seconds of inactivity"
    
  - question: "What file formats and size limits for profile picture uploads?"
    response: "JPG/PNG/WEBP only, 5MB max, auto-resize to 300x300px"
    
  - question: "How should validation errors be displayed to users?"
    response: "Inline below each field with red border, friendly error messages"
```

### Context Completion Status

```yaml
context_status:
  business_gaps_identified: 4
  questions_asked: 4
  responses_received: 4
  context_completeness: "100%"
  ready_for_enhancement: true
  
  remaining_gaps: []
  technical_context_source: "auto-determined from codebase analysis"
  business_context_source: "engineer consultation"
```

## Integration Points

### Task Enhancement Integration
- **Handoff to**: `hubtel-task-enhancer.md` with complete business context
- **Context Package**: Business requirements, user experience, validation rules
- **Technical Context**: Auto-determined separately from codebase analysis

### Engineer Workflow Integration
- **Triggered by**: `batch-azure-processor.md` during enhancement preparation
- **Engineer Command**: `*provide-business-context [task-ids]`
- **Completion Signal**: Ready for task enhancement with complete context

## Quality Standards

### Question Quality
- **Specific**: Questions target specific business requirements for each task
- **Actionable**: Answers directly inform implementation decisions
- **Non-redundant**: No questions about technical details auto-determined from codebase
- **Minimal**: Only 2-4 questions per task focusing on critical gaps

### Context Quality
- **Complete**: All business logic and user experience requirements defined
- **Consistent**: Business context aligns with task objectives and constraints
- **Implementable**: Context provides sufficient detail for successful development
- **Validated**: Engineer has confirmed accuracy and completeness of context

This workflow ensures precise task execution by gathering only the business context missing from Azure tasks, while technical implementation details are automatically determined from codebase analysis.