[WSJF-4] Sprint decomposition: extract first, then generate parser separately #14

New issue

Open

opened 2026-06-27 10:45:50 +02:00 by bullitt · 0 comments

bullitt commented

2026-06-27 10:45:50 +02:00

Owner

Context

Article: break complex tasks into managed chunks with contracts between stages.

Problem

Extraction and parser generation happen in one prompt. If extraction is wrong, the parser encodes the wrong patterns.

Proposal

Call 1: 'Extract these fields from this email' → returns {fields}
Validate extraction (tracking_number format, status in valid list)
Call 2: 'Given this email and these correct field values, create a field_map' → returns {field_map}
Only store parser if both calls succeed and agree

WSJF: 4 (Medium value, but larger size due to 2 API calls)

## Context Article: break complex tasks into managed chunks with contracts between stages. ## Problem Extraction and parser generation happen in one prompt. If extraction is wrong, the parser encodes the wrong patterns. ## Proposal - Call 1: 'Extract these fields from this email' → returns {fields} - Validate extraction (tracking_number format, status in valid list) - Call 2: 'Given this email and these correct field values, create a field_map' → returns {field_map} - Only store parser if both calls succeed and agree ## WSJF: 4 (Medium value, but larger size due to 2 API calls)