|
| 1 | +# Roadmap |
| 2 | + |
| 3 | +Public roadmap for `opencode-sdlc-wizard`. Items are ordered by current |
| 4 | +priority but may shuffle as real-world use surfaces friction. |
| 5 | + |
| 6 | +## v0.2.0 — shipped 2026-05-04 |
| 7 | + |
| 8 | +- ✅ Privacy-first four-tier backend picker (`scripts/{detect,configure}-backend.sh`) |
| 9 | +- ✅ Live E2E reliability fixes (session.created race + Bun.spawnSync) |
| 10 | +- ✅ Codex round-3 cross-model review CERTIFIED 9/10 |
| 11 | +- ✅ 113/113 tests across 4 suites |
| 12 | +- ✅ npm publish flow + `release.yml` automation |
| 13 | +- ✅ Companion docs: PRIVACY.md, RELEASING.md, HANDOFF.md addendum |
| 14 | + |
| 15 | +See [CHANGELOG.md](CHANGELOG.md#020---2026-05-04) for the full release |
| 16 | +notes. |
| 17 | + |
| 18 | +## v0.3.0 — `npx opencode-sdlc-wizard init` CLI |
| 19 | + |
| 20 | +Status: planned. Target after v0.2.0 sees real consumer use in OpenCode. |
| 21 | + |
| 22 | +The bash `install.sh` works but the wizard ships without an npx entry |
| 23 | +point. Parent `agentic-sdlc-wizard` exposes `npx agentic-sdlc-wizard |
| 24 | +init` via a `bin` field in package.json + a small Node CLI in |
| 25 | +`cli/bin/`. Mirroring that gives users a one-command install: |
| 26 | + |
| 27 | +```bash |
| 28 | +npx opencode-sdlc-wizard init |
| 29 | +``` |
| 30 | + |
| 31 | +Scope: |
| 32 | +- Add `bin` entry to `package.json` mapping to `cli/bin/init.js` |
| 33 | +- Tiny Node wrapper that shells out to `install.sh` |
| 34 | +- Add `--dry-run` and `--target-dir` flags through to the bash installer |
| 35 | +- Update README + `npm pack --dry-run` test to verify CLI ships |
| 36 | + |
| 37 | +## v0.3.0 candidate — `cross-model-review` skill (OSS reviewer) |
| 38 | + |
| 39 | +Status: planned. Target after v0.2.0 sees real consumer use. |
| 40 | + |
| 41 | +The cross-model review SDLC step today expects Codex (OpenAI gpt-5.5). |
| 42 | +That re-introduces the vendor lock that v0.2.0 removed for the coder. |
| 43 | +Closing the loop: a `cross-model-review` skill that runs the review |
| 44 | +through OpenCode itself with an OSS-tier model: |
| 45 | + |
| 46 | +- **Reviewer recommendations:** DeepSeek-V3 via Together (deep reasoning, |
| 47 | + ~$0.27/M input — pennies per review) or Qwen2.5-Coder-32B via Groq |
| 48 | + (fastest), or local Ollama Qwen2.5-Coder-32B (true zero-egress |
| 49 | + for air-gapped contexts). |
| 50 | +- **Skill:** reads `.reviews/handoff.json` + `.reviews/response.json`, |
| 51 | + invokes `opencode run --model <chosen>` with a structured review |
| 52 | + prompt, writes `.reviews/latest-review.md`. Symmetric to the codex |
| 53 | + flow. |
| 54 | +- **Wrapper:** `scripts/cross-model-review.sh` for non-skill / CI use. |
| 55 | +- **PRIVACY.md addition:** the all-OSS pipeline recipe (Ollama coder + |
| 56 | + Ollama reviewer = zero network egress for the entire SDLC loop). |
| 57 | + |
| 58 | +## v0.4.0 candidate — domain-adaptive expansion |
| 59 | + |
| 60 | +Status: speculative. Triggered by real demand. |
| 61 | + |
| 62 | +The wizard currently treats `setup-wizard` as web-API-default. Domain |
| 63 | +detection in the parent (firmware / data-science / CLI / web) |
| 64 | +applies here too. If `npm i opencode-sdlc-wizard` users start landing |
| 65 | +on firmware or data-science repos, surface domain-specific TESTING.md |
| 66 | +templates the way the parent does. |
| 67 | + |
| 68 | +## Phase B — backend matrix proof |
| 69 | + |
| 70 | +Status: deferred from v0.1.0. Triggered by maintainer authorization. |
| 71 | + |
| 72 | +Run paired E2E SDLC scenarios (plan → TDD → self-review) against: |
| 73 | + |
| 74 | +| Tier | Backend | Floor model | |
| 75 | +|------|---------|--------------| |
| 76 | +| Local | Ollama / Qwen2.5-Coder-32B (16-24GB VRAM class) | Floor | |
| 77 | +| Enterprise | Azure OpenAI tenant | Floor | |
| 78 | +| Hosted OSS | Together / Groq / OpenRouter (Qwen-Coder, DeepSeek-V3) | Floor | |
| 79 | +| Anthropic baseline | Opus 4.7 max | Ceiling | |
| 80 | + |
| 81 | +Score each against parent's tier-2 evaluation rubric (10-point criteria, |
| 82 | +5 trials, 95% CI). Document which backends hold SDLC compliance and |
| 83 | +which degrade. Capability-floor note still applies: small models |
| 84 | +(7-13B) will fail and that's a result, not a bug. |
| 85 | + |
| 86 | +## Phase C — hardware scout for local tier |
| 87 | + |
| 88 | +Status: deferred. Triggered if Phase B needs hardware. |
| 89 | + |
| 90 | +Test gaming laptop + Windows laptop first (zero spend). If 16-24GB |
| 91 | +VRAM bar isn't met, evaluate $200/$300/$400 rig OR cloud-GPU rental. |
| 92 | + |
| 93 | +## Cross-cutting — XDLC ditto migrator |
| 94 | + |
| 95 | +Status: roadmapped, not in this repo's scope. |
| 96 | + |
| 97 | +A separate cross-host migrator (`ditto`) is roadmapped at |
| 98 | +[`xdlc/docs/ditto-roadmap.md`](https://github.com/BaseInfinity/xdlc/blob/main/docs/ditto-roadmap.md) |
| 99 | +to automate future ports between siblings. v0.1.0 trigger: when |
| 100 | +sibling #5 starts (or upstream `claude-sdlc-wizard` ships a release |
| 101 | +that needs syncing across the three existing siblings). |
| 102 | + |
| 103 | +The first transform set ditto v0.1.0 will codify is the |
| 104 | +`claude-sdlc-wizard → opencode-sdlc-wizard` port we hand-applied for |
| 105 | +v0.2.0 — captured in `HANDOFF.md` v0.2.0 addendum + the F1-F6 + E2E |
| 106 | +findings tables in `.reviews/response.json`. Those are effectively the |
| 107 | +unstructured form of `xdlc/docs/ports/claude-to-opencode.md`. |
| 108 | + |
| 109 | +When `ditto v0.1.0` ships, its first regression test will harvest |
| 110 | +those tables, scan + diff the two repos, and assert the auto-generated |
| 111 | +transform table matches what we wrote down by hand. |
| 112 | + |
| 113 | +## How to consume this roadmap |
| 114 | + |
| 115 | +- Open issues in [the repo](https://github.com/BaseInfinity/opencode-sdlc-wizard/issues) |
| 116 | + to bid up an item or propose a new one. |
| 117 | +- Items are not promises. Real-world use of v0.2.0 may surface |
| 118 | + higher-priority work that bumps these. |
| 119 | +- `feedback` skill (privacy-first) is the canonical way to surface |
| 120 | + bugs / requests without scanning the repo. |
0 commit comments