initiative-status-report

Generates weekly status reports for active initiatives with progress, blockers, risks, and KPIs.

2|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/jupes/agent-forge-harness --skill initiative-status-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: initiative-status-report
Source: https://github.com/jupes/agent-forge-harness/tree/main/.claude/skills/initiative-status-report
Command: npx skills add https://github.com/jupes/agent-forge-harness --skill initiative-status-report

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the generation of comprehensive weekly status reports, saving time and ensuring consistency in reporting for initiatives.

Core Features & Use Cases

  • Automated Reporting: Generates structured reports with status, progress, blockers, risks, and KPIs.
  • Weekly Reporting: Designed for team updates, stakeholder meetings, and sprint reviews.
  • Use Case: With a simple command, obtain a detailed weekly report that covers all active epics, including their status, progress, and key metrics.

Quick Start

Generate a weekly status report for all active epics using the command: initiative-status-report.

Frequently Asked Questions about initiative-status-report

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

FAQPage Schema
How do I automate weekly status reporting for active initiatives?

Automate weekly status reporting by extracting progress, blockers, risks, and KPIs from issue tracking systems and version control logs to generate structured Markdown reports for active epics.

What's the best way to generate project tracking reports that cover blockers and KPIs?

Generate project tracking reports by pulling data from issue trackers and version control logs to compile initiative progress, blockers, risks, and KPIs into a structured Markdown format.

Can I use initiative reporting with my existing issue tracking systems and version control logs?

Initiative reporting requires interaction with issue tracking systems and version control logs to extract the necessary data for generating comprehensive weekly status reports.

Does weekly status reporting require manual input for team collaboration updates?

Weekly status reporting requires a simple command to automatically generate detailed reports covering active epics, their status, progress, and key metrics for team updates and sprint reviews.

What format does automated initiative reporting output for stakeholder meetings?

Automated initiative reporting outputs Markdown formatted files containing structured progress, blockers, risks, and KPIs for use in stakeholder meetings and sprint reviews.

What should I do if weekly status report generation is not extracting issue tracking data correctly?

If weekly status report generation is not working, verify that the issue tracking systems and version control logs are accessible and properly integrated for extracting initiative progress and KPI data.