weekly-plan

Creates a weekly goal plan in a markdown doc bound to a live-feedback workspace.

Updated May 12, 2026
One-click install
npx skills add https://github.com/fryanpan/ai-team-lead --skill weekly-plan-fryanpan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: weekly-plan
Source: https://github.com/fryanpan/ai-team-lead/tree/main/.claude/skills/weekly-plan
Command: npx skills add https://github.com/fryanpan/ai-team-lead --skill weekly-plan-fryanpan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Weekly planning across multiple agent-run projects tends to produce bloated, stale documents that nobody reads. This Skill sets the week's goals with the user in a single lean markdown doc bound to the Team Lead live-feedback workspace, carrying over unfinished work, deriving capacity from the user's calendars, and keeping every goal to a strict format. ## Core Features & Use Cases - Carry-over and candidate goal surfacing: Pulls unfinished goals from last week's plan, open PRs across the fleet, peer summaries, and workspace board items into prioritized candidate lists. - Calendar-derived capacity block: Reads the user's personal, work, and family calendars, subtracts accepted meetings inside 9am-5pm from a 7h weekday baseline, and compares committed hours against both capacity and last week's planned total. - Structured goal format with hard length limits: Each goal carries a measurable title with estimate, Due and Lead lines, at most 5 key outcomes, and a body capped at 10 lines, with no Value block or explanatory text. - Workspace board mirroring: After user confirmation, mirrors committed goals as bands and tasks on the workspace board and notifies owning peer agents via claude-hive messages. - Use Case: On Monday morning, ask the Team Lead to plan the week; it reads your three calendars, proposes carry-over and new goals with hour estimates, you tag each as commit, drop, or defer, and the confirmed plan lands on the workspace board with tasks assigned to the fleet. ## Quick Start Ask the Team Lead agent to run the weekly plan for this week and review the candidate goals it proposes against your calendar capacity.

Frequently Asked Questions about weekly-plan

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

FAQPage Schema
How do I set up a weekly plan with an AI agent team?▼

Invoke the weekly-plan skill on Sunday or Monday. It pulls carry-over goals from last week's doc, surfaces new candidates from open PRs and peer summaries, derives your available hours from your calendars, and lets you commit, drop, or defer each goal before finalizing.

How does the weekly plan estimate my available hours?▼

It reads your personal, work, and family calendars for Monday through Sunday, starts from a 7-hour weekday baseline, and subtracts one hour for each accepted meeting between 9am and 5pm. Weekends default to 2 hours, and travel or all-day events zero out the day.

Does the weekly plan sync to Notion or Asana?▼

No. The plan lives as a markdown doc bound to the Team Lead live-feedback workspace, and committed goals are mirrored onto the workspace board as goal bands and tasks. Notion and Asana syncs were explicitly removed to avoid duplicate surfaces.

What format does each weekly goal follow?▼

Each goal has a title with the outcome, rationale, and hour estimate, plus separate Due and Lead bullets, an optional one-line Constraint, and at most five key outcomes. The whole goal body is capped at 10 lines with no Value block or explanatory text.

Why should I not edit the weekly plan markdown file directly?▼

Once the doc is bound to the workspace, direct file writes race the live-feedback flush and get silently overwritten. All later edits must go through the live-feedback edit tools such as find_and_replace or anchor-based block operations.