Change requests — propose or apply updates to your team's context files
Use change requests when you have new insight or learning that should be reflected across the team's shared context files.
When to use this
- You learn something about your users, competitors, or strategy that should update the team's context
- You want to correct or expand a context file based on recent discovery or research
- A teammate has flagged that a context file is out of date for your product
Setup
- Open mySecond and navigate to the context file you want to update.
- Make your edits directly in the editor, or work with Claude Code to draft the revision.
- Add a rationale explaining what changed and why — this is required when submitting a change request.
- Submit the change request to send it to your lead for review.
Your lead will approve or reject the request. If approved, the update is applied to the shared context file for your product.
How it works
Your ability to apply or propose changes depends on your permission type.
Leads can edit context files directly — both in mySecond and in Claude Code. Changes take effect immediately without a review step.
Contributors can propose changes to context files in either mySecond or Claude Code. Each proposal requires a rationale and goes to the lead for your product to approve or reject. Once approved, the change is applied to the shared context file.
This keeps your team's context accurate without requiring every update to go through a single person — contributors surface insights, leads control what becomes canonical.