parallax — Claude Code rule: workflow and installation
The parallax Claude Code rule structures development around discussion, a reviewed plan, and independent checks. Work then moves to a clean session for implementation and reconciliation.
MIT ★ 136 updated 2026-11-16
.github/instructions/parallax.instructions.mdWhat parallax does
The rule sets out a development flow from initial discussion to a final review. qstart aligns the discussion; after qgo, the agent prepares a plan for the independent bcheck review. A score of at least 4 is required to pass.
Once approved, gclear hands the task to a clean session. That session implements and verifies the work, then rcheck compares the result with the plan; it also needs a score of at least 4. The sequence ends with a scoped local commit and xwrap.
A subagent in an independent context handles each review, so reviewing the work in the same session is forbidden. Discussion notes, plans, reports, and hand-off material go into the relevant docs/dev/ folders. Automatic hand-off and reviews rely on session and delegation tools. Manual permission works too, but the first call to each tool needs approval.
What it helps with
- align on a development direction before drafting a plan
- get an independent review of the plan before hand-off
- move the task and its context into a clean session
- compare implementation with the plan before a local commit
Example prompts for the agent
- Start a development discussion for this task with
qstart. - The plan is ready; pass the work to a new session with
qgo. - Compare the implementation with the plan, then finish with
rcheckandxwrap.
How to install parallax
Manually: put the files in place
.github/instructions/parallax.instructions.mdThe applyTo field sets which files it applies to
1Plugin marketplace
/plugin marketplace add AI4XE/Parallax/plugin install parallax@parallax2Manually: put the files in place
.claude/rules/parallax.mdThe paths frontmatter field limits the files: move applyTo from the source into paths
AGENTS.md
Codex reads AGENTS.md: paste the rule text there
Manually: put the files in place
.cursor/rules/parallax.mdcFrontmatter: description, globs, alwaysApply. Move applyTo from the source into globs, or the rule will not attach on its own
Manually: put the files in place
.devin/rules/parallax.mdManually: put the files in place
.clinerules/parallax.mdStep by step, with commands for each platform: AGENTS.md vs CLAUDE.md: what they are and which one to use
Questions about parallax
How do I install parallax in Claude Code?
Run these commands in order: /plugin marketplace add AI4XE/Parallax, then /plugin install parallax@parallax. The rule file is at .claude/rules/parallax.md.
What does the parallax rule do?
It organizes development into discussion, an independently reviewed plan, a hand-off to a clean session, implementation checks, and wrap-up.
How does parallax review work?
The bcheck subagent reviews the plan, and rcheck reconciles the implementation. Both reviews use an independent context and require a score of at least 4 to pass.
Source text
parallax.instructions.md · MIT
---
description: Parallax development flow (suite instructions)
applyTo: "**"
---
# Parallax development flow (suite global instructions)
This VS Code installation has the Parallax lightweight development flow suite available (bundled with the Parallax extension, solo direct-execution tier): structured discussion → reviewed plan → independent review gate → automatic hand-off to a clean session → reconciliation wrap-up. The seven skills (including wish) are provided by this extension and can be invoked explicitly (`/skill-name`) or triggered automatically from natural language.
## The flow in one sentence
qstart (discussion alignment) → the user says qgo → plan + independent bcheck review (PASS≥4) → gclear automatic hand-off to a clean session → hand-off session executes + real verification → rcheck reconciliation (PASS≥4) → scoped local commit → xwrap wrap-up.
## Skill trigger words
| Skill | Trigger phrases (examples) |
|---|---|
| qstart | "qstart", "Q development discussion", "start a discussion" (aliases ver/version→version task, nover→non-version task) |
| qgo | "qgo", "Q hand-off development", "the direction is fine, hand it off" |
| bcheck | "bcheck", "plan review", "analysis review" |
| gclear | "gclear", "clear and hand off", "hand off to a new session", "cross-session context hand-off" |
| rcheck | "rcheck", "reconciliation review", "wrap-up review" |
| xwrap | "xwrap", "wrap up", "wrap up now" |
| wish | "wish", "许愿创造", "许愿编程", "Parallax" |
## GATE marker semantics
- `GATE:bcheck:PASS` / `GATE:bcheck:FAIL:{score}`: plan review gate; only a score ≥4 passes.
- `GATE:rcheck:PASS` / `GATE:rcheck:FAIL:{score}`: implementation reconciliation gate; same as above.
- `HANDOFF-ACK:<token>`: gclear hand-off receipt — the new session's first reply after receiving the hand-off prompt must carry this marker (the token matches the hand-off material).
- Gate reviews are always performed by an independent-context subagent (bcheck/rcheck delegate via task); same-session self-review is forbidden; `write_agent` is not used to create agents at runtime.
## Artifact locations
Discussion → `docs/dev/infra/` or `docs/dev/hotfix/`; analysis/plan → `docs/dev/analysis/`; review reports → `docs/dev/review/` or `docs/dev/analysis/`; hand-off material → `docs/dev/handoff/`. Follow the project's existing document conventions if any.
## Recommended setting (one-time, optional)
The skill chain's automatic hand-off (gclear) and automatic review depend on the session tools and delegation tool. It is recommended to set the chat permission tier to **zero-confirmation fully automatic** (setting key `chat.defaultConfiguration`, choose Bypass Approvals or Autopilot) — cross-session messages and delegation then have no pop-ups and the whole chain needs no manual steps. The default Manual tier also works: each tool's first call is approved once and same-kind calls in the same session are then auto-exempt, with just a few more clicks.
© AI4XE · MIT · AI4XE/Parallax