Bring the context.
Provide merged change and linked issue, current documentation, documentation style and ownership. Choose the systems and documents this team is allowed to read.
Engineering
Keep documentation aligned with code changes.
Find documentation affected by a change and prepare a reviewed update with code references.
WORKING DRAFTKeep documentation aligned with code changes
Code changeConfiguration updated
Affected docsSetup guide
PatchOwner review
Sources retainedOwner review
Illustrative output. Your records and rules shape the workflow.
CONNECTED TO YOUR STACK
Your systems. One coordinated workflow.
Bring context from the tools your team already uses. Connect MCP servers and APIs to read records, coordinate actions and keep the evidence together.
FROM INPUT TO OUTPUT
See how the work comes together.
Explore the request, the responsibilities and the handoff. Each step keeps the source context attached.
WHAT STARTS THE WORK
A code change lands in the approved branch.
Corin uses the request together with the procedures and records you make available to this workflow.
01Merged change and linked issueContext
02Current documentationContext
03Documentation style and ownershipContext
SPECIALIZED RESPONSIBILITIES
A team built around this task.
These example roles show how the work can be divided. Review the proposed team, models, tools and permissions for your process.
1
Change context agent
Identify changed behavior, configuration and public interfaces from the merged code.
2
Documentation mapping agent
Find documentation that describes those areas and compare it with the new behavior.
3
Drafting agent
Prepare a documentation patch with source references and owner review notes.
READY FOR THE NEXT STEP
A documentation update proposal tied to the code changes it explains.
The result includes its source context so the responsible person can review it and decide what happens next.
YOUR WORKFLOW DELIVERS
- A documentation update proposal tied to the code changes it explains.
- Supporting records and source references
- Open questions and the accountable reviewer
WHERE THIS FITS
Keep documentation aligned with code changes with your own records and rules.
A code change lands in the approved branch. The team needs merged change and linked issue, current documentation and documentation style and ownership to make the next step useful.
Start with the procedure your team already follows. Corin uses that context to propose responsibilities and help coordinate the work across the tools you connect.
MAKE IT YOURS
Start with one process.
Review the responsibilities.
Use change context agent, documentation mapping agent, drafting agent as a starting point. Set each role's tools, permissions and approval boundaries.
Check the first handoff.
Run a representative task. Compare the result with your procedure, review its sources and open questions, then refine the team before expanding the workflow.
KEEP EXPLORING
Other work your agents could take on.
ContextReviewNext step
Change scopeAPI validation
Test evidenceCI results attached
ReviewTwo questions to resolve
Engineering
GitHub
Slack
Notion+ more
Prepare a pull request review brief
Summarize the change, examine test evidence and give reviewers a focused set of questions.
GitHubSlackNotion+ moreRouting & handoffsExplore workflow
Version changeRelease notes reviewed
CompatibilityMigration checked
ValidationResults for maintainer
EngineeringGitHubSlackNotion+ more
Prepare dependency updates with test evidence
Bring release notes, compatibility concerns and validation results into a dependency update proposal.
GitHubSlackNotion+ moreTask coordinationExplore workflow
WORKING DRAFTGet ready before a contract renewal
Renewal date60 days away
Account signalsUsage and support reviewed
Owner packetDraft ready
Sales
Salesforce
Google WorkspaceSlack+ more
Get ready before a contract renewal
Bring usage, support history and contract terms into a renewal brief before the conversation begins.
SalesforceGoogle WorkspaceSlack+ moreResearch & draftsExplore workflow
OPEN SOURCE AT THE CORE
Build this around your way of working.
Give Corin your procedures, connected context and approval rules. Review the agent team, then put it to work.