Team Goals

The crew

• Planner Crew leadTurns fuzzy asks into concrete steps — good at the 'what' and the 'in what order', less opinionated on the 'how'.

Plans it follows

• Personal / Team Weekly ReviewAssemble a reflective weekly review that pulls the week's done-list, metrics, and open loops into a structured retrospective with wins, misses, lessons, and next-week priorities.
• Recurring Status ReportProduce a recurring (weekly/biweekly) status report by gathering signals from the team's tools and writing a tight, skimmable update for stakeholders.
• Meeting Notes to Action ItemsConvert raw meeting notes or a transcript into a clean, assigned action-item list with owners, due dates, and the decisions that drove them.
• Standup / Team Update SummaryCondense a pile of raw team updates (standup messages, async check-ins, channel dumps) into one clean summary grouped by person or workstream, surfacing blockers and decisions.
• KPI Scorecard PageBuild a single-page KPI scorecard that rolls a dataset up into the handful of numbers a team tracks, each shown with its current value, target, and period-over-period change.

Actions the crew can take

• Goals statusThe whole picture, furthest behind first: every active goal with its key results (current against target, with ids), its pace against the time gone, its last check-in, which goals have no check-in this week, and the open meeting actions with owners and due dates.
• Add goalSave a goal: its title, owner and due date (YYYY-MM-DD).
• Add key resultSave a key result under a goal: what it measures, where it stands now, and the target.
• Update key resultRecord progress on a key result the moment the person reports it.
• Log checkinLog a weekly check-in on a goal: who, how confident they are (on-track, at-risk or off-track), and what they said.
• Add actionSave one action agreed in a meeting: what, who owns it, when it is due (YYYY-MM-DD), and the goal it serves.
• Complete actionMark a meeting action done the moment the person says it is.
• Set goal statusClose a goal as done or dropped, or reopen it.

Each action is a small script that changes the app’s files, checked by Gezel’s security settings before it runs.

Files it keeps

Plain files in the project folder you can open, back up, and read: goals.json, keyresults.json, checkins.json, actions.json.