By Epiphytic
Brainstorm-to-implementation multi-LLM development workflow plugin — three-phase pipeline with teammate Claude Code instances, beads-based task tracking, and per-plan-phase nurture and secure review
This skill should be used when the user asks to "run the brains pipeline", "start the brains workflow", "plan and implement from scratch", "do an ADR", "start with brainstorming", or invokes "/brains:brains". Phase 1 of the BRAINS pipeline: interactive research, question generation, questionnaire, architecture synthesis, and ADR production. Supports --single, --parallel (default), and --debate modes, and an optional --autopilot flag that auto-chains into hands-off map + implement. Chains into /brains:map at the user gate.
Generate architecture diagrams for ADRs. Emits Mermaid source (.mmd) for flowchart, state, er, and sequence types and Structurizr DSL (.dsl) for c4. Source and .svg output are stored side-by-side in docs/adr/diagrams/. Invokable standalone or auto-triggered from brains:brains phase-1 step 8.
This skill should be used when the user asks to "document mode", "edit only docs", "just update the docs", "fast-path a doc change", or invokes "/brains:document". Canonical entry point for BRAINS document mode: an abbreviated spine for document-only changes that skips planning, teammate orchestration, nurture, and secure. Runs an eligibility gate, lightweight research, the full 2-4 question questionnaire, a slim ADR, inline document edits, direct star-chamber council review (replacing nurture+secure), and an inline commit. Supports --single, --parallel (default), and --debate modes for the review phase, plus --autopilot and --lean.
This skill should be used when the user asks to "implement the plan", "execute the plan", "start implementation", "build the tasks", "run the teammates", or invokes "/brains:implement". Phase 3 of the BRAINS pipeline: spawns a teammate Claude Code instance per plan-phase via agent-teams (preferred) or tmux (fallback), waits on beads state, handles task failures with two-strike-plus-human-in-loop flow. Supports --single, --parallel (default), and --debate modes for nurture/secure review within each plan-phase, plus an optional --autopilot flag that runs hands-off across phases until a needs-human ticket or direct user intervention stops it. Also supports --resume to pick up after a pause.
This skill should be used when the user asks to "map out the plan", "create the implementation plan", "outline the tasks", "plan it out", "sketch the implementation", or invokes "/brains:map". Phase 2 of the BRAINS pipeline: high-level plan generation (no implementation specifics), topic-slug derivation, optional branch creation, beads task creation with brains:-prefixed labels, and user approval gate. Supports --single, --parallel (default), and --debate modes for plan review, plus an optional --autopilot flag that skips user gates and auto-chains into /brains:implement --autopilot. Chains into /brains:implement at the user gate.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Brainstorm Research Architect Implement Nurture Secure

A structured, multi-LLM development workflow plugin for Claude Code. Guides complex tasks through a three-phase pipeline, with optional multi-model debate and review at each stage.
Why three phases, just-in-time grooming, and per-phase review? See docs/why-brains.md for the design rationale — why forced brainstorming, sequential phases, focused teammate context, and star-chamber gating reduce token spend and rework compared to unstructured LLM coding.
BRAINS encodes a three-phase methodology for tackling complex software tasks:
--parallel with star-chamber review.brains:-prefixed labels.Each phase chains into the next via a user-approval gate — or, with --autopilot, skips those gates and runs hands-off from phase 1 through phase 3, stopping only on a brains:needs-human escalation. The nurture, secure, and diagram skills remain user-invocable for standalone use on any codebase.
For changes that only edit documents (prose, not code), /brains:document provides an abbreviated fast path that skips planning, teammate orchestration, and the nurture+secure passes — reviewing the final document(s) directly with the star-chamber council instead. It is a terminal alternate route: it ends after inline edits, council review, and its own commit, and never enters phases 2 (map) or 3 (implement). It is auto-invoked from phase 1 when a change is document-only and eligible, or requested explicitly via --document-mode. See Document mode.
See docs/diagrams.md for rendered examples of all five diagram types (flowchart, state, c4, er, sequence) — including the pipeline itself as a flowchart and a C4 context diagram of the plugin's components.
Required:
Required for multi-LLM modes (parallel, debate):
uvx star-chamber)~/.config/star-chamber/providers.jsonRequired for phase 3 (/brains:implement): either
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 in settings; Claude Code v2.1.32+)Strongly recommended:
TaskCreate / TaskUpdate (tmux mode) or agent-teams' built-in task list (agent-teams mode) with degraded functionality.Optional:
mmdc fallback renderer for brains:diagram (Mermaid types only)./brains:setup --with-kroki, which runs a local yuzutech/kroki gateway paired with the yuzutech/kroki-mermaid companion on a user-defined network. This is the preferred diagram renderer and the only path that supports --type c4 (Structurizr DSL); for Mermaid types, brains:diagram falls back to mmdc and then to source-only.From GitHub:
# 1. Register the marketplace (one-time)
claude plugin marketplace add --github Epiphytic/brains
# 2. Install the plugin
claude plugin install brains@brains-marketplace
From a local clone:
# 1. Register the marketplace (one-time)
claude plugin marketplace add /path/to/brains
# 2. Install the plugin
claude plugin install brains@brains-marketplace
After installing, run /brains:setup --global to install dependencies and configure LLM providers, then /brains:setup --local in each project for project-specific settings. Add --with-kroki to either invocation to pull and run a local Kroki container as the diagram renderer — undo later with --without-kroki.
npx claudepluginhub epiphytic/brains --plugin brainsPre-configured skill management for Claude Code — discover, activate, and invoke skills from skills.sh and GitHub with security gating.
Claude Code plugin for spawning sandboxed LLM instances with intelligent resource provisioning and lifecycle management
AI-powered development tools for code review, research, design, and workflow automation.
Plan and autonomously build a software task end-to-end. Recons the codebase, applies preloaded memory, decomposes into the right number of phases, gets one confirmation, then prepares a single ready-to-paste /goal command — one paste between you and done — that drives execution to completion with built-in retry, fix-spec recovery, and per-phase memory writeback. Works on Claude Code and Codex.
Plugin for effective agentic development
No description provided.
Structured project planning and execution through brainstorm, spec, and build phases across three execution tiers: sequential, delegated sub-agents, and full agent teams
Describe your goal, approve the spec, then step away — Claude and Codex loop together until it's right.