domains / families / devops / ship-loop

ship-loop

separate

Run a chained build→ship→verify→notify pipeline for multi-segment feature work. Use when implementing multiple features in sequence, each as a coding agent task that gets committed, deployed, and verified before moving to the next. Prevents dropped handoffs between segments.

When to use

• Building multiple features for a project in sequence
• Any work that follows: code → preflight → commit → deploy → verify → next
• When you need checkpointing so progress survives session restarts
• When you want self-healing: failures auto-repair before asking humans
• When you want cost visibility and learning from past runs

When not to use

• Untrusted repos without reviewing the config

Skill page

Source