You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> **Status:** private-first working draft. The structure is stable enough to share internally now and is being shaped for a later public open-source release.
20
20
21
+
> [!IMPORTANT]
22
+
> One primary owner per task. Other layers may assist, but they do not compete for ownership.
23
+
21
24
---
22
25
23
26
## Start here
24
27
25
-
If you are reading this repo for the first time, use this order:
28
+
Choose the path that matches what you need:
26
29
27
-
1. Read [Workflow stack](#workflow-stack)for the mental model
28
-
2. Read [Operating model](#operating-model) to understand ownership and overlays
29
-
3. Read [`docs/en/setup.md`](./docs/en/setup.md) if you want to reproduce the setup
30
-
4. Read [`examples/prompts.en.md`](./examples/prompts.en.md) for practical usage patterns
30
+
-**Understand the model** → [Workflow stack](#workflow-stack)and [Operating model](#operating-model)
31
+
-**Reproduce the setup** → [`docs/en/setup.md`](./docs/en/setup.md)
32
+
-**Learn the terminology** → [`docs/en/glossary.md`](./docs/en/glossary.md)
33
+
-**Adapt the prompts** → [`examples/prompts.en.md`](./examples/prompts.en.md)
31
34
32
35
## Why this repo
33
36
@@ -38,6 +41,12 @@ Most AI coding setups fail in one of two ways:
38
41
39
42
This repository documents a workflow stack designed to avoid both failure modes.
40
43
44
+
It is for people who already use AI coding tools and want:
45
+
46
+
- a clear lifecycle owner for tracked work
47
+
- stronger execution discipline without duplicate process
48
+
- runtime validation when local confidence is not enough
49
+
41
50
It captures a converged OpenCode setup where:
42
51
43
52
-**OpenSpec** owns tracked lifecycle work through `opsx-*`
@@ -68,6 +77,9 @@ It captures a converged OpenCode setup where:
68
77
69
78
## Quick start
70
79
80
+
> [!TIP]
81
+
> Most teams should start with two layers, not five: OmO for orchestration, plus OpenSpec for tracked lifecycle work.
82
+
71
83
### 1. Understand the model
72
84
73
85
Read these first:
@@ -92,6 +104,8 @@ The core rule of this stack is simple:
92
104
93
105
## Operating model
94
106
107
+
At runtime, the workflow stays simple: pick one owner first, then add overlays only when they contribute a different kind of value.
108
+
95
109
```text
96
110
user request
97
111
│
@@ -145,47 +159,31 @@ The core rule of this stack is simple:
145
159
3. Pull in the relevant Gentleman skill for framework-specific quality
146
160
4. Use Sentry MCP when runtime evidence matters
147
161
148
-
## Repository map
149
-
150
-
```text
151
-
.
152
-
├── README.md
153
-
├── README.zh-CN.md
154
-
├── config/
155
-
│ ├── opencode.template.json
156
-
│ ├── ROUTING_POLICY.template.md
157
-
│ └── ENV_SELF_CHECK_POLICY.template.md
158
-
├── docs/
159
-
│ ├── en/
160
-
│ └── zh-CN/
161
-
└── examples/
162
-
├── prompts.en.md
163
-
└── prompts.zh-CN.md
164
-
```
165
-
166
162
## Adoption paths
167
163
168
164
You do not need to adopt everything at once.
169
165
166
+
Most teams should begin with a small, legible stack and only add layers when the pain is real.
167
+
170
168
### Minimal
171
169
172
-
- OmO baseline only
170
+
- OmO baseline only — good for solo experimentation and lightweight local work
173
171
174
172
### Structured
175
173
176
-
- OmO + OpenSpec lifecycle via `opsx-*`
174
+
- OmO + OpenSpec lifecycle via `opsx-*` — good for repeatable, tracked execution
177
175
178
176
### Disciplined
179
177
180
-
- OmO + OpenSpec + Superpowers
178
+
- OmO + OpenSpec + Superpowers — good when quality drift starts becoming expensive
181
179
182
180
### Specialist-ready
183
181
184
-
- OmO + OpenSpec + Superpowers + selected Gentleman skills
182
+
- OmO + OpenSpec + Superpowers + selected Gentleman skills — good for framework-heavy repositories
185
183
186
184
### Runtime-aware
187
185
188
-
- add Sentry MCP when local confidence is not enough
186
+
- add Sentry MCP when local confidence is not enough and production evidence should shape decisions
189
187
190
188
## FAQ
191
189
@@ -210,15 +208,56 @@ It detects drift in commands, skills, disabled assets, MCP auth, and duplicate l
210
208
211
209
</details>
212
210
211
+
<details>
212
+
<summary><strong>Who is this repo for?</strong></summary>
213
+
214
+
It is for people who already use AI coding tools and want a cleaner ownership model, better execution discipline, and a workflow stack that stays composable instead of collapsing into duplicate process.
215
+
216
+
</details>
217
+
213
218
## Documentation
214
219
215
-
- English architecture: [`docs/en/architecture.md`](./docs/en/architecture.md)
216
-
- English setup: [`docs/en/setup.md`](./docs/en/setup.md)
217
-
- English context log: [`docs/en/context-2026-03-22.md`](./docs/en/context-2026-03-22.md)
218
-
- Chinese architecture: [`docs/zh-CN/architecture.md`](./docs/zh-CN/architecture.md)
219
-
- Chinese setup: [`docs/zh-CN/setup.md`](./docs/zh-CN/setup.md)
220
-
- Chinese context log: [`docs/zh-CN/context-2026-03-22.md`](./docs/zh-CN/context-2026-03-22.md)
Private-first today, public-friendly by design. See [CONTRIBUTING.md](./CONTRIBUTING.md) for contribution expectations and [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md) for collaboration norms.
221
260
222
261
## License
223
262
224
-
License selection is intentionally left open until the repository is ready to be published publicly.
263
+
License is intentionally undecided while the repository remains in private-first draft mode.
0 commit comments