# CR-002: Refocus Extractor on Knowledge Learning & Tool Skill Delegation

| Field | Value |
|-------|-------|
| CR ID | CR-002 |
| Feature | FEATURE-050-A through E (cross-cutting) |
| Epic | EPIC-050 |
| Classification | modification |
| Priority | High |
| Date | 03-17-2026 |
| Requestor | User (product owner) |

## Change Description

Refocus the Application Knowledge Extractor on its core responsibility:
1. Phase 1: Add extraction technique guidance (chrome devtools screenshots, source analysis strategies)
2. Enable Chrome DevTools as explicit extraction tool option
3. Phase 2/3: Call tool skill for feedback during extraction (not just validation)
4. Phase 5: Delegate quality scoring to tool skill (remove self-scoring)
5. Add score_quality operation to tool skill

## Business Justification

The extractor was doing too much domain-specific work itself (quality scoring formulas, criteria evaluation) instead of delegating to tool skills which have domain expertise. This CR restores the two-tier architecture intent: extractor orchestrates, tool skills own domain knowledge.

## Impact Analysis

- **SKILL.md:** Phases 1, 2, 3, 5 modified (additive + replacement)
- **execution-procedures.md:** Steps 1.1, 2.1, 3.1, 5.1 updated
- **Tool skill SKILL.md:** New score_quality operation added
- **No breaking changes:** All existing operations preserved

## Implementation Details

### Extractor SKILL.md Changes
1. **Step 1.1 (Analyze Input):** Added extraction technique planning (4-5 action items)
2. **Step 2.1 (Extract Source Content):** Added tool skill early feedback (items 5-6)
3. **Step 3.1 (Validate & Coverage Loop):** Emphasized tool skill delegation (item 1)
4. **Step 5.1 (Quality Scoring):** REPLACED with tool-skill-delegated procedure
5. **Execution Flow table:** Updated Phase 5.1 description
6. **Phase Definitions table:** Updated Phase 5 typical activities

### Extractor execution-procedures.md Changes
1. **Step 1.1:** Added "Plan Extraction Techniques" block (9 lines)
2. **Step 2.1:** Added "Tool Skill Early Feedback" action item 9 (4 lines)
3. **Step 3.1:** Updated action item 1 to emphasize tool skill delegation
4. **Step 5.1:** REPLACED entire section with tool-skill-delegated procedure (23 lines)

### Tool Skill SKILL.md Changes
1. **Added score_quality operation:** New operation after pack_section (28 lines)
2. **Updated Input Parameters:** Added score_quality to operation enum
3. **Updated Output Result:** Added quality_result output format (7 fields)
4. **Updated Error Handling:** Added SCORING_FAILED error
5. **Updated Templates table:** Note that acceptance-criteria.md also used for scoring

## Conflict Resolutions

### DC-3: Determinism Guarantee
**Resolution:** Hybrid approach — tool skill returns `{weights, thresholds, dimension_config}`, extractor applies deterministic math. This preserves AC-050E-08's bit-identical guarantee while allowing tool-skill-definable weights.

### DEP-4: CR-001 split_mode × Structure Scoring
**Resolution:** Structure dimension counts H3 headings across all files in `packed/` directory. Clarifying note added to score_quality operation and execution-procedures.md Step 5.1 CONTEXT.

## Testing Strategy

1. **Unit Tests:** Verify score_quality operation returns valid quality_result structure
2. **Integration Tests:** Verify extractor Phase 5 can call tool skill score_quality
3. **Regression Tests:** Verify existing operations (validate_section, pack_section) still work
4. **Fallback Tests:** Verify graceful fallback when score_quality operation not available

## Rollout Plan

1. Deploy tool skill first (adds new operation, backward compatible)
2. Deploy extractor (uses new tool skill operation)
3. Monitor quality scores in `.kb-intake/` outputs
4. Compare quality scores between old self-scoring and new delegated scoring (validation run)

## Rollback Plan

If issues arise:
1. Revert extractor to previous version (self-scoring)
2. Tool skill remains compatible (new operation unused but harmless)
3. No data migration needed — quality scores are computed per-extraction

## Related Documents

- FEATURE-050-E specification (quality scoring acceptance criteria)
- FEATURE-051-A specification (tool skill operations)
- CR-002 conflict analysis report
- DAO decision log entry (26-03-17)
