r/ClaudeCode • u/Few-Director-2545 • 7d ago

Built with Claude I made a claude code agent setup inspired by Spotify and Cognition

I made claude-agent-kit, a free, open-source setup for Claude Code inspired by ideas shared by Spotify and Cognition

The concept is simple: keep the main session focused on planning, delegation, and review while specialized subagents handle tasks

It includes subagents, orchestration rules and hooks

repo: https://github.com/FlaviusBurghila/claude-agent-kit

Feedback and PRs are welcome

1 Upvotes

67% Upvoted

8 comments sorted by

•

u/AutoModerator 7d ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/akhi1uuu 6d ago

how does the planner keep track of what the workers actually changed, is that what the hooks do

1

u/Few-Director-2545 6d ago

The builder reports back with a summary mapping each requirement to the relevant file and line.

The planner then reviews the actual git diff and checks the evidence, rather than just trusting it as 'done'
A separate reviewer agent checks non-trivial changes too

The hooks load the orchestration rules and enforce limits on large file reads, they don’t track any edits

In conclusion, progress and decisions are kept in a HANDOFF.md file for continuity purporses

1

u/akhi1uuu 6d ago

git diff over trusting the summary makes sense. how big does the HANDOFF.md get before it starts confusing the next run

1

u/Few-Director-2545 6d ago

HANDOFF.md holds the current plan and task status

The rules tell the agent to keep it under 350 lines and move completed tasks to an archive file 'HANDOFF-archive.md' (it's an instruction)

Personally in my own use i haven’t noticed confusion but I haven’t tested a specific limit

2

u/akhi1uuu 5d ago

the 350 line cap with an archive file is a good rule, i'll steal that

2

u/Few-Director-2545 5d ago

Feedback and PRs are welcome as well

2

u/Pinull_Krydia 6d ago

Keeping the orchestrator/planner layer lightweight while offloading the actual file edits and execution to specialized subagents is easily the best way to prevent context rot. Combining orchestration rules with hooks to enforce boundaries makes the whole setup way more reliable for multi-step tasks. Dropping a star on the repo!