Feature Brainstorm Flow

Brainstorm a new feature with an assistant that knows the whole repo, pressure-test it, and turn the decision into an ADR — without your exploration ever touching real code or the wrong branch. Three commands do all the git; you type none.

Brainstorm-only namespace. Notes in docs/brainstorm/ are working drafts, not code. A decision becomes an ADR only through a reviewed PR from the real repo — never directly from a brainstorm session.

The three commands

/qiiub-feature-brainstorm

Syncs a separate brainstorm copy to the latest main, reads the current ADRs and rules, pressure-tests your idea through four lenses (feasibility · conflict · risk · devil's advocate), and saves the decision as a draft-*.md note.

Run in: the brainstorm copy — if you run it in the real repo, it sets the copy up and points you there

/qiiub-feature-status

Read-only dashboard: which ideas are still draft, which are approved, and which have already been promoted to an ADR.

Run in: either folder

/qiiub-feature-promote

Turns an approved note into an ADR and opens its PR, with a collision-checked ADR number.

Run in: the real repo only — it refuses to run in the brainstorm copy

Setup — once per developer

In your normal repo: git pull origin main — you now have the three commands.
Run /qiiub-feature-brainstorm once. It creates a sibling brainstorm copy at ../qiiub-brainstorm whose push is disabled, and tells you to open it.

That is the whole install. No manual git.

Daily use

Brainstorm — open the qiiub-brainstorm folder and run /qiiub-feature-brainstorm. It syncs to the latest main, you talk the feature through, and the decision is saved as a draft note.
Check what's pending — /qiiub-feature-status.
Make it real — back in your normal repo, /qiiub-feature-promote drafts the ADR and opens the PR. Mike (or the ADR-review deputy) reviews it before it merges.

Why it is safe

Three layers. The real wall is the last one — it lives on the server, not in trusting the assistant.

🚫

1 · The brainstorm copy cannot pushremote.origin.pushurl = DISABLED. Whatever happens in that copy cannot reach the remote or your real working tree.

🧭

2 · The commands guard the folder/qiiub-feature-brainstorm refuses to run in the real repo; /qiiub-feature-promote refuses to run in the copy. You cannot fumble the wrong folder.

🔒

3 · The source of truth changes only through a reviewed PRmain accepts changes only via PR approval plus the cascade-guards CI. Even if the assistant does something unexpected, nothing lands in main without a human "yes". This is the wall.

Admin — required to complete the wall (not done yet)

Branch protection on main is currently OFF — gh api repos/BCPOS/qiiub/branches/main returns protected: false. Until it is enabled, "nothing lands without a PR" is convention, not enforcement.

To enable it (repo admin → GHES Settings → Branches → Add branch protection rule for main):

Require a pull request before merging — 1 approval.
Require status checks to pass — cascade-guards.
Block force pushes and deletion of main.

API endpoint, if scripting: PUT repos/BCPOS/qiiub/branches/main/protection. Once this is on, the model above is fully enforced rather than relied upon.

Companion: docs/brainstorm/README.md (same content, text form) · design history: docs/design/qiiub-orchestrated-brainstorm.md.