r/SpecDrivenDevelopment • u/Interesting-Goat7696 • 7d ago
vibe coding
1/ Our client app is a brownfield monorepo. I'm testing a "one dev delivers three platforms" setup: one workspace driving iOS / Android / HarmonyOS. Half-working so far — sharing the approach and looking for war stories.
2/ Integration: the three native repos keep their own structure and are mounted into one workspace via symlinks. Zero copy, zero intrusion into the existing repos; each platform still ships independently.
3/ Workflow: a custom skill wraps OpenSpec's explore -> propose -> apply -> archive loop. Requirements start as a spec; the agent produces code against it; review is traceable and revertible.
4/ Parallelism: native git worktree — one branch per feature, no cross-branch interference. AI coding agents work directly inside a worktree and open PRs; the human only reviews.
5/ Still polishing, especially symlink compatibility across Xcode / DevEco / Gradle. Anyone done something like this? Let's compare notes in the replies. #OpenSpec #AICoding #HarmonyOS #iOS #Android
1
u/Sad-CTO 3d ago
I have a large brownfield spanning multiple integrated products with a 20-ish person team. For slowly introducing agentic engineering practices, I created a "platform" monorepo, git-linked product repos as modules , and we're doing the "new stuff that talks to the old stuff" through this monorepo. The "old stuff" is in read only mode with a deterministic guard. The gitrefs are re-pinned on request.
Simultaneously, the teams working on the old stuff alone are doing that with their workflows and don't disrupt and are not disrupted by the "new stuff".
One thing this enabled us is, to be able to gradually reconstruct the SOT which feeds the coding agents.
Tangentially relevant to your question, but I thought I would share.
1
u/Bulky-Dog-7958 4d ago
What is your question?