skills.rest
vitalwarley
vitalwarleyCOMMUNITY
Explore all skills by this author →
Website𝕏@vitalwarley_GitHub

weekly-planning

Compresses previous week outcomes and generates current week plans from project context, GitHub issues, and meeting notes.

Updated Aug 27, 2026
Search Tags:#changelog#github#project-management#sprint-planning#meeting-notes#resolution-map#weekly-planning
One-click install
npx skills add https://github.com/vitalwarley/hyprdots --skill weekly-planning-vitalwarley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: weekly-planning
Source: https://github.com/vitalwarley/hyprdots/tree/main/claude-global/skills/weekly-planning
Command: npx skills add https://github.com/vitalwarley/hyprdots --skill weekly-planning-vitalwarley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps sprint planning documents accurate, concise, and traceable by compressing the previous week's outcomes, resolving statuses, and producing a structured plan for the current week so teams and researchers stop working from stale or scattered sources.

Core Features & Use Cases

  • Source aggregation: reads project context files, meeting configs, dailies, weekly atas, GitHub issues, and recent comments to assemble a single view of status and work.
  • Resolution mapping and compression: builds a resolution map to avoid false blockers and turns last week's work into a compact table of outcomes and migrated items.
  • Plan generation and updates: writes or updates sprint planning docs with per-work-area tables, risk updates, changelog entries, and marked criteria, handling both team and research workflows.
  • Use case: a product manager uses it every Monday to convert accumulated dailies, weekly minutes, and issue state into a one-page planning update with decisions and migrated tasks.

Quick Start

Use the weekly-planning skill to update the project's sprint planning document for week-17 by reading project context and issue state and producing a compressed previous-week summary plus a detailed current-week plan.

Frequently Asked Questions about weekly-planning

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

FAQPage Schema
How do I automatically compress weekly sprint planning notes and GitHub issues into a summary?▼

Automatically compress weekly sprint planning notes by reading project context files, daily notes, meeting artifacts, and GitHub issues to generate a compact table of previous-week outcomes and a detailed current-week plan. This prevents teams from working with stale or scattered sources.

How does a resolution map work for sprint planning?▼

A resolution map works for sprint planning by analyzing previous week statuses and issue comments to resolve false blockers. It compresses last week's work into a compact table of outcomes and migrated items, ensuring sprint planning documents remain accurate and traceable.

Can I generate sprint planning documents from local meeting notes and GitHub CLI outputs?▼

Yes, you can generate sprint planning documents from local meeting notes and GitHub CLI outputs. The process reads these artifacts alongside project context files and issue lists to produce structured planning updates with per-work-area tables, risk updates, and changelog entries.

What is the best way to update a sprint planning document with migrated tasks and risk updates?▼

The best way to update a sprint planning document with migrated tasks and risk updates is to aggregate weekly atas, dailies, and issue states. This converts accumulated project context into a one-page planning update with decisions, marked criteria, and structured section updates.

Does sprint planning compression work for both team workflows and research workflows?▼

Yes, sprint planning compression works for both team workflows and research workflows. It reads project context files and issue state to produce a compressed previous-week summary and detailed current-week plan, handling per-work-area tables and changelog entries for either context.

Why are my sprint planning documents stale and how do I fix traceability?▼

Sprint planning documents become stale when accumulated dailies, weekly minutes, and issue states are not compressed into a single view. Fix traceability by applying resolution mapping and structured section updates to generate planning documents that preserve changelog entries and marked criteria.

Related Skills

Explore More Product & Management Skills→
shysssthanhtrishysssthanhtri

breakdown-plan

Generate GitHub project plans and issue checklists from product artifacts.

Community
Advanced
mzniumzniu
7

stakeholder_analysis

Identify and map project stakeholders by power, interest, attitude, and influence.

Community
Advanced
jingsongliujingjingsongliujing
76

lark-workflow-meeting-summary

Automate collection and structured summarization of meeting minutes within a time window.

Community
Advanced
SuniljitSuniljit

project-timeline

Convert weekly goals into a Markdown sprint-grid with status markers.

Community
Advanced