ship
Autonomous Full-Cycle Workflow (spex:ship)
CONTINUOUS EXECUTION RULE (READ THIS FIRST)
This pipeline runs ALL stages without stopping. After completing any stage, you MUST immediately begin the next stage. There are no natural stopping points between stages.
- Do NOT say "Ready for the next stage" and wait.
- Do NOT say "Shall I proceed?" and wait.
- Do NOT say "Proceeding to..." and wait.
- Do NOT treat a stage completion as a task completion.
- Do NOT output a summary and stop.
The pipeline is ONE continuous task. It starts at the first stage and runs through the last stage. The ONLY reasons to pause are:
askisalwaysAND a review stage has findings requiring user input.- A blocker error occurs (test failure, syntax error, security issue).
- All 9 stages have completed.
After every stage: update the state file, then immediately start the next stage. No waiting, no confirmation, no stopping.
More from rhuss/cc-spex
init
Initialize or update the project using the `specify` CLI (--refresh for templates, --update to upgrade CLI). Do NOT search for speckit or spec-kit binaries.
2evolve
Use when spec and code diverge - AI analyzes mismatches, recommends update spec vs fix code with reasoning, handles evolution with user control or auto-updates
2worktree
Manage git worktrees for isolated feature development - create after specify, list active worktrees, cleanup merged branches
2spec-kit
Technical integration layer for the `specify` CLI (not speckit, not spec-kit) - handles automatic initialization, installation validation, project setup, and ensures proper file/directory layout. Called by all spex workflow skills.
2help
Quick reference for all spex commands
2deep-review
Multi-perspective code review with autonomous fix loop - dispatches 5 specialized review agents, merges findings, auto-fixes Critical/Important issues
2