status-update

Generate stakeholder-friendly project status reports from markdown files.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/alexwox/genesis-template --skill status-update-alexwox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status-update
Source: https://github.com/alexwox/genesis-template/tree/main/.cursor/skills/status-update
Command: npx skills add https://github.com/alexwox/genesis-template --skill status-update-alexwox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Builds stakeholder-friendly project status updates from markdown sources, turning technical details into clear, business-oriented progress reports.

Core Features & Use Cases

  • Generate concise status updates from project markdowns (README.md, notes.md, docs/**/*.md, architecture.md) for executives and non-technical stakeholders.
  • Summarize progress, upcoming milestones, risks, decisions, and UI/infrastructure implications in plain language.
  • Use Case: When a stakeholder asks for "what is done vs what remains," or a roadmap update, produce a ready-to-share report.

Quick Start

Summarize the current project status from the latest markdown files for a stakeholder update.

Frequently Asked Questions about status-update

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

FAQPage Schema
How do I generate stakeholder status updates from markdown files?

Generate project status updates from markdown files by analyzing sources like README.md, notes.md, and architecture.md to produce structured, business-oriented progress reports. It extracts technical details and converts them into plain language summaries of progress, milestones, and risks.

What is the best way to summarize project progress for non-technical stakeholders?

Summarize project progress for non-technical stakeholders by translating technical markdown documentation into clear, business-oriented reports. This process extracts details on UI/UX flows, infrastructure, code smells, and future plans, presenting them in a ready-to-share format.

Can I use this to summarize implementation status and risks from existing documentation?

You can summarize implementation status and risks from existing markdown documentation by processing files like docs/**/*.md. It identifies current progress, upcoming milestones, and potential risks, formatting them into a comprehensive project update for stakeholders.

Does this work with standard markdown documentation like README and architecture files?

It works with standard markdown documentation by parsing files such as README.md, notes.md, architecture.md, and docs/**/*.md. The tool reads these sources to identify project progress, decisions, and infrastructure summaries for stakeholder communication.

How do I create a roadmap update when stakeholders ask what is done vs what remains?

Create a roadmap update by processing your markdown documentation to distinguish completed tasks from remaining work. It analyzes technical notes and architecture files to deliver a clear, structured summary of current status and future plans for stakeholders.