DOCS · GETTING STARTED

Getting started

Choose the coding agent you use below. Every supported harness loads the same Synthex workflows: a messy idea becomes a peer-reviewed implementation plan and parallel-executed, tested code. Claude Code is Synthex's home and has the richest native experience; the other harnesses use the shared Agent Skills layer.

1. Install Synthex

Claude Code

Run these commands inside Claude Code:

/plugin marketplace add bluminal/lumenai
/plugin install synthex

Claude Code provides Synthex's native plugin experience: namespaced slash commands, plugin agents, hooks, and native looping.

Codex CLI

Run these commands in a terminal, then start a new Codex session:

codex plugin marketplace add bluminal/lumenai
codex plugin add synthex@lumenai

Codex exposes the Synthex workflows and specialists as skills. Invoke one with $, such as $review-code or $architect, or select it from /skills.

Grok

Run these commands in a terminal, then start a new Grok session:

grok plugin marketplace add bluminal/lumenai
grok plugin install synthex --trust
grok plugin enable synthex

Grok exposes the Synthex workflows and specialists as skills. Invoke one as /synthex:review-code or /synthex:architect. When the name is unambiguous, /review-code works too.

Gemini CLI

Gemini CLI installs Synthex as workspace Agent Skills. From the project root:

git clone --depth 1 --filter=blob:none --sparse https://github.com/bluminal/lumenai.git .synthex-source
git -C .synthex-source sparse-checkout set plugins/synthex
mkdir -p .gemini
cp -R .synthex-source/plugins/synthex/{agents,commands,config,scripts} .gemini/
for skill in .synthex-source/plugins/synthex/skills/*; do
  gemini skills install "$skill" --scope workspace --consent
done

Use gemini skills list to confirm the inventory. If .gemini/ already contains project-managed files, merge the copied directories deliberately rather than overwriting them.

OpenCode

OpenCode discovers project-local Agent Skills under .agents/skills. From the project root:

git clone --depth 1 --filter=blob:none --sparse https://github.com/bluminal/lumenai.git .synthex-source
git -C .synthex-source sparse-checkout set plugins/synthex
mkdir -p .agents
cp -R .synthex-source/plugins/synthex/{skills,agents,commands,config,scripts} .agents/

Use opencode debug skill to confirm discovery. If .agents/ already contains project-managed files, merge the copied directories deliberately rather than overwriting them.

2. Initialize your project

From the project you want Synthex to manage, run the init workflow:

Harness	Invoke init
Claude Code	`/synthex:init`
Codex CLI	`$init` or choose `init` from `/skills`
Grok	`/synthex:init`
Gemini CLI	Ask Gemini to use the Synthex `init` skill
OpenCode	Ask OpenCode to use the Synthex `init` skill

This scaffolds the standard project layout:

.synthex/config.yaml — project configuration (review loops, concurrent task count, multi-model review opt-in)
docs/reqs/ — product requirements documents
docs/plans/ — implementation plans
docs/specs/ — technical specifications
docs/specs/decisions/ — Architecture Decision Records (ADRs)
docs/specs/rfcs/ — Requests for Comments
docs/runbooks/ — operational runbooks
docs/retros/ — retrospective documents

In Claude Code, /synthex:init also adds .claude/worktrees/ to your .gitignore and asks you to pick a concurrent_tasks value: Yolo (every CPU core), Aggressive (75% of cores), or the conservative default of 3. This initialization is optional; the workflows have sensible defaults if you want to start without a project config.

3. Describe what you want, then ship it

Write a PRD at docs/reqs/main.md. The fastest way is conversational:

Harness	Write an implementation plan
Claude Code	`/synthex:write-implementation-plan`
Codex CLI	`$write-implementation-plan`
Grok	`/synthex:write-implementation-plan`
Gemini CLI	Ask Gemini to use Synthex's `write-implementation-plan` skill
OpenCode	Ask OpenCode to use Synthex's `write-implementation-plan` skill

This pulls in the Product Manager agent. PM interviews you, drafts the plan, runs it through a peer review loop with the Architect, Designer, and Tech Lead, then writes the finalized plan to docs/plans/main.md.

Then execute:

Harness	Execute the next batch
Claude Code	`/synthex:next-priority`
Codex CLI	`$next-priority`
Grok	`/synthex:next-priority`
Gemini CLI	Ask Gemini to use Synthex's `next-priority` skill
OpenCode	Ask OpenCode to use Synthex's `next-priority` skill

This identifies the next batch of unblocked, non-overlapping tasks (up to your concurrent_tasks limit), spins up a git worktree per task, delegates each to a Tech Lead instance, and merges the results back as they pass review. Run it repeatedly — once per delivery batch — until the plan is done.

What happens behind the scenes

Every plan task carries a typed acceptance criterion:

Tag	Meaning
`[T]`	Testable — proven by an automated test that must pass before the task merges
`[H]`	Human-validated — requires your explicit approval before merge
`[O]`	Observational — measurable only after deployment (adoption rates, error reduction)

Code reviews run automatically before any merge: code review + security review as mandatory gates, with optional performance, design-system, and reliability reviewers configurable per project.

The full plan — read the plugin README for the complete command + agent reference
Source — the plugin's markdown-and-YAML source on GitHub
Agent compatibility — install the same workflows in Codex, Grok, Gemini CLI, OpenCode, or another Agent Skills host

Getting started

#1. Install Synthex

#Claude Code

#Codex CLI

#Grok

#Gemini CLI

#OpenCode

#2. Initialize your project

#3. Describe what you want, then ship it

#What happens behind the scenes

#Next