Quick Start

In 15 minutes you will go through the core Brewcode workflow: from writing a structured specification to capturing your project’s conventions and generating a project-tailored deep review skill.

Before you begin

Make sure Claude Code and the brewcode plugin are installed. If not, follow the instructions in Installation.

Full workflow

  1. Install brewcodeplugin install

    Add the plugin from the marketplace and install it into your Claude Code session:

    claude plugin marketplace add https://github.com/kochetkov-ma/claude-brewcode
    claude plugin install brewcode@claude-brewcode

    This step runs once per machine. Reload with /reload-plugins if already inside a session.

  2. Write a specification/brewcode:spec

    Describe the task in plain text or point to a requirements file:

    /brewcode:spec “Implement JWT authorization with role-based access”

    Or from a file:

    /brewcode:spec ./docs/requirements/auth.md

    What happens: the skill launches 5-10 research agents in parallel. They analyze the codebase, locate related code, dependencies, and patterns, then ask clarifying questions (use the -n flag for autonomous mode without questions).

    Result: a SPEC.md file — a structured specification with full project context.

  3. Capture project conventions/brewcode:convention
    /brewcode:convention

    What happens: parallel agents analyze each architectural layer, extract etalon classes and recurring patterns, and write them into .claude/convention/.

    Result: every later agent has a written reference for how this project does things — no more guessing at style or structure.

  4. Generate a deep review skill/brewcode:superreview
    /brewcode:superreview

    What happens: analyzes your codebase and conventions, then generates a project-tailored quorum review skill that merges code review and standards checking into one reusable skill installed locally at .claude/skills/.

    Result: a custom review skill ready to invoke any time you need a deep, project-aware code review.

  5. Create a domain agent team/brewcode:teams — optional
    /brewcode:teams

    Generates 5-20 project-specific agents with self-selection logic and performance tracking. Skip this step if the default agent set is sufficient for your project.

What’s next

After the workflow

Your project is set up for iterative development. Here is what you can do next:

Deep review — run a quorum review of any changes:

/brewcode:superreview

Extract rules — convert knowledge into project-wide coding rules:

/brewcode:rules

Prompt optimization — reduce tokens in prompts and agents:

/brewtools:text-optimize

All skills

🏛

brewcode

8 skills: spec, deep review, conventions, rules, teams, and more.

🔧

brewtools

11 skills for text utilities: prompt optimization, AI artifact removal, secrets scanning, SSH, deploy.

🖼️

brewui

Placeholder for future UI/visual/creative tools (currently empty).

📄

brewdoc

6 skills for documentation: automatic sync with the codebase, doc generation, memory sync, PDF conversion, publishing.

📋

All brewcode skills

Full list of 8 brewcode skills with commands, parameters, and dependencies.

👥

Dynamic teams

Create 5-20 project-specific agents with self-selection and performance tracking.

🚀

Latest Release

Download, changelog, and installation instructions.

🔗

View on GitHub

Source code, README, and configuration files.