The planning layer for Roo Code.
The Hamster CLI syncs Briefs, Plans, and team decisions into your repo so Roo Code can work from your team's requirements alongside the code.
Free for 10 briefs a month.
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
A large feature needs to be broken into scoped Tasks so the implementation can be reviewed in manageable pieces.
No persistent project context
A new session needs a record of completed work, constraints, and team decisions to continue the feature without another explanation.
Hamster structures work for Roo Code.
Hamster drafts a Brief from your intent and generates a Plan with scoped Tasks. The CLI syncs that work into .hamster/ so Roo Code can read the requirements and acceptance criteria before building.
Structured briefs as input
The Brief gives Roo Code the requirements, constraints, and acceptance criteria that its implementation will be reviewed against.
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 CLI keeps the Briefs, Tasks, and Plans in .hamster/ current as your team makes changes, so Roo Code can pick up the latest requirements without manual copying.
How teams use Hamster with Roo Code
Feature implementation
Before
Requirements supplied only in a prompt can leave the scope unclear, requiring more explanation and corrections as the agent builds.
After
The agent reads the Brief and task details from .hamster/, so its work can be reviewed against the requirements your team agreed on.
Multi-session work
Before
Resuming a feature requires someone to explain what was completed and which work remains when that context is missing from the repo.
After
The CLI keeps task status and requirements in sync, so the next session can pick up the remaining work from the shared Plan.
Team coordination
Before
Developers working in separate coding sessions can duplicate work when they have no shared requirements or task boundaries.
After
Hamster gives the team a shared Brief and scoped Tasks, so each developer can choose work with clear acceptance criteria.
Bring your next Brief into Roo Code.
Your coding agent can work from the shared Brief and scoped Tasks, giving you clear acceptance criteria to review its changes against.
The Free plan includes 10 Briefs a month for you and your team.
Related pages
Hamster CLI
Install the CLI, sync briefs and plans into your repo, and give your coding agent full project context.
Hamster for Cline
Structured task specs for Cline autonomous sessions.
Hamster for Cursor
Plan outside the editor, build inside it with scoped Cursor sessions.
Hamster for Developers
Implementation-ready task specs for developers who ship with AI agents.