Menú
Use when all workflow stages are completed and verified — generates summary report, archives results, and commits
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when creating, reading, or updating workflow checkpoint files (workflow-state.json, progress.log, init.sh) — the file-centric state system for cross-session computational workflows
Use when a workflow stage subagent has prepared computation scripts and needs to submit the job to a local or HPC backend via DPDispatcher
Use when a workflow plan exists and stages need to be executed sequentially in the current session
Use when the user wants to set up a new computational experiment — before any computation begins, to design the method, stages, and success criteria
Use before marking any workflow stage as completed — verify outputs exist, are valid, and meet success criteria defined in workflow-state.json
Use when starting a new session and workflow-state.json exists in the working directory — recovers full context from checkpoint files before any new work
| name | workflow-completion |
| description | Use when all workflow stages are completed and verified — generates summary report, archives results, and commits |
Wrap up a completed workflow with a summary report and clean archival.
Core principle: A workflow is not done until it's documented and committed.
Read workflow-state.json. Every stage must have status: "completed" (or skipped). If any stage is not completed, do NOT proceed — invoke superscientist:executing-workflows instead.
Save to docs/superscientist/reports/YYYY-MM-DD-<topic>-report.md:
# [Topic] Workflow Report
**Workflow ID:** [workflow_id]
**Completed:** [timestamp]
**Total sessions:** [count from progress.log]
**Amendments:** [count]
## Objective
[From experiment design doc]
## Results Summary
### Stage N: [Name]
- **Status:** completed
- **Key result:** [1-2 sentence summary of output]
- **Output files:** [paths]
## Issues Encountered
[Any failed stages, retries, amendments — summarized from progress.log]
## Key Outputs
[List of final deliverables with paths]
workflow-state.jsonAdd top-level field: "workflow_status": "completed" and update "updated" timestamp.
Append to progress.log via Bash tool:
echo "[$(date -Iseconds)] Workflow completed. All N stages verified. Report: docs/superscientist/reports/..." >> progress.log
git add workflow-state.json progress.log docs/superscientist/reports/
git commit -m "feat: complete workflow <workflow_id>"
Tell the user: workflow is complete, where to find the report, and list the key output files.