Operations

Use this skill for live-system readiness and ongoing operational handling.

Current Project Context

Production Readiness

!cat docs/06-operations/production-readiness.md 2>/dev/null || echo "No production readiness artifact found."

User Manual

!cat docs/06-operations/user-manual.md 2>/dev/null || cat docs/06-operations/runbook.md 2>/dev/null || echo "No user manual found. It should have been created during design; see the design-review skill."

Recent Incident Records

!find docs/06-operations/incidents -name "*.md" | sort 2>/dev/null || echo "No incident records found."

Interaction Pattern

1. Before first release, present the production readiness checklist.
   • Monitoring and alerting: are key signals defined?
   • User Manual: does it exist from Stage 3, and has Operations extended it with the machine-facing material — deployment, restart, rollback, on-call? Operations maintains this document; it does not author it at go-live.
   • Keep futures out of the manual. It describes present behaviour, because an operator acts on it directly. Anything designed but not yet shipped stays in the marked <!-- UNSHIPPED: R-NNN --> block that the release's closure step removes, so nobody follows a procedure the product will not perform.
   • Rollback plan: is there a tested path to restore prior state?
   • Operational ownership: is responsibility explicit?
2. Review the roadmap at the product's own operating cadence.
   • The rhythm comes from the User Manual's calendar — whatever beat the operator actually runs (monthly close, release train, weekly review).
   • Invoke the roadmap skill. This trigger answers what closure cannot: external drift — the world moving, needs changing, the goal shifting. Internal staleness is handled at release closure; drift can only be noticed.
   • It is also the one trigger that recurs when no work is happening, so a missed review is itself an attrition signal worth naming to the human.
3. For steady-state operations, guide the incident lifecycle.
   • Detect -> Triage -> Respond -> Resolve -> RCCA
4. Route RCCA findings back to the right stage.
   • Analysis for flawed assumptions or goals
   • Design for structural gaps
   • Implementation for code defects
   • Operations for process, monitoring, or configuration gaps
5. Route resulting bugs and enhancements back into the normal change pipeline.
   • Operations should not become an untracked side channel for product change.

Outputs

Produce or update these artifacts as needed:

• docs/06-operations/production-readiness.md
• docs/06-operations/user-manual.md — extend and maintain; it is created in Stage 3
• docs/06-operations/incidents/incident-*.md
• docs/ROADMAP.md — reviewed at the operating cadence via the roadmap skill; not owned here

Use the templates in this skill directory when scaffolding or substantially reshaping operational artifacts.