AI PRODUCT PLAYBOOK
Every Activity combines the right people, agents, context and quality gate, from customer evidence to shipped software.
Your team keeps the judgement. Teklens handles the coordination around it.
An Activity is a concrete step of product work, from the first source to human approval. It knows who owns the job, what context it needs, which agents and skills to use, what good looks like and where the result goes.
How the Playbook works
The clearest examples of context-aware, multiplayer product work.
Synthesise across participants without counting repeated mentions as independent evidence; communicate decisions with their support.
Answer whether the opportunity deserves exploration without prematurely prescribing requirements or implementation.
Prioritise by objective contribution without forcing essential maintenance into an invented strategic link.
Describe what users must be able to do, explicitly bound scope, and avoid substituting design or architecture for requirements.
Prepare and refine a PM-agreed subset of upcoming stories; preserve partial meeting coverage, per-story discussion and confirmation, and resume the same Activity without overwriting approved sources.
Review actual change scope and system effects, separating substantiated issues from optional preferences.
Translate shipped changes into user value and never equate a merged change with general availability.
Learn from system conditions and information available at the time, preserving uncertainty and avoiding personal blame.
Start wherever the conversation has useful evidence. The steps are prompts for the Activity, not a required sequence, and «usually next» is a suggestion, not a mandatory step.
Set the Product AI direction with us, or test the shared Product Brain on real work with Jira and code.
