/euxlab-write-okrs
The engagement folder into two or three outcome OKRs, every key result with a baseline, a target, and a source.
When you reach for it
A team has to set OKRs for a quarter or a half. The skill reads what the engagement folder already knows, shows you the gaps, and interviews you only about those. The more the folder holds, the shorter the interview.
Input, output, writes
- Input
- Whatever the engagement folder holds: the stakeholder map, the interview guide, insights, personas, the design brief. Plus any draft OKRs.
- Output
- One file: a context map with sources, two or three objectives with owners, key results, initiatives, risks, a cut list, a self-critique, and scoring guidance.
- Writes
- docs/okrs.md
Completion criterion
Two or three objectives, each naming an outcome and an owner. Every key result has a metric, a graded baseline or baseline unknown with a measurement plan, a target, a date, and a source. Every trap checked against every key result, each hit fixed and recorded. The cut list holds at least one item. Someone outside the team could score every key result at period end from the file alone.
Checkable, and demanding. A skill that cannot say whether it is finished is a prompt.
Anti-patterns
- A task list with numbers. "Ship 3 features" measures the team’s calendar, not an outcome.
- An invented baseline. A plausible number with no source is a D dressed as an A.
- A lone speed metric. Time to resolve with no reopen rate beside it rewards closing cases badly.