Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From astravue
Generates executive status reports from Astravue data covering task progress, budget consumption, and project health.
npx claudepluginhub astravueorg/astravue-mcp-server --plugin astravueHow this skill is triggered — by the user, by Claude, or both
Slash command
/astravue:generating-status-reportThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. **Identify scope**
Generates a project status report by reading artifacts (charter, backlog, sprint plan, WBS), calculating metrics, identifying blockers, and summarizing progress with RAG indicators. Use at end of sprint or for stakeholder updates.
Generates client-facing project heartbeat/status update messages for Kanopi projects by pulling activity from Teamwork and Fathom, then drafting in a consistent voice and format.
Tracks time on tasks with timers or manual entries and generates timesheet reports. Use when logging hours, starting/stopping timers, or asking 'how much time was spent?'
Share bugs, ideas, or general feedback.
Identify scope
Clarify which project and audience (executive vs team). Use astravue_list_projects to help select.
Collect data
astravue_get_project — status, health, priority, dates, budget fieldsastravue_internal_get_project_stats — task completion metricsastravue_list_overdue_tasks — overdue count and detailsastravue_get_project_time_summary — billable vs non-billable hoursWrite the report in narrative paragraphs
Cover four sections:
Project Overview — status, health, completion %, whether on schedule.
Task Progress — total, completed, pending, overdue. Use plain language.
Budget — allocated vs spent, billable vs non-billable, remaining. Compare budget consumption % to completion %.
Risks — overdue tasks, budget concerns, schedule slippage.
Present to user
Ask if they want adjustments or more detail on any section.