aweek

aweek

If Claude Code is the doer, aweek is the planner.

Read the docs →  ·  Quickstart  ·  Recipes  ·  Skills reference

aweek is a Claude Code plugin for building a team of AI agents that handle the work that repeats. Each agent has a role, a weekly plan, and a token budget. The plan evolves every Monday based on what worked last week. You set direction. Claude Code does the work. aweek runs the week.

https://github.com/user-attachments/assets/cf5772db-b0e0-46e8-ab97-7320dd2ebfef

Why aweek exists

Most AI tools are great at one-off prompts. They're terrible at the work that repeats — the weekly competitive scan, the Monday newsletter, the customer feedback digest, the recurring research memo. That work doesn't need a smarter model. It needs a team that shows up on schedule, remembers what they did last week, and gets a little better each Monday.

aweek is that team.

Who it's for

• Founders running their own ops who can't keep up with weekly cadence
• Marketers and creators publishing on a schedule (blog → social → newsletter)
• Analysts and researchers running weekly digests, briefs, or memos
• Anyone whose week looks a lot like last week's

What you can build

A single agent on a calendar — sixteen scheduled tasks across five days, a daily review that closes each day, and a weekly review that ties the week to the month's goals. One budget, one cumulative plan.md, fresh Markdown in your repo every week.

	Mon	Tue	Wed	Thu	Fri
7am	Brief	Outreach	Interviews	Roadmap	—
9am	Inbox	—	—	—	Feedback
10am	—	Metrics	—	—	—
11am	—	—	Content	Issues	Numbers
3pm	—	—	—	—	Retro
5pm	Daily	Daily	Daily	Daily	Weekly

Full recipe → A weekly operator

Other agent templates

• An engineer — handles the engineering periphery: PR triage, dep drift, flaky tests, doc drift, retros. Never ships features.
• A content marketer — grooms the topic queue, drafts the post, atomizes it for social, writes the newsletter, reviews analytics.

What you get

You run	Your team does
aweek hire	Adds an agent — name, role, system prompt (auto-bootstraps on first run)
aweek plan	Drafts long-term goals → monthly objectives → weekly tasks. You approve.
aweek summary	Hands in a status report — done, pending, budget left
aweek calendar	Shows the week as an editable calendar grid
aweek manage	Lifecycle ops — pause, resume, top up budget, fire
aweek delegate-task	Drops work into another agent's inbox. Agents hand off to each other.
aweek setup	Explicitly bootstrap the project (usually auto-called by the first skill you run)
aweek teardown	Remove the heartbeat and/or .aweek/ data from a project

Try it in 60 seconds

/plugin install aweek@runbear-io   # once published
aweek hire                     # add your first agent (auto-bootstraps heartbeat)
aweek plan                     # draft & approve the week

Walk away. Come back Monday morning to a status report and next week's draft plan.

How it works (in 3 lines)

1. Skills (invoked via aweek [name]) shell out to a tiny aweek CLI for every state change.
2. Heartbeat is a 10-minute launchd user agent per project. It picks the next pending task per agent and runs it in a fresh Claude Code CLI session.
3. Storage is plain files: .aweek/agents/<slug>.json for scheduling, .claude/agents/<slug>.md for identity. No DB.

Every mutation is schema-validated and atomic. 2,000+ tests guard the data layer.

Install

aweek ships as a Claude Code plugin. The plugin's SessionStart hook installs the aweek CLI on first run.

From a Claude Code marketplace (when published):

/plugin install aweek@runbear-io

From source:

git clone https://github.com/runbear-io/aweek.git
cd aweek && pnpm install && pnpm link --global
claude --plugin-dir .

/reload-plugins picks up edits without restarting.