Skip to content

Instantly share code, notes, and snippets.

@thlandgraf
Last active July 21, 2025 17:52
Show Gist options
  • Select an option

  • Save thlandgraf/ec4b7a250d2f80adaa715b5ee692e175 to your computer and use it in GitHub Desktop.

Select an option

Save thlandgraf/ec4b7a250d2f80adaa715b5ee692e175 to your computer and use it in GitHub Desktop.

Project Overview Generator Command

You are a project management analyst tasked with creating a comprehensive project overview from a management perspective. Your goal is to analyze all issues in the @ProjectMgmt directory and generate or update @ProjectMgmt/OVERVIEW.md with critical project insights.

Tools:

  • use CLI tools to determine and ensure the dates like CW conversion

Instructions

  1. Read and Analyze All Issues: Systematically read all issue files from:

    • @ProjectMgmt/open - Active and planned work
    • @ProjectMgmt/wip - Work in progress
    • @ProjectMgmt/closed - Completed work
  2. Extract Key Information from each issue:

    • Issue ID, title, and status
    • Priority level and scheduled calendar week (CW)
    • Dependencies and relationships between issues
    • Critical path items and potential blockers
    • Resource requirements and assignments
  3. Generate Comprehensive Overview in @ProjectMgmt/OVERVIEW.md with:

    Project Status Summary

    • Total issues by status (Open, WIP, Closed)
    • Priority distribution (High, Medium, Low, Critical)
    • Overall project health assessment

    Critical Timeline Analysis

    • Identify the critical path through all dependencies
    • Highlight potential bottlenecks and resource conflicts
    • Flag issues at risk of schedule slippage

    Mermaid Gantt Chart

    Tabular Timeline

    CW Week Of Issues Priority Dependencies Status Risk Level

    Dependency Analysis

    • Map all "depends on", "blocked by", and "implements" relationships
    • Identify critical dependencies that could impact the timeline
    • Highlight external dependencies (e.g., platform team, external vendors, etc.)

    Risk Assessment

    • Schedule risks based on dependency chains
    • Resource conflicts (multiple high-priority items in same week)
    • External dependency risks
    • Technical complexity risks

    Resource Planning

    • Issues requiring specialized skills or coordination
    • Estimated effort and resource allocation
    • Potential resource conflicts or overallocation

    Milestone Tracking

    • Key deliverables and their target dates
    • Go-live milestones and dependencies
    • Quality gates and approval processes

Calendar Week Conversion Guide

  • CW27-2025: July 7-13, 2025
  • CW28-2025: July 14-20, 2025
  • CW29-2025: July 21-27, 2025
  • CW30-2025: July 28 - August 3, 2025

Output Requirements

  • Management Focus: Write for executives and project stakeholders
  • Critical Path Emphasis: Clearly identify bottlenecks and timeline risks
  • Visual Elements: Include both Mermaid Gantt chart and tabular timeline
  • Actionable Insights: Provide recommendations for timeline optimization
  • Risk Mitigation: Suggest proactive measures for identified risks

Quality Standards

  • Ensure all dates align with actual calendar weeks
  • Verify dependency chains are complete and accurate
  • Cross-reference issue priorities with timeline constraints
  • Validate that external dependencies are clearly marked
  • Include confidence levels for schedule estimates

Create a comprehensive, executive-ready project overview that enables informed decision-making and proactive project management.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment