Overview

Create and update structured project status reports from meetings, messages, and documents. Extracts status updates into markdown reports with summary, problems, risks, and actions sections. Supports single-team, compiled, and multi-team report formats.

Getting Started

Add your source materials to the project workspace, then activate the Project Status Reports skill. The agent will guide you through the process step by step.

Example Conversation

You: Create a status report for the Platform team from these Slack updates and the standup notes I’ve pasted.

Agent: I’ve read the Slack thread and standup notes. I’ll structure a single-team status report. Which team name should I use for the report title and file name — “Platform” or something else? And should I infer RAG status (on track / risk-concern / problem) from the content, or do you want to set it explicitly?

You: Use “Platform”. Infer RAG from the content.

Agent: I’ve created platform-status-report-2024-10-15.md with your projects: API v2 (in progress, on track), Dashboard (in progress, risk-concern — design dependency), and Auth migration (scheduled). Each section has summary, on-track bullets, problems, risks, and actions from the sources. I didn’t add anything that wasn’t in your inputs. Want to add or change any project or move something to Done?

Sample Output Excerpt

Below is a representative excerpt from a single-team project status report.

tags:

• work/report created_at: 2024-10-15 updated_at: 2024-10-15 type: note

Platform - Status Report - 2024-10-15

This document shares work status from Platform as of 15-10-2024.

API v2

• status: in progress
• rag status: on track

API v2 spec is done; first endpoints are in development. Backend and frontend agreed on contract; staging will be ready by end of week.

On track:

• Spec and contract: Signed off; implementation started.
• Staging: On track for Friday.

Problems:

• None.

Risks and Concerns:

• Design dependency for docs portal: If design slips, we can still ship API; only the docs site would move.

Actions:

• Deploy to staging by Friday.
• Update API changelog.

Links, assets, references:

• [Spec link]

Dashboard v2

• status: in progress
• rag status: risk-concern

Dashboard v2 is in progress. Tables and filters are done; export is in QA. Onboarding flow is blocked on final design.

On track:

• Tables and filters: Done.
• Export: In QA.

Problems:

• Onboarding flow: Blocked on final design; Design ETA Friday.

Risks and Concerns:

• If design is late, onboarding slips to next sprint.

Actions:

• Design: deliver onboarding mocks by Friday.
• Eng: start with wireframes if needed.