Weekly Goal Progress Pulse

Measures your weekly progress against quarterly and annual goals with trajectory predictions, course correction suggestions, and milestone tracking. Connects to project management tools (Jira, Linear, Asana), OKR platforms (Lattice, 15Five), and personal goal files to generate a data-driven progress report that tells you whether you are on track, ahead, or falling behind -- with enough lead time to adjust.

Supported Platforms & Integrations

Platform	Setup Method	Auth Type	Notes
Jira	Jira Cloud REST API	API token + email	Sprint progress, epic completion, velocity
Linear	Linear GraphQL API	API key	Project progress, cycle tracking
Asana	Asana REST API	Personal access token	Goal tracking, project milestones
Notion	Notion API	API token	OKR databases, goal tracking pages

When to Use This Skill

• Use this when you set quarterly or annual goals and want weekly accountability
• Use this when you manage OKRs and want automated progress measurement
• Use this when you need trajectory predictions to catch off-track goals early
• Consider alternatives when you need daily task tracking (use daily-habit-scorecard)

Quick Start

Copy
# Minimal configuration - goal-progress.yml
skill: weekly-goal-progress-pulse
schedule: "sunday-18:00"
goals:
  - name: "Ship V2 product launch"
    type: quarterly
    deadline: "2026-03-31"
    key_results:
      - metric: "Features completed"
        target: 12
        current: 8
        source: linear
      - metric: "Beta users onboarded"
        target: 100
        current: 67

Copy
claude /weekly-goal-progress-pulse

Expected Output

GOAL PROGRESS PULSE - Week ending March 15, 2026
Q1 2026: 16 days remaining | 82% of quarter elapsed

GOAL 1: Ship V2 Product Launch (Q1 - March 31)
  Overall: 62% complete | Status: AT RISK

  KR1: Features completed: 8/12 (67%)
    [================--------] 67% done, 82% of time elapsed
    Trajectory: At current pace, 10/12 by March 31 (MISS by 2)
    Needed: 2 features/week for remaining 2.3 weeks

  KR2: Beta users onboarded: 67/100 (67%)
    [================--------] 67% done
    Trajectory: 89/100 by March 31 (MISS by 11)
...

Advanced Configuration

Platform-Specific Setup

Linear Project Tracking

Copy
sources:
  linear:
    api_key_env: "LINEAR_API_KEY"
    team_id: "your-team-id"
    map_to_goals:
      "Ship V2 product launch":
        project_id: "project-uuid"
        metric: "completed_issues"

Full Options Reference

Parameter	Type	Default	Description
schedule	string	"sunday-18:00"	Weekly pulse delivery time
goals	array	required	Goal definitions with key results
sources	object	{}	External data source integrations
review_period	string	"weekly"	Review frequency: weekly, biweekly
trajectory_method	string	"linear"	Projection: linear, weighted-recent, exponential
confidence_tracking	boolean	true	Ask for subjective confidence rating

Core Concepts

Concept	Purpose	How It Works
Trajectory Projection	Predicts end-state from current pace	Linear extrapolation from weekly progress rate to deadline date
Gap Analysis	Quantifies the distance to close	Calculates required weekly pace vs actual weekly pace for each key result
Risk Classification	Early warning system for goals	Marks goals as ON TRACK (>90% trajectory), TIGHT (80-90%), or AT RISK (<80%)
Course Correction	Actionable recovery suggestions	Generates specific tactics to close gaps based on remaining time and resources

Architecture

Goal Config ──────> Goal Parser ──────> Key Result Tracker ──> Trajectory Calculator
                                                |                        |
  Linear/Jira API ──> Progress Fetcher ─────────┘                  Gap Analyzer

Workflow Examples

Scenario 1: Q1 final push with 2 weeks remaining

Input: 3 quarterly goals, 2 on track, 1 at risk with 16 days left Processing: Calculates exact daily/weekly effort needed for each at-risk key result. Identifies which key results are mathematically achievable and which may need target adjustment. Suggests priority stack-ranking. Output: "Final sprint plan" showing daily targets for the remaining 16 days, with specific recommendations on which key results to push hard on and which to negotiate a target reduction with your manager.

Scenario 2: Annual goal mid-year check-in

Input: 5 annual goals at week 26 (50% mark), running --mid-year-review Processing: Compares 50% time elapsed vs actual progress percentage for each goal. Identifies goals significantly ahead or behind the 50% mark. Projects year-end status with confidence intervals. Output: Mid-year report card with each goal rated green/yellow/red, projected year-end status, and recommendations for H2 priority adjustments.

Best Practices

1. Update key result numbers before running the pulse -- The skill can auto-pull from Linear/Jira, but manual key results need weekly updates. Spend 5 minutes updating current values.

2. Pay attention to velocity trends, not just progress -- A goal at 60% with accelerating velocity is healthier than one at 70% with decelerating velocity. The velocity indicator tells.

3. Act on course corrections within 48 hours -- The Sunday pulse gives you corrections to implement Monday. If you wait until mid-week, you lose half the benefit. Review on.

Common Issues

1. Linear/Jira data not matching expected progress -- Verify the mapping between your goal's key result and the project/epic in your tool. Ensure the status filter matches your.

2. Trajectory prediction seems unrealistic -- The default linear projection assumes constant pace. If your work is back-loaded (e.g., documentation after coding), switch.

Privacy & Data Handling

Goal data and progress metrics are stored locally in ~/.claude/data/goal-progress/. No goal names, key results, or progress data is transmitted to external services beyond the project management APIs you configure. The skill requests read-only access to Linear, Jira, and other platforms. Shareable reports are generated locally and you control distribution.