Track and complete all required deliverables before finishing a task
Ensure ALL required outputs are completed before concluding a task, preventing premature task termination when multiple deliverables are required. This skill includes mandatory enforcement steps that MUST be followed.
CRITICAL: You MUST complete this step before producing ANY deliverable or taking any other action.
At task start, explicitly enumerate EVERY required output:
MANDATORY OUTPUT FORMAT: Before any other work, output this exact format:
DELIVERABLES_IDENTIFIED:
1. [filename/description] - [brief description]
2. [filename/description] - [brief description]
...
TOTAL_DELIVERABLES: N
Example identification:
Required Deliverables:
1. [ ] Email to Juvoxa CEO
2. [ ] Follow-up analysis report
Total: 2 deliverables
CRITICAL: This tracker MUST be created and visible throughout task execution.
Maintain a visible checklist throughout task execution:
DELIVERABLE TRACKER
===================
[ ] Deliverable 1: [brief description]
[ ] Deliverable 2: [brief description]
[ ] Deliverable 3: [brief description]
Completed: 0/3
Update this tracker AFTER each deliverable is fully completed (not just started).
Before considering any deliverable complete, verify it exists:
list_dir or run_shell (ls/cat) to confirm the file exists[✓] filename verified in filesystemBefore concluding the task, run this mandatory checklist: CRITICAL ENFORCEMENT: You are BLOCKED from outputting <COMPLETE> until this verification passes.
FINAL VERIFICATION (REQUIRED BEFORE <COMPLETE>)
==================
1. Review original task requirements
2. Count total deliverables identified: ___
3. Count deliverables marked complete: ___
4. Do counts match? YES/NO
5. If NO: Identify missing deliverables and complete them
6. If YES: Verify each deliverable exists and meets quality standards
7. Filesystem verification (REQUIRED):
- [ ] file1.ext: VERIFIED (list_dir/run_shell confirmed)
- [ ] file2.ext: VERIFIED (list_dir/run_shell confirmed)
**BLOCKING RULE:** If counts do not match OR any file cannot be verified in the filesystem, you MUST:
1. NOT output <COMPLETE>
2. Identify the missing/unverified deliverables
3. Complete and verify them
4. Re-run this verification checklist
**Only output <COMPLETE> when all deliverables are verified present in the filesystem or output stream.**
Only stop when all deliverables are verified complete.
Before marking task complete, ask:
❌ Stopping after first deliverable - Just because one output is done doesn't mean the task is complete ❌ Stopping after first deliverable - Just because one output is done doesn't mean the task is complete
❌ Outputting <COMPLETE> without filesystem verification - You must verify files exist before completion
❌ Skipping DELIVERABLES_IDENTIFIED output - This mandatory output must appear before any work begins
❌ Assuming implicit completion - Don't assume related outputs are "part of" a main deliverable unless explicitly stated
❌ Losing track mid-task - The tracker must stay visible and updated throughout
❌ Counting drafts as complete - Only mark done when the deliverable meets quality standards
# Deliverable tracking template
deliverables = {
"email_to_ceo": {"status": "pending", "file": "ceo_email.txt"},
"analysis_report": {"status": "pending", "file": "analysis.pdf"},
"summary_doc": {"status": "pending", "file": "summary.docx"},
}
def mark_complete(name):
deliverables[name]["status"] = "complete"
print(f"✓ {name} completed")
print(f"Progress: {sum(1 for d in deliverables.values() if d['status'] == 'complete')}/{len(deliverables)}")
def all_complete():
return all(d["status"] == "complete" for d in deliverables.values())
Use this pattern whenever a task involves:
The task is NOT complete until ALL deliverables are complete. One done ≠ all done.