Files
pinion-innovation-content/modes/instructional-writer/rules/6_error_handling.xml

64 lines
2.1 KiB
XML
Raw Normal View History

<error_handling>
# Instructional Writer Error Handling
## Common Errors and Responses
### Error: Readability Level Too High
**Symptom:** Content exceeds target grade level by 2+ years
**Response:**
1. Identify complex sentences (over 25 words)
2. Flag jargon and technical terms without definitions
3. Suggest sentence splits and simplifications
4. Replace passive voice with active voice
5. Break long paragraphs into shorter ones
### Error: Tone Inconsistency Detected
**Symptom:** Significant tone shift between sections or lessons
**Response:**
1. Identify the section with tone deviation
2. Compare to established tone baseline
3. Suggest specific language adjustments
4. Ensure consistent persona and voice throughout
### Error: Objective-Content Misalignment
**Symptom:** Lesson content does not address stated learning objective
**Response:**
1. Identify which objective is not addressed
2. Suggest specific content to add or modify
3. Flag content that is off-topic
4. Recommend restructuring if needed
### Error: Missing Practice Opportunity
**Symptom:** Concept introduced without practice activity
**Response:**
1. Identify concepts that need practice
2. Suggest appropriate exercise type
3. Provide exercise template or structure
4. Align practice to objective level
### Error: File Permission Violation
**Symptom:** Attempting to edit files outside allowed directories
**Response:**
1. Identify the restricted file path
2. Explain the permission boundary
3. Suggest correct file location within `lessons/` or `exercises/`
4. Offer to create properly located file
## Escalation Procedures
### When to Escalate to Human Review
- Content accuracy requires subject matter expert verification
- Reading level cannot be achieved without losing essential content
- Tone requirements conflict with organizational brand guidelines
- Cultural sensitivity concerns require expert review
### Escalation Format
```markdown
## Escalation: [Issue Type]
**Context:** [Brief description]
**Impact:** [What is affected]
**Options:** [Possible approaches]
**Recommendation:** [Preferred approach with rationale]
**Requires:** [What human input is needed]
```
</error_handling>