skills.rest
Kohlex
KohlexOFFICIAL
Explore all skills by this author →
WebsiteGitHub

stakeholder-status-generator

Generate STATUS.md and STATUS-TODAY.md from capabilities.yaml and Git history.

Updated Jun 4, 2026
Search Tags:#automation#git#documentation#status#capabilities#stakeholders
One-click install
npx skills add https://github.com/Kohlex/autopilot-plugin --skill stakeholder-status-generator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stakeholder-status-generator
Source: https://github.com/Kohlex/autopilot-plugin/tree/main/skills/stakeholder-status-generator
Command: npx skills add https://github.com/Kohlex/autopilot-plugin --skill stakeholder-status-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps stakeholders informed with up-to-date product health by turning capability data and merge history into readable reports.

Core Features & Use Cases

  • Generates STATUS.md as a running, consolidated timeline of merged capabilities.
  • Generates STATUS-TODAY.md for morning briefings with yesterday's changes and current blockers.
  • Supports multi-product usage by reading .planning/<product>/capabilities.yaml and the main Git history.
  • Incorporates escalation logs to surface blockers and dependencies impacting delivery.

Quick Start

Regenerate STATUS.md and STATUS-TODAY.md for a product by running stakeholder-status-generator <product>.

Frequently Asked Questions about stakeholder-status-generator

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

FAQPage Schema
How do I automate stakeholder status reports from Git history?▼

Automate stakeholder status reports by reading capability data and Git merge history to generate readable documents. The tool consolidates merged capabilities into a running timeline and extracts yesterday's changes for morning briefings.

Can I generate morning status briefings from capabilities.yaml and git log?▼

Yes, you can generate morning status briefings by parsing capabilities.yaml and git log. The process creates a STATUS-TODAY.md file that highlights yesterday's merged changes and current blockers for daily stakeholder updates.

Does stakeholder status generation work for multiple products?▼

Stakeholder status generation supports multi-product usage by reading .planning/<product>/capabilities.yaml and the main Git history. You can regenerate STATUS.md and STATUS-TODAY.md for any specific product by targeting its name.

What is the best way to keep stakeholders informed of product health and blockers?▼

The best way to keep stakeholders informed is turning capability data and merge history into readable reports. This approach incorporates escalation logs to surface blockers and dependencies impacting delivery in both running and daily formats.

How do I surface stale-status discrepancies for operator review?▼

Surface stale-status discrepancies for operator review by cross-referencing canonical sources like capabilities.yaml, git log, and escalation logs. The generation process detects inconsistencies between these inputs and flags them for manual inspection.

Related Skills

Explore More Product & Management Skills→
KohlexKohlex

stakeholder-risks-generator

Aggregate risk signals from YAML, JSON logs, and architecture notes into a deduplicated RISKS.md register.

Official
Advanced
ronnycodingronnycoding
12

daily-briefing

Aggregate calendar events, email inbox status, and reminders into a structured daily briefing.

Community
Intermediate
KiloforgeKiloforge
2

kf-conflict-resolver

Resolve git merge conflicts during push or pull sync operations.

Official
Advanced
cyberpunk042cyberpunk042

pm-status-report

Generate project status reports from git history, tasks, and metrics.

Community
Intermediate