Goals and OKRs · Standard
Objectives with key results, weekly check-ins, stakeholders and a status that is computed from the work, not typed in. The planner drafts the tasks under a goal and waits for review; workload and capacity show who is overloaded before the sprint.

Key results
Add key results with a target and a unit; link tasks and integrations (GitHub, Sentry, Finance) so progress moves on its own. Status (on track, at risk, off track) follows pace against the date.
Check-ins
The assistant pre-fills the check-in from the week's tasks, PRs and conversations; the owner edits and confirms. Stakeholders get the summary; misses escalate.
Planner and workload
Describe what you want to achieve; the planner reads your team, docs and pipeline and drafts tasks with owners, dates and dependencies. The workload gauge and sprint net capacity catch overload before it happens.
Both: a goal can carry key results (OKR style) or just tasks and a date. Teams mix them.
Yes. Organization-level goals aggregate team goals; stakeholders see one view with the status computed from the work.
Invite the team, import what you have, and turn on only the modules you need.