weekly-goals

Read weekly goals from docs/plans and surface P0-P2 priorities.

4|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/markhazlett/agent-harness --skill weekly-goals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weekly-goals
Source: https://github.com/markhazlett/agent-harness/tree/main/.claude/skills/weekly-goals
Command: npx skills add https://github.com/markhazlett/agent-harness --skill weekly-goals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Load and reference the current week's goals to keep work aligned with weekly priorities, flag when tasks drift off-track, and suggest what to work on next.

Core Features & Use Cases

  • Surface the North Star, current priorities (P0 -> P1 -> P2), and What's NOT This Week boundaries to guide work.
  • Map tasks to the demo script scenes and enforce sprint plan awareness, enabling plan / plan-sprint flow.
  • Track progress by prompting to update goals docs as tasks complete and maintain guardrails and scope.

Quick Start

Load the current week's goals and present the North Star, current priorities, and recommended next steps.

Frequently Asked Questions about weekly-goals

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

FAQPage Schema
How do I track weekly goals and keep sprint priorities aligned?

Weekly goal tracking is handled by surfacing your current priorities and prompting you to update the goals document as tasks complete, keeping sprint work aligned with the North Star.

What's the best way to enforce sprint scope and prevent task drift?

Sprint scope enforcement works by reading the weekly goals file under docs/plans, surfacing P0 to P2 priorities, and maintaining guardrails that flag when tasks drift off-track.

How do I map sprint tasks to a demo script for weekly planning?

Mapping tasks to demo script scenes is done by reading the weekly goals document, linking each priority to its corresponding demo scene, and suggesting the next steps for the plan-sprint flow.

Can I use weekly goal tracking for prioritizing what to work on next?

Weekly goal tracking supports next-step prioritization by surfacing P0, P1, and P2 priorities from the docs/plans layout and recommending what to work on next based on current progress.

Does weekly goal tracking require a specific file layout for sprint planning?

Weekly goal tracking requires a goals file located under the docs/plans directory to surface North Star priorities, sprint boundaries, and what is explicitly out of scope for the week.

How does weekly goal tracking handle boundaries for what is not in scope?

Weekly goal tracking manages scope boundaries by surfacing a What's NOT This Week section from the goals document, ensuring work stays within the defined sprint guardrails.