Login

u/Alive-Replacement-75

I built /octowiz — a coordinator skill that routes Claude Code through plan / TDD / review using LiteLLM memory
▲ 2 r/vibecoders_+1 crossposts

I built /octowiz — a coordinator skill that routes Claude Code through plan / TDD / review using LiteLLM memory

Most AI coding tools give an agent either a giant system prompt or nothing. octowiz takes a third path: doctrine lives in LiteLLM `/v1/memory`, agents fetch only what’s relevant to their current phase, and a `/octowiz` coordinator routes between superpowers and mattpocock-skills.

The result is that a planner gets planning doctrine, an implementer gets TDD loops and deep-module principles, a reviewer gets fresh-context-review discipline. None of them carry the others’ doctrine as noise.

What you get:
- 26 LiteLLM memories distilled from Matt Pocock’s AI Engineer workshop (planner / implementer / reviewer / qa slices, plus routing contracts).
- `/octowiz` slash command — reads project state, picks A/B/C/D (fresh idea / stress-test plan / implement / review), routes to the right upstream skill.
- v0.2 ships a local cache for the durable doctrine. Sub-second boot, offline fallback when LiteLLM is unreachable.

OSS, MIT, no signup. I built this on top of work by Matt Pocock and Jesse Vincent — neither library is bundled, octowiz just routes.

Repo: https://github.com/raelli/octowiz

Genuinely curious what other Claude Code users do for keeping context tight across long-running coding sessions.

u/Alive-Replacement-75 — 3 days ago
▲ 1 r/cursor

Tooling pattern · cache your agent’s doctrine layer, not its prompt or its response

Three layers of an agent stack can be cached:

  • the LLM response — fast on hit, dangerous on stale.
  • the prompt — saves tokens, not latency.
  • the doctrine — the stable rules the agent retrieves before it does anything.

I think the third is the most interesting and the most under-cached. So I built octowiz-cache for it.

octowiz is an OSS coordinator skill for Claude Code (works the same way for any slash-command-based agent). The doctrine layer is now cached to ~/.cache/octowiz/... with a manifest + TTL. /octowiz boots in ~200ms once warm, refuses to silently serve a stale plan from yesterday’s repo state, and falls back to stale-but-served when the upstream proxy is unreachable.

Volatile project state — git status, file contents, test output — is never cached.

Repo: https://github.com/raelli/octowiz. Not Cursor-specific. MIT.

reddit.com
u/Alive-Replacement-75 — 3 days ago