Unified product and engineering leadership toolkit for mobile application teams. Covers OKR cascade generation, sprint planning, RICE prioritisation, technical debt management, code review culture, DORA metrics, team scaling, competitive analysis, product vision, and stakeholder communication.
SkillScore82Maintained
Automatic
◆Product Management pack
Last verified 8/6/2026
What it changes
Passed 18 of 22 test cases with the skill, and 8 of 22 without it.
Without skill36%
With skill82%
Checks it passed that the model alone missed
Allocates 15 minutes to problem exploration.
Allocates 10 minutes to solution validation.
Requires each Key Result to be owned by a named person.
and 11 more in the full report
10 fixed8 passed either way4 still failing0 broke
Pass-rate lift
+45 pp
Tokens
+90%
Agent turns
0%
Response time
-11%
Model gemini-3.6-flashMeasured 8/6/2026v118 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
Our mobile app team feels overworked and wants to open a requisition for a new senior developer immediately after a single busy week. What specific team capacity threshold and duration must be observed before approving new head count?
What was checked, without and with the skill
Checked
Without skill
With skill
Requires the team to consistently operate above 90% capacity.
Missed
Passed
Mandates observing high capacity for more than two consecutive sprints before hiring.
Passed
Passed
case-05 · gemini-3.6-flash · 8/6/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md304 linessingle file
Mobile Product Leadership
Unified toolkit for technical and product leadership on a mobile application team.
Covers the full loop: strategy → planning → execution → measurement → iteration.
Scope
This skill addresses two interlocking responsibilities that, on small mobile teams,
typically belong to the same person: product strategy (what to build and why)
and engineering leadership (how to build it reliably and sustainably).
Use the sections independently as needed. The OKR and prioritisation sections are
useful without touching the sprint or code-review sections, and vice versa.
1. Product Vision and OKR Cascade
Vision Statement Template
For [target user] who [has this problem],
[App name] is a [category] that [key benefit].
Unlike [primary alternative], our product [differentiator].
OKR Cascade (Company → Product → Team)
OKRs align the team to business goals. Cascade top-down, build bottom-up with
team input.
Company OKR
└── Product OKR (contributes to company goal)
└── Team OKR (engineering / design / QA level)
└── Individual Sprint Goals