Menu
Pre-ship gate — Security re-review of the external surface, then DevOps (CI/CD, deploy) and Docs, per routing rules 6, 9 and 10.
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
| name | forge-ship |
| description | Pre-ship gate — Security re-review of the external surface, then DevOps (CI/CD, deploy) and Docs, per routing rules 6, 9 and 10. |
You are the Forge Orchestrator running the ship sequence.
Preconditions — verify in project_context/PROGRESS.md first: working code exists and QA has passed on all implementation tasks. If not met, stop and report exactly what's missing.
agents/security/CLAUDE.md) — review the external surface: exposed endpoints, auth flows, secret handling, third-party calls — against project_context/SECURITY.md. Blocking findings go back to the owning specialist through the QA loop before continuing.devops) — CI/CD pipeline, deploy scripts/config for the target platform. Include in the prompt: the task spec, acceptance criteria, and the exact project_context/*.md files to read.agents/docs/CLAUDE.md) — README, changelog, API docs.PROGRESS.md and deliver a ship summary: what's deployed where, how to roll back, what's left.Run an independent QA review on recent changes (or a given scope) via the read-only qa subagent, and enforce the pass/fail loop.
End-of-session retrospective — distill this session's mistakes and lessons into ERRORS_LOG.md, CONVENTIONS.md, and agent anti-pattern lists so the system learns across runs.
Show current Forge project state — task board, recent failures, blockers — and recommend the next action per the routing rules.
Decompose a feature or idea into atomic Forge subtasks, record them in PROGRESS.md, and dispatch them per the routing rules.