Industry · Software & SaaS · schema_pack: 7 types
Each agent carries with it what the team already decided.
Architecture decisions, support feedback, and onboarding that starts from accumulated context, delivered to Claude Code, Cursor, Codex, and Devin via MCP.
Scenario
How context circulates when ValorBrain is in the flow.
- 01
Claude Code closes the architecture discussion and the decision-extractor records the decision with its source (ADR, PR) and owner.
- 02
The next day, Cursor receives the current standard via context-surfacing, right at question time.
- 03
Nobody re-explains: the new endpoint already ships in line with the ADR, consistent across agents.
- 04
Support records the exception granted to the customer, with source and who approved it.
- 05
In the roadmap discussion, the agent retrieves the cases behind the request, not just the request.
- 06
The decision to prioritize (or not) gets recorded, and the next discussion starts from it.
- 07
The engineer joining, or the new agent, receives what changed since the last session.
- 08
The handoff-generator routes pending work with the permissions inherited from whoever opened the task.
- 09
The team's accumulated context becomes a starting point, not archaeology material.
Schema pack
Schema pack types: decision + adr + feature + bugfix + refactor + antipattern + feedback de suporte
Next step
Less starting over. More continuity
Bring a real project. In one conversation we map where context gets lost between the people and agents on your team, and where to start.