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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
# Contributing
4
4
5
-
Boatstack is a generated content distribution. Propose changes to workflow semantics, templates, evidence rules, or generated presentation in [Intelligence Flow](https://github.com/operatorstack/intelligence-flow/tree/004b6c1288661bbbfdcfe96c068f35e48f4c8bb3/labs/12-product-engineering-loop).
5
+
Boatstack is a generated content distribution. Propose changes to workflow semantics, templates, evidence rules, or generated presentation in [Intelligence Flow](https://github.com/operatorstack/intelligence-flow/tree/7faf0ffbc012b9830eb7c23c8b845ebba4be6da1/labs/12-product-engineering-loop).
6
6
7
7
The Boatstack repository receives product/runtime changes through a generated pull request. Review the PR's `UPSTREAM.json`, tests, adapter diff, and context-size change; do not hand-edit generated output on `main`. `.github/workflows` is the exception: it is Boatstack's executable control plane, excluded from scheduled projection and changed only through a separate manually reviewed Boatstack PR.
Copy file name to clipboardExpand all lines: README.md
+15-14Lines changed: 15 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@
10
10
11
11
## A delivery harness for AI coding agents
12
12
13
-
<!-- boatstack-claim:portable-product-flow -->Boatstack connects the work from an idea to a reviewed PR. Keep using Cursor, Codex, or Claude Code, with the models and specialist skills that fit the work. Boatstack keeps the plan, decisions, gaps, tests, review findings, and project context connected along the way.
13
+
<!-- boatstack-claim:portable-product-flow -->Boatstack connects the work from an idea to a reviewed PR. Keep using Cursor, Codex, Claude Code, or Gemini CLI, with the models and specialist skills that fit the work. Boatstack keeps the plan, decisions, gaps, tests, review findings, and project context connected along the way.
14
14
15
15
The agent remains free to build. Before it says the work is done, Boatstack asks for the approval, tests, review, and recorded evidence appropriate to the change.
16
16
@@ -22,17 +22,17 @@ The agent remains free to build. Before it says the work is done, Boatstack asks
22
22
23
23
| You change | Boatstack keeps |
24
24
|---|---|
25
-
| Cursor, Codex, or Claude Code | The same path from planning through PR preparation |
25
+
| Cursor, Codex, Claude Code, or Gemini CLI| The same path from planning through PR preparation |
26
26
| Lower-cost, general, or frontier model | The same approval, testing, and review requirements |
27
27
| React guidance, gstack, Spec Kit, or another skill | Human approval and evidence remain authoritative |
28
28
| Session, worktree, or feature | Durable decisions, gaps, evidence, and code state in the repository |
29
29
30
30
## Install with your coding agent
31
31
32
-
Copy this into Cursor, Codex, or Claude Code while the repository is open:
32
+
Copy this into Cursor, Codex, Claude Code, or Gemini CLI while the repository is open:
33
33
34
34
```text
35
-
Install Boatstack in this repository from https://github.com/operatorstack/boatstack. Detect whether you are running in Cursor, Codex, or Claude Code; create or use a chore/install-boatstack branch; run the official installer for this operating system; default to core unless I request gstack or Spec Kit; keep all portable host adapters; run Boatstack doctor; show me the generated files and installation diff; and prepare the installation PR without merging it or starting product work.
35
+
Install Boatstack in this repository from https://github.com/operatorstack/boatstack. Detect whether you are running in Cursor, Codex, Claude Code, or Gemini CLI; create or use a chore/install-boatstack branch; run the official installer for this operating system; default to core unless I request gstack or Spec Kit; keep all portable host adapters; run Boatstack doctor; show me the generated files and installation diff; and prepare the installation PR without merging it or starting product work.
36
36
```
37
37
38
38
Install Boatstack in its own infrastructure PR and merge it before starting a feature. Install once per Git clone; linked worktrees reuse the verified runtime and restore their ignored local helper automatically.
@@ -46,15 +46,16 @@ Install Boatstack in its own infrastructure PR and merge it before starting a fe
46
46
|---|---|
47
47
| Claude Code |`/auto-plan`|
48
48
| Cursor |`/auto-plan`|
49
+
| Gemini CLI |`/auto-plan`|
49
50
| Codex |`$boatstack auto-plan`|
50
51
51
52
That is all you need to learn up front. Boatstack shows one next action at a time through approval, building, tests, review, and PR preparation.
52
53
53
-
When you return after an interruption, run `/boatstack-next` in Claude Codeor Cursor, or `$boatstack next` in Codex. Boatstack reports the repository-verified stage and one next action without changing state. It distinguishes a feature that has not started from one that is complete.
54
+
When you return after an interruption, run `/boatstack-next` in Claude Code, Cursor, or Gemini CLI, or `$boatstack next` in Codex. Boatstack reports the repository-verified stage and one next action without changing state. It distinguishes a feature that has not started from one that is complete.
54
55
55
-
`$boatstack run` in Codex or `/boatstack-run` in Claude Codeand Cursor starts from one saved plan and continues through publication, pausing for approvals and product decisions. It checks branch freshness before delivery; it never merges or deploys.
56
+
`$boatstack run` in Codex or `/boatstack-run` in Claude Code, Cursor, and Gemini CLI starts from one saved plan and continues through publication, pausing for approvals and product decisions. It checks branch freshness before delivery; it never merges or deploys.
56
57
57
-
In Claude Codeand Cursor, that guidance moves through `/plan-gate` → `/build` → `/test-gate` → `/review-gate` → `/ship-gate`. In Codex, use the same operation names after `$boatstack`.
58
+
In Claude Code, Cursor, and Gemini CLI, that guidance moves through `/plan-gate` → `/build` → `/test-gate` → `/review-gate` → `/ship-gate`. In Codex, use the same operation names after `$boatstack`.
58
59
59
60
> The diagram shows what Boatstack guides—not a checklist you need to memorize.
60
61
@@ -66,7 +67,7 @@ In Claude Code and Cursor, that guidance moves through `/plan-gate` → `/build`
66
67
67
68
After Build, describe changes normally. Boatstack records them, preserves valid work, and resumes at the earliest boundary.
68
69
69
-
Invoke `/repair` in Claude Codeor Cursor, or `$boatstack repair` in Codex. It needs an active delivery and the exact change; earlier work routes to planning or Build.
70
+
Invoke `/repair` in Claude Code, Cursor, or Gemini CLI, or `$boatstack repair` in Codex. It needs an active delivery and the exact change; earlier work routes to planning or Build.
|**Coding agent** — Cursor, Codex, or Claude Code | Executes the work in your repository |
111
+
|**Coding agent** — Cursor, Codex, Claude Code, or Gemini CLI| Executes the work in your repository |
111
112
|**Model** — lower-cost, general, or frontier | Reasons, writes, and evaluates within the agent |
112
113
|**Skill** — React guidance, gstack, Spec Kit, or another specialty | Adds expertise for a particular kind of work |
113
114
|**Boatstack**| Carries the delivery path, saved context, and proof of completion across them |
@@ -124,7 +125,7 @@ This does not mean every model performs equally. [See the evidence and paired ev
124
125
125
126
## Why these steps?
126
127
127
-
They come from coding failures observed in benchmark and product-repository work—not guesses. Every safeguard links what happened, what Boatstack now does, and whether that behavior has actually been tested.
128
+
They derive from coding failures observed in benchmark and product work—not guesses. Each link explains what happened, what Boatstack does, and whether that behavior has actually been tested.
128
129
129
130
| What happened | What Boatstack does | Current evidence |
130
131
|---|---|---|
@@ -139,7 +140,7 @@ They come from coding failures observed in benchmark and product-repository work
139
140
140
141
## A small example
141
142
142
-
A request said, “Add a password reset button,” but the product used passwordless sign-in and had no reset route. Boatstack surfaced the conflict instead of building the button literally. The human chose dual authentication; later, review caught an unsafe recovery-session assumption and returned the change for repair before PR preparation.
143
+
A request asked to “Add a password reset button,” but the product used passwordless sign-in. Boatstack flagged the conflict. The developer chose dual authentication; later, review caught an unsafe recovery assumption and prompted a repair.
143
144
144
145
[Follow the sanitized walkthrough](docs/account-recovery-walkthrough.md) or [ship your first feature](docs/getting-started.md).
145
146
@@ -170,14 +171,14 @@ The installer previews generated paths, verifies the platform helper, offers opt
Boatstack is an open-source research prototype. Its workflow and enforcement behavior are tested, but the current record does not prove improved product-delivery success. A paired feature-building benchmark—same model, task, and budget with and without Boatstack—is the next evaluation.
182
+
Boatstack is an open-source research prototype. Its workflow and enforcement behavior are tested, but the current record does not prove improved delivery success. A paired feature benchmark—same model, task, and budget—is the next evaluation.
182
183
183
184
Exact Intelligence Flow provenance and generated file hashes are recorded in [`UPSTREAM.json`](UPSTREAM.json).
Copy file name to clipboardExpand all lines: docs/evidence-engineered-coding.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -146,6 +146,6 @@ Delivery and system improvement also remain separate. A failed task may suggest
146
146
147
147
## What is evidence-backed
148
148
149
-
The current moves were derived from the Intelligence Flow benchmark corpus and product-repository studies. The generated source commit is [`004b6c1288661bbbfdcfe96c068f35e48f4c8bb3`](https://github.com/operatorstack/intelligence-flow/tree/004b6c1288661bbbfdcfe96c068f35e48f4c8bb3/labs/12-product-engineering-loop).
149
+
The current moves were derived from the Intelligence Flow benchmark corpus and product-repository studies. The generated source commit is [`7faf0ffbc012b9830eb7c23c8b845ebba4be6da1`](https://github.com/operatorstack/intelligence-flow/tree/7faf0ffbc012b9830eb7c23c8b845ebba4be6da1/labs/12-product-engineering-loop).
150
150
151
151
The evidence supports specific failure mechanisms and guardrails. It does not establish that Boatstack is optimal, that control-theory notation proves software quality, or that one workflow dominates every team. Those are evaluation questions, so the distribution preserves measurements, provenance, gaps, and negative results.
0 commit comments