Operations
The final AI-DLC phase turns a built feature into something shippable and owned.
/specforge:operate writes an operations plan for the active feature — and it plans operations, it
does not execute deploys (running a real deployment stays an explicit human action).
| Step | Command | Output |
|---|---|---|
| Operate | /specforge:operate |
specs/NNN/operations.md — deploy · runbook · observability · rollback · handoff |
What it produces
Section titled “What it produces”- Deployment — ordered steps, migrations, flags/config/secrets, post-deploy verification.
- Runbook — symptoms → cause → action for likely failures; common ops commands; escalation.
- Observability — metrics to watch, alert thresholds, where logs/traces live.
- Rollback — how to revert safely, data/back-compat considerations, roll-back-vs-forward criteria.
- Handoff & Ownership — owner/on-call, dependencies, known limitations and follow-ups.
The committed operations plan travels with the PR, so on-call gets a runbook instead of tribal
knowledge. New operational scope (a monitoring feature, an infra change) is a new
/specforge:specify cycle, not something smuggled into the operations plan.