Check Prerequisites:
- Verify docs/work/{name}/analysis.md exists
- If not, ERROR: "Run /workflow-analyze first"
Load Analysis Document:
- Extract selected approach from analysis.md
- Identify key technical assumptions and risks
Determine Validation Method:
- Choose appropriate validation approach based on context:
  - Prototype implementation
  - UI/UX verification (Playwright MCP)
  - TDD approach
  - Library/API exploration
  - Technical documentation research
  - User verification delegation
Execute Validation:
- Perform selected validation method
- Create prototype code in __prototype__/{feature-name}/ if needed
- Collect results and evidence
Assess Results:
- Determine status: ✅ Success / ⚠️ Partial Success / ❌ Failure
- Document findings and constraints
Write Document:
- Create docs/work/{name}/validation.md (Korean)
- Include clear next steps recommendation

Key Rules

CRITICAL: All documents must be written in Korean.

Choose based on uncertainty type:

Location: __prototype__/{feature-name}/

How to create:

Purpose:

Lifecycle:

📊 Validation Status Guidelines

This validation follows Agile Spike methodology:

Now start the validation task according to the guidelines above.