Refresh product context
Keep the Product Brain current with what changed in Jira, code, documents and meeting notes, so every other Activity starts from today's facts.
Product statusAvailable now
Why it matters
Other AI looks for context when asked. Teklens keeps it up to date. This Activity is the maintenance loop behind that sentence: changes are detected, compared with what the team believes to be true, and only approved changes become authoritative.
Owner
Product Manager
Agent-led
Participants · Agents
Trigger
A material change in Jira or code, a new decision, or a scheduled context review.
Required context
Optional context
Skills
Activity steps
- 1Detect what changed in the connected sources since the last refresh.
- 2Compare the changes with the current Product Brain and previous decisions.
- 3Propose updates and flag conflicts, including documentation that drifted from the code.
- 4Apply approved changes and notify the Activities that depend on them.
Output
Proposed context changes with a conflict list.
Artifacts
Updates: Product Brain, Documentation
What good looks like
- Only material changes are proposed.
- Every change is traceable to a source.
- Conflicts are explicit, never silently resolved.
- No speculation is promoted to fact.
Quality gate
Destination
Usually next
Method references: DORA 2025: connect AI to internal context
Deep dives from the AI PM Lab
Articles that explain the thinking behind this Activity.
Show us exactly how product work happens today.
Thirty minutes with a founder. We compare your process with the Playbook and pick the first Activity to run on your Jira and your repo.