status-report

Generate weekly status reports for 8090 client projects from project notes and prior reports.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/8090-inc/8090-claude-skills --skill status-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: status-report
Source: https://github.com/8090-inc/8090-claude-skills/tree/main/.claude/skills/status-report
Command: npx skills add https://github.com/8090-inc/8090-claude-skills --skill status-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of weekly status reports for 8090 project management teams, saving project managers hours by compiling context from project files, meeting notes, deadlines, and blockers into a standardized report format.

Core Features & Use Cases

  • Automated Context Gathering: Locates the previous week's report and relevant meeting notes to build a coherent, up-to-date update.
  • Structured Output: Produces the status report in a consistent, executive-friendly format including phase, deadlines, blockers, notes, and team allocation.
  • Use Case: When asked to "generate weekly status" or "prepare this week's project status," it assembles a comprehensive update for stakeholders with minimal manual digging.

Quick Start

Generate this week's status report for the current project using the latest project notes and the previous 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 project teams?

Automate weekly status reports by gathering context from project folders, meeting notes, and development logs into a standardized format. The Skill compiles deadlines, blockers, work completed, and next steps into a ready-to-distribute document, eliminating manual assembly time.

What information should I organize before generating a status report?

Collect the previous week's report, current meeting notes, project deadlines, identified blockers, development logs, and team allocation data. The Skill uses these inputs to build a coherent weekly update with risk-leveled blockers and structured sections for Notes, Work This Week, and Next Steps.

Can status report automation follow a specific project format?

Yes, the Skill applies project-specific status report formats and computes cumulative delays while populating all required sections including phase, deadlines, blockers, and Software Factory Usage. It produces standardized output that matches your team's reporting structure.

What makes automated status reports better than manual compilation?

Automated status reporting extracts context from multiple sources—meeting notes, development logs, prior reports—and structures it into an executive-friendly format with risk-level blockers. This reduces hours of manual digging and ensures consistency across weekly updates.

When should I use automated status reports instead of manual updates?

Use automated status reports when you manage multiple projects and need weekly stakeholder updates. The Skill works best when previous reports and meeting notes exist, enabling it to build cumulative context and identify recurring blockers without manual data entry.