Skip to content

Quick Start

This guide gets you from zero to your first Systematic workflow in under five minutes.

You need OpenCode installed and running. That’s it. No API keys, no accounts, no extra tooling.

  1. Add the plugin to your OpenCode config

    Open ~/.config/opencode/opencode.json and add Systematic to the plugins array:

    {
    "plugins": ["@fro.bot/systematic@latest"]
    }

    If you already have other plugins, add it to the existing array.

  2. Restart OpenCode

    Close and reopen your OpenCode session. The plugin loads automatically on startup — no manual wiring required.

  3. Verify it’s working

    In any conversation, check that systematic_skill appears in the available tool list. If you see it, you’re good. You can also run:

    /systematic:using-systematic

    The skill will load and display usage instructions.

Systematic is built around a four-step loop. Here’s what it looks like in practice, using a concrete task: adding a dark mode toggle.

  1. Brainstorm — Explore the problem before writing code

    /ce:brainstorm "add dark mode toggle"

    The brainstorm skill asks clarifying questions, surfaces edge cases, and produces a requirements document. You end up with a clear scope before a single line of code is written.

  2. Plan — Break the work into a structured implementation plan

    /ce:plan

    Takes the requirements document from the brainstorm and produces a sequenced implementation plan. For high-stakes work, run /systematic:deepen-plan afterward to stress-test the plan’s assumptions.

  3. Work — Execute the plan

    /ce:work

    The agent follows the plan, tracks progress, and surfaces blockers instead of silently guessing. You stay in the loop without micromanaging every step.

  4. Review — Check the work before opening a PR

    /ce:review

    Tiered persona agents check for correctness, security, performance, and style — in parallel. You get a structured report, not a wall of unranked comments.

After shipping, use /ce:compound to capture what you learned. That knowledge becomes part of the system and speeds up the next similar task.

  • The Systematic Philosophy — Understand why the loop is structured this way and what “compounding” actually means in practice.
  • Configuration — Disable bundled content you don’t want, add project-specific skills, or configure agent overlays.
  • Skills Reference — Browse all 40+ bundled skills and when to reach for each one.
  • Agents Reference — Explore the specialized subagents available for review, research, and architecture work.