|
| 1 | +# E13 Ops Automation Readiness Slice - 2026-03-13 |
| 2 | + |
| 3 | +Status: `doing` |
| 4 | +Branch: `feat/ops-automation-slice-1` |
| 5 | +Worktree: `/Users/cauhirsch/Codes/Projects/my_opencode-wt-ops-automation-slice-1` |
| 6 | + |
| 7 | +## Why this slice first |
| 8 | + |
| 9 | +E13 still lists operations automation expansion as a P0 gap. The current runtime already has canonical commands for the main operator lanes: |
| 10 | + |
| 11 | +- issue delivery: `/delivery` |
| 12 | +- release PR prep: `/ship` |
| 13 | +- release packaging/publish: `/release-train` |
| 14 | +- incident response: `/hotfix` |
| 15 | + |
| 16 | +The immediate gap is not missing commands. It is missing cross-surface readiness visibility before operators depend on those commands more heavily. |
| 17 | + |
| 18 | +## Open requirements extracted from current docs |
| 19 | + |
| 20 | +- improve issue, PR, release, and hotfix automation without creating a second overlapping command family |
| 21 | +- keep canonical commands as the source of truth |
| 22 | +- land docs, diagnostics, and validation in the same slice when workflow behavior changes |
| 23 | +- make the first slice small enough to ship quickly, then deepen toward higher-touch automation later |
| 24 | + |
| 25 | +Primary source references: |
| 26 | + |
| 27 | +- `docs/plan/e13-shared-memory-swarm-plugin-ops-plan.md` |
| 28 | +- `docs/plan/current-roadmap-tracker.md` |
| 29 | +- `docs/plan/release-milestone-automation-runbook.md` |
| 30 | + |
| 31 | +## First-slice scope |
| 32 | + |
| 33 | +1. add `/ship doctor` so PR/release readiness can be audited directly from the canonical ship surface |
| 34 | +2. wire `/ship doctor` into umbrella `/doctor` |
| 35 | +3. refresh operator docs so the canonical issue/PR/release/hotfix path is easier to discover |
| 36 | +4. add selftest coverage for the new readiness path |
| 37 | + |
| 38 | +## Explicit non-goals |
| 39 | + |
| 40 | +- no new top-level ops command |
| 41 | +- no issue creation wrapper yet |
| 42 | +- no automatic PR/release execution beyond current guarded flows |
| 43 | +- no hotfix workflow redesign in this slice |
| 44 | + |
| 45 | +## Next slice candidates after this lands |
| 46 | + |
| 47 | +1. add higher-touch delivery-to-ship handoff summaries from canonical runtime state |
| 48 | +2. add release PR scaffolding that consumes delivery/workflow evidence directly |
| 49 | +3. add deterministic hotfix-to-followup issue linkage audits in umbrella doctor output |
| 50 | + |
| 51 | +## Follow-up landed in same worktree |
| 52 | + |
| 53 | +- `/ship doctor` now surfaces the latest canonical `/delivery` run summary when runtime state exists |
| 54 | +- `/ship create-pr --issue <id>` can inject the matched delivery handoff summary into the generated PR template without adding a new command family |
| 55 | +- `/hotfix doctor` now audits the latest closure for follow-up linkage completeness so umbrella `/doctor` can surface incident follow-up drift through canonical command wiring |
| 56 | +- `/delivery doctor` now surfaces the latest run summary and warns when the issue flow is stalled in `handoff-pending` or failed workflow states |
| 57 | +- `/ship create-pr` now injects `/release-train draft --include-milestones` context into the PR template so release PRs start from the latest canonical release narrative |
| 58 | +- umbrella `/doctor` now exposes an aggregated ops readiness summary across `/delivery`, `/ship`, `/release-train`, and `/hotfix` |
0 commit comments