Nebula is a small framework that structures multi-agent workflows using explicit contracts. I wanted to get feedback from people actually using coding agents so I can improve on it. Repos are here: https://github.com/gajakannan/nebula-agents https://github.com/gajakannan/nebula-insurance-crm The problem I kept running into: a single session can now do a lot, write code, explain architecture, review tests, think through product behavior, suggest refactors. But it got blurry fast. I can’t always tell what perspective the agent is coming from anymore. I wanted to see how I can encode my real life work experience in this. Nebula is my attempt to make that explicit, not through personality prompts, but by defining small role contracts around the work: what each agent is responsible for what it should not decide what output it should produce how it fits with other agents in a workflow maintain the token economics and context to avoid context bloat, avoid hallucinations, and consistent agent ops what telemetry would be useful to understand agent behavior over time I’m testing it against an insurance CRM because that domain I am familiar with and has enough complexities to pressure test the framework. A screen can render and still be wrong. A test can pass and still miss the workflow. The code can be clean and still fail the business intent. The starter prompt I use asks Claude Code/Code to walk through the repos, Please review these two repos in full. Don’t make assumptions. https://github.com/gajakannan/nebula-agents https://github.com/gajakannan/nebula-insurance-crm Walk me through the purpose of the system with a detailed report. My experience level with AI agentic development is: [beginner / intermediate / advanced] My technical skill level is: [non-technical / developer / architect / engineering leader] Explain the purpose, how the agent workflow is structured, how the insurance CRM is being used as the proving ground, and what parts look useful versus over-designed. A few things I’d genuinely like feedback on: Would repo-level agent definitions be useful, or just more ceremony? What would make something like this lightweight enough to actually use? Is this solving a real problem, or am I over-structuring? Feel free to stress test and poke holes in the idea. Thanks! submitted by /u/hello-insurance
Originally posted by u/hello-insurance on r/ClaudeCode