Create quarterly OKRs based on team goals and role. Generates 3 Objectives with 3 Key Results each (9 total), with 70%/100% achievement criteria.
69
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Advanced interactive command that helps create individual quarterly OKRs based on team-level goals.
/okr --role <role> "<team-goals>" [options]| Argument | Description |
|---|---|
--role <role> | Role (engineer, pm, designer, qa, data-analyst, etc.) |
<team-goals> | Team-level goals (natural language text) |
| Option | Description |
|---|---|
--sample <path> | Reference OKR sample file |
--team-okr <path> | Reference team OKR file |
--previous <path> | Reference previous quarter OKR |
| Option | Description |
|---|---|
--output <path> | Output file path |
--format <type> | Output format: markdown/json/yaml |
| Option | Description |
|---|---|
--interactive | Interactive OKR creation mode |
--refine | Refine vague goals through questions |
# Basic usage
/okr --role engineer "20% revenue increase, NPS +10, 2 new product launches"
# With sample reference
/okr --role engineer "売上20%増加" --sample ./okrs/samples/engineer.md
# Interactive mode with persistence
/okr --role engineer --interactive --persistEach KR includes:
45a1bdf
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.