skills.rest
tomzx
tomzxCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

start-week

Automate ISO week planning with theme, outcomes, and carryover.

5|Updated Jul 25, 2025
Search Tags:#goals#team-collaboration#carryover#planning-automation#weekly-planning#iso-week
One-click install
npx skills add https://github.com/tomzx/agents --skill start-week
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: start-week
Source: https://github.com/tomzx/agents/tree/main/skills/start-week
Command: npx skills add https://github.com/tomzx/agents --skill start-week

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates weekly planning by setting a theme, defining outcomes, and handling carryover from the previous week.

Core Features & Use Cases

  • Synthesize the week's context from prior week, goals, and current week context to produce a concise plan including the theme, top outcomes, carryover, collaboration needs, and risks.
  • Provide an optional file output at {BASE_DIR}/{YEAR}/weekly/{WEEK}/plan.md to persist the plan.

Quick Start

Start the skill to generate your Week plan for the current ISO week.

Frequently Asked Questions about start-week

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

FAQPage Schema
How do I automate weekly planning to align my team and track carryover?▼

Weekly planning automation establishes a theme, defines top outcomes, and captures carryover from the previous week to align the team. It synthesizes prior summaries and current goals to produce a concise plan covering collaboration needs and risks.

What inputs do I need to set up a weekly plan with carryover and outcomes?▼

Weekly planning requires the environment to supply BASE_DIR, TODAY, YEAR, and WEEK variables. It optionally reads existing context from goals.md, team-goals.md, and the previous week's plan.md to synthesize the current schedule.

Can I persist my weekly plan as a markdown file for future reference?▼

Yes, weekly planning can output an optional persisted plan.md file. This file is saved at the specified BASE_DIR path under the current YEAR and WEEK directory structure for future reference.

How does the ISO week date format affect weekly planning automation?▼

ISO week formatting standardizes the weekly planning cycle by determining the YEAR and WEEK variables. This ensures the automation correctly retrieves previous carryover and saves the new plan in the proper directory.

What is the best way to surface collaboration needs and risks during team planning?▼

Surfacing collaboration needs and risks during team planning is handled by synthesizing the week's context from prior summaries and current goals. The automation generates a structured plan that explicitly highlights these areas.

Related Skills

Explore More Product & Management Skills→
tomzxtomzx
5

end-of-day-review

Write a dated end-of-day review file with goals and next steps.

Community
Intermediate
aeoncity-demoaeoncity-demo

Idea Capture

Capture and categorize ideas sent via Telegram into Projects, Areas, Resources, or Archives.

Community
Basic
reubenjohnreubenjohn

goal-check

Analyze long-term goal progress and generate a structured weekly review.

Community
Intermediate
heyitsnoahheyitsnoah
2.6k

weekly-synthesis

Aggregate weekly activity across notes, tasks, and projects into a structured synthesis.

Community
Advanced