Hamster for Roo Code

The planning layer for Roo Code.

Hamster syncs briefs, plans, and team decisions into your repo. Roo Code reads them directly — full context on every session.

The problem

Roo Code needs more than a prompt to build the right thing.

Prompts lack product context

Roo Code generates from what you type. Without structured requirements, it fills gaps with assumptions that do not match your team decisions.

Large features need decomposition

Handing Roo Code a full feature description produces sprawling changes. Someone has to break the work down — manually, every time.

No persistent project context

Each session starts fresh. Roo Code does not remember what was decided, what was completed, or what remains in the feature plan.

Hamster structures work for Roo Code.

Write a brief in Hamster, and AI expands it into a full spec. Generate a plan with scoped tasks. The Hamster CLI syncs everything into .hamster/ — Roo Code reads the full context directly.

Structured briefs as input

Roo Code sessions start with requirements, constraints, and acceptance criteria instead of ad-hoc prompts. The output matches the spec.

Task-sized units of work

Hamster decomposes features into tasks that fit a single focused session, preventing scope creep and making PRs easier to review.

Always-on context via the CLI

The Hamster CLI syncs briefs, tasks, and plans into .hamster/ as markdown files in real time. Roo Code reads them on every action.

How teams use Hamster with Roo Code

Feature implementation

Before

Describe the feature in a prompt. Hope Roo Code infers the right scope. Fix the output when it misses requirements.

After

The Hamster CLI syncs the full brief into your repo. Roo Code reads .hamster/ files and builds against the spec your team aligned on.

Multi-session work

Before

Re-explain remaining work each session. Track progress manually.

After

The CLI keeps task status in sync. Each session picks up where the last one left off.

Team coordination

Before

Developers using Roo Code independently have no shared context or task boundaries.

After

Hamster breaks features into non-overlapping tasks with clear acceptance criteria for each.

Give Roo Code the context it needs.

Structured briefs and scoped tasks for focused AI-assisted development.

Start building with Hamster