pm-weekly-update

Draft weekly stakeholder updates from git activity and roadmap status.

42|2|Updated Mar 28, 2026

Search Tags:#roadmap #transparency #history #update #team #stakeholders #weekly

Ready to run

npx skills add https://github.com/nmrtn/nanopm --skill pm-weekly-update

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm-weekly-update
Source: https://github.com/nmrtn/nanopm/tree/main/pm-weekly-update
Command: npx skills add https://github.com/nmrtn/nanopm --skill pm-weekly-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly progress updates are time-consuming and prone to bias. This skill drafts a clear, honest status email for managers, executives, investors, or teammates by assembling shipped work, slippage, and strategic changes and by adapting tone to the audience.

Core Features & Use Cases

Automates the creation of weekly updates by summarizing what shipped, what slipped, and what changed strategically.
Tailors tone and content for different stakeholders (manager, CEO, investor, dev team) and appends to a persistent history for continuity.
Saves the draft to a reusable artifact at .nanopm/WEEKLY_UPDATE.md and maintains a weekly history log.

Quick Start

Run /pm-weekly-update at the end of your work week to generate the weekly update draft.

Frequently Asked Questions about pm-weekly-update

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

FAQPage Schema

How do I automate weekly stakeholder updates from git activity?▼

Tailor weekly stakeholder updates by adjusting tone and content for specific audiences like managers, executives, investors, or development teams. The generated report adapts its language to suit the target reader while maintaining honest progress tracking.

How to generate a weekly progress report that includes shipped work and slippage?▼

Maintain weekly history continuity by appending each generated stakeholder update to a persistent log. This creates a historical record of shipped work, slippage, and strategic changes for future reference and accountability.

Can I tailor the tone of a weekly update for different audiences like investors or dev teams?▼

No external dependencies are required to generate weekly stakeholder updates. The workflow operates independently to gather git activity and roadmap status, producing a markdown file and updating the history log without additional packages.

Do I need any dependencies to generate weekly team updates?▼

Generate weekly stakeholder updates by running the command at the end of your work week. This triggers the workflow to draft a status report covering shipped work, slippage, and strategic changes, saving it to a markdown file.

What is the best way to keep a persistent history of weekly project updates?▼

Create weekly stakeholder updates by running a single command at the end of your work week. This initiates an end-to-end workflow that drafts an honest status report and saves it as a markdown artifact.