finalize-zip-deliverable

Finalize ZIP Deliverable

CRITICAL: This skill defines a MANDATORY workflow that MUST be executed before any task can be marked complete. Task completion is BLOCKED until ZIP verification passes.

Agents often assume that creating the project directory and files constitutes task completion. However, many tasks require a single downloadable artifact (ZIP file) for delivery. You are forbidden from declaring task completion until the ZIP artifact is created and verified.

ITERATION-AWARE PRIORITY: If the agent's iteration count approaches the task limit (e.g., iteration 25 of 30), ZIP creation MUST be elevated to highest priority. Do not continue adding features or refining code—execute the ZIP command immediately with whatever files exist.

Early Warning System

TRIGGER CONDITION: When iteration count reaches 25/30 (or 80% of any iteration limit), activate the following protocol:

1. Immediately halt any non-essential code generation or refinement.
2. Assess current state: List all files currently in the project directory.
3. Execute minimum viable ZIP: Package whatever exists, even if incomplete.
4. Document the fallback: Note in completion summary that ZIP was created as fallback due to iteration constraints.

RATIONALE: A partial ZIP deliverable is ALWAYS preferable to zero deliverable. Never exhaust iterations without creating the required artifact.

Minimum Viable ZIP Fallback

When triggered by the early warning system, execute this fallback procedure:

# Create ZIP with whatever files currently exist
zip -r project_fallback.zip ./project/ 2>/dev/null || zip -r project_fallback.zip ./*

# Verify creation succeeded
ls -lh project_fallback.zip

Acceptable fallback scenarios:

• ZIP contains partial codebase (better than nothing)
• ZIP contains only configuration files
• ZIP contains even a single source file

Unacceptable outcome: No ZIP file created due to iteration exhaustion.

Workflow Steps

1. Verify Project Completeness