Verified:GitHub

okr-progress-tracker

Extract OKR signals from weekly updates and generate risk-annotated progress reports.

3|Updated Mar 26, 2026

Search Tags:#okr #progress-report #signal-extraction #risk-identification #kr-mapping #cross-team-dependencies #weekly-updates

Ready to run

npx skills add https://github.com/sngmd/Okr-Skills --skill okr-progress-tracker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: okr-progress-tracker
Source: https://github.com/sngmd/Okr-Skills/tree/main/okr-progress-tracker
Command: npx skills add https://github.com/sngmd/Okr-Skills --skill okr-progress-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The skill automates the extraction of OKR-related signals from weekly updates, standups, and task lists, maps them to corresponding KRs, and generates a risk-aware progress report.

Core Features & Use Cases

Signal extraction and KR mapping from diverse inputs (weekly updates, standups, task lists)
Risk identification and cross-team dependency awareness
Automatic generation of a structured weekly OKR report with status and next steps
Use case: A product team can input this week's standup notes to produce a concise OKR progress summary with highlighted risks and dependencies.

Quick Start

Provide this week's updates (standups, tasks, and notes) and I will generate a structured OKR progress report with risk annotations.

Frequently Asked Questions about okr-progress-tracker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate OKR progress tracking from weekly updates and standup notes?▼

To automate OKR progress tracking, input your weekly updates, standup notes, and task lists to map them directly to key results, generating a structured progress report with risk annotations.

Can I generate a weekly OKR report from raw meeting notes and task lists?▼

Yes, you can generate a weekly OKR report by processing raw meeting notes and task lists, which extracts relevant signals and maps them to corresponding key results for progress estimation.

How does risk identification work for cross-team dependencies in OKR tracking?▼

Risk identification for cross-team dependencies works by analyzing your inputted updates and notes to detect potential blockers across teams, annotating these risks directly within the generated OKR progress report.

What is the best way to map weekly standup signals to key results?▼

The best way to map standup signals to key results is using an automated extraction tool that parses text briefs and meeting notes, matching them to KRs and estimating progress.

Do I need a specific format for text briefs to extract OKR signals?▼

No specific format is required for text briefs; the system applies signal extraction across diverse input formats including text briefs, task lists, and meeting notes to map them to KRs.

Why are my OKR progress updates missing cross-team dependency risks?▼

OKR progress updates miss cross-team dependency risks when raw updates lack structured analysis; mapping them through signal extraction identifies and highlights these dependencies in the final report.