Batch Edit Reference
4 requirements
·
17 scenarios
Reference Documents Field
JR-batch-edit-reference-002
The batch_edit tool SHALL accept an optional
references field in each edit instruction that specifies a list of attachment IDs for documents the subagent can consult.
5 test scenarios
- Edit with single reference specified JR-batch-edit-reference-002.1
- Edit with multiple references specified JR-batch-edit-reference-002.2
- Edit without references specified JR-batch-edit-reference-002.3
- Subagent uses grep on reference JR-batch-edit-reference-002.4
- Subagent uses read_file on reference JR-batch-edit-reference-002.5
Accepted Reference File Types
JR-batch-edit-reference-003
The batch_edit tool SHALL accept any file type as a reference that the read_file tool supports.
5 test scenarios
- Word document as reference JR-batch-edit-reference-003.1
- PDF as reference JR-batch-edit-reference-003.2
- Spreadsheet as reference JR-batch-edit-reference-003.3
- Image as reference JR-batch-edit-reference-003.4
- Prompt guidance for grep limitations JR-batch-edit-reference-003.5
Reference Read-Only Enforcement
JR-batch-edit-reference-004
The subagent prompt SHALL instruct the subagent that reference documents are read-only and must not be edited.
2 test scenarios
- Read-only warning in prompt JR-batch-edit-reference-004.1
- Subagent respects read-only guidance JR-batch-edit-reference-004.2
Reference Attachment Upfront Validation
JR-batch-edit-reference-006
The batch_edit tool SHALL validate all reference attachment IDs before spawning subagents and fail fast if any are invalid or inaccessible.
5 test scenarios
- All references valid and accessible JR-batch-edit-reference-006.1
- Reference attachment does not exist JR-batch-edit-reference-006.2
- Reference attachment not accessible JR-batch-edit-reference-006.3
- Invalid reference format JR-batch-edit-reference-006.4
- Numeric reference format (legacy) JR-batch-edit-reference-006.5