status-report

Generate a Project+ style weekly status report as a .docx file.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/kenmulford/PMSkills --skill status-report-kenmulford
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status-report
Source: https://github.com/kenmulford/PMSkills/tree/main/skills/status-report
Command: npx skills add https://github.com/kenmulford/PMSkills --skill status-report-kenmulford

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python-docx, and includes scripts (resource) components.

What problem does it solve?

Inconsistent weekly project updates slow decision making and inflate risk of miscommunication. This skill standardizes status reports by enforcing a fixed structure and guardrails so stakeholders can read the same sections in the same order each week, while preserving user-provided data.

Core Features & Use Cases

  • Fixed section order: Executive Summary, RAG with trend, Metrics, Accomplishments, Upcoming, Risks, Issues, Asks, Dependencies.
  • Deterministic rendering: outputs a .docx artifact with consistent styling and guardrails that prevent invented content.
  • Use cases: weekly status for steering committees, governance reviews, stakeholder updates, and light governance artifacts.

Quick Start

Describe your project situation in plain language and run the script to render a fixed-format status report.

Frequently Asked Questions about status-report

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

FAQPage Schema
How do I automate weekly status report generation for stakeholders?

Weekly status report generation is automated by processing user-provided project context through a fixed section order, yielding a consistently styled .docx artifact. It enforces a never-invent discipline to ensure deterministic rendering of executive summaries, RAG trends, metrics, risks, and asks.

What is the best way to standardize project management reporting for steering committees?

Standardizing project management reporting involves enforcing a fixed structure containing executive summaries, RAG status, and dependencies. This approach prevents miscommunication by ensuring stakeholders read the same sections in the same order each week while preserving original user-provided data.

Can I generate a .docx status report with RAG trends and risk sections from plain text?

Yes, generating a .docx status report with RAG trends and risk sections is possible by providing plain language project context. The deterministic rendering script maps the input into a fixed-format document containing accomplishments, upcoming tasks, issues, asks, and dependencies.

Does this status report automation require python-docx to output governance artifacts?

Yes, status report automation requires the python-docx dependency to output .docx governance artifacts. The script component relies on this library to apply consistent document styling and render the fixed section order required for steering committee reviews.

How to prevent invented content when automating project status updates?

Preventing invented content during project status update automation is achieved through strict never-invent discipline. The skill requires explicit input data for all metrics and accomplishments, ensuring the deterministic rendering only includes user-provided context without hallucinated information.

What limitations exist when using deterministic rendering for weekly project updates?

Limitations of deterministic rendering for weekly project updates include the strict requirement for explicit input data. Because the never-invent discipline prevents generated content, the report quality directly depends on the completeness of the user-provided project context.