Menu
Run when the Conductor reports that project work is complete. Confirms with the user, tells the Conductor to close the project, waits for the close-project report, then terminates the Conductor and Reviewer and marks the project done.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when editing `~/.system2/config.toml` — adding or modifying a database connection, tuning per-agent overrides, or changing operational defaults. Does NOT cover `~/.system2/auth/.auth.toml` (managed by `system2 config`).
Run on first launch (when ~/.system2/knowledge/infrastructure.md is still the template) or whenever the user explicitly asks to re-onboard. Greets the user, learns about them, detects the system, installs and configures the data stack (database, orchestrator, Python environments), scaffolds the pipeline repository, and captures interaction preferences.
Use when building, debugging, deploying, or testing data pipelines with Prefect v3. Trigger on any code importing prefect, prefect YAML config, or user mentioning Prefect flows/tasks/deployments/workers.
Run before declaring project work complete. A self-audit checklist to honestly assess whether the deliverables actually meet the requirements before requesting final review or reporting completion to the Guide.
Run when delegating complex work to a new project. Gathers preliminary requirements with the user, creates the project in app.db, spawns a Conductor and Reviewer, introduces them to each other, updates the user, and schedules a follow-up reminder so a silent Conductor is noticed.
Build interactive HTML dashboard artifacts with live database queries via the postMessage bridge. Includes a copy-paste helper function, workflow steps, and Chart.js integration patterns.
| name | project-completion |
| description | Run when the Conductor reports that project work is complete. Confirms with the user, tells the Conductor to close the project, waits for the close-project report, then terminates the Conductor and Reviewer and marks the project done. |
| roles | ["guide"] |
Follow these steps end-to-end when the Conductor reports that its work is complete. Never terminate agents or finalize a project without explicit user confirmation.
Show the Reviewer's final report to the user. The Conductor's completion message includes the Reviewer's assessment (outcome, report path, key findings). Display the full report via show_artifact with the path to ~/.system2/projects/{dir_name}/artifacts/final_review.md. Walk the user through the key points.
Relay to user and request confirmation:
"The Conductor reports that project #N is complete. [Brief summary from Conductor's message]. The Reviewer's final assessment: [outcome and key findings]. Would you like to address any of the Reviewer's findings, or shall I finalize this project?"
Wait for explicit user decision. Do NOT proceed without user approval. If the user wants changes or wants to address Reviewer findings, relay them to the Conductor. The Conductor may make adjustments and request a re-review from the Reviewer. Repeat this step until the user is satisfied and confirms closure.
After user confirms closure, message the Conductor: "User has confirmed project #N is complete. Please close the project."
Handle the Conductor's re-confirmation request. The Conductor will ask you to confirm closure a second time. Confirm explicitly: "Yes, the user is approving project closure for project #N."
Wait for the Conductor's close-project report. The Conductor will resolve any remaining tasks, trigger the project story for the Narrator, and report back when everything is done.
After the Conductor confirms the project is closed:
terminate_agent (using their agent IDs)"done" in app.db (set end_at to now)show_artifact with the absolute path ~/.system2/projects/{dir_name}/artifacts/project_story.md, then inform the user with a final summary.