orchestrix/orchestrix-core/tasks/frontend-user-confirmation.md

Orchestrix - Universal AI Agent Framework for Coordinated AI-Driven Development

# Frontend User Confirmation Task

## Purpose

To facilitate user review and confirmation of frontend implementation before proceeding to backend development. This task ensures the frontend meets user expectations and requirements before investing effort in backend implementation.

## When to Use

- **Automatic Trigger**: When `frontendFirstStrategy: true` in core-config.yaml
- **Story Status**: When story reaches "FrontendReview" status
- **Manual Trigger**: When dev agent completes Phase 1 frontend tasks

## Task Execution

### 1. Present Frontend Implementation

**Dev Agent Responsibilities:**
- Deploy frontend to local development server
- Provide clear instructions for accessing the application
- Document any limitations or mock data being used
- Capture screenshots or screen recordings if requested

**Presentation Checklist:**
- [ ] Frontend is running and accessible
- [ ] All implemented features are demonstrated
- [ ] User flows can be tested end-to-end (with mock data)
- [ ] Responsive design verified on different screen sizes
- [ ] Key interactions and animations working

### 2. User Review Process

**User Should Evaluate:**
- **Visual Design**: Does it match the UI/UX specification?
- **User Experience**: Are the workflows intuitive and efficient?
- **Functionality**: Do all features work as expected?
- **Responsiveness**: Does it work well on different devices?
- **Performance**: Is the interface responsive and smooth?

**Review Questions:**
1. Does the frontend implementation meet your expectations?
2. Are there any visual or interaction changes needed?
3. Do the user flows feel natural and efficient?
4. Are there any missing features or UI elements?
5. Is the overall user experience satisfactory?

### 3. Possible Outcomes

#### Option A: Approval ✅
- **User confirms**: "Frontend looks good, proceed to backend"
- **Next action**: Update story status to "BackendInProgress"
- **Dev Agent**: Begin Phase 2 backend implementation

#### Option B: Minor Changes Needed 🔄
- **User feedback**: Specific changes required (colors, layout, copy, etc.)
- **Next action**: Dev agent makes requested changes
- **Loop**: Return to step 1 for re-review

#### Option C: Major Revisions Required ❌
- **User feedback**: Significant changes needed
- **Next action**: Return story to "InProgress" status
- **Review**: May require SM agent to revise story or consult UX Expert

### 4. Documentation Requirements

**Record in Story File:**
- User feedback and decisions made
- Any changes requested and implemented
- Final approval timestamp
- Screenshots or recordings if helpful

**Update Status:**
- From "FrontendReview" → "BackendInProgress" (if approved)
- From "FrontendReview" → "InProgress" (if major changes needed)

## Benefits of This Process

1. **Early Validation**: Catch UX issues before backend investment
2. **Better APIs**: Frontend reveals actual data requirements
3. **User Satisfaction**: Ensures final product meets expectations
4. **Reduced Rework**: Prevents costly backend changes later
5. **Iterative Improvement**: Allows refinement of user experience

## Integration with Development Workflow

This task seamlessly integrates with the frontend-first strategy:

```
SM creates story → Dev implements frontend → USER CONFIRMATION → Dev implements backend → Integration testing
```

The confirmation checkpoint acts as a quality gate, ensuring frontend excellence before backend development begins.