Daily Project Status Digest

Skill files

The public post is only the explanation. Use these links to inspect or download the actual reviewed skill artifact.

skill.mdDownload SKILL.mdevalDownload evals.json

Skill Overview

Daily project reporting is repetitive, but it is also easy to get wrong. A useful PM update needs to compress messy inputs without hiding deadline risk, unclear ownership, or blocked decisions.

The daily-project-status-digest Codex skill gives the agent a structured workflow for turning raw standup notes, Slack excerpts, issue comments, task tracker exports, or meeting notes into a daily PM digest.

Intended Role

This skill is designed for Project Managers who manage cross-functional delivery work and need a reliable daily reporting rhythm.

Required Inputs

• Raw updates from the team, tools, or meeting notes.
• Project context such as milestone, target date, workstreams, stakeholders, or known priorities when available.
• Optional audience context, such as leadership, internal team, client, vendor, or cross-functional stakeholder update.

The skill can proceed with imperfect inputs. It labels missing owners, dates, and assumptions instead of inventing certainty.

Expected Output

The skill produces:

• Overall status with green, yellow, or red rationale.
• Executive summary focused on progress, risks, blockers, and decisions.
• Workstream table with owner, next step, and status.
• Blockers and risks with severity, impact, owner, due date, and escalation recommendation.
• Decisions needed with decision maker, deadline, and context.
• Short follow-up messages ready to send.
• Assumptions and gaps for facts the PM should confirm.

Validation Scenario

The included eval set checks three realistic PM situations:

• A leadership update for an analytics dashboard launch with dependency and staging-data blockers.
• A client migration update with go-live risk and unclear ownership.
• A mobile release channel update with launch-window pressure and missing Android release ownership.

The expected outputs verify that the skill surfaces deadline risk, assigns owners or marks gaps, separates facts from inference, and creates practical follow-up messages.

Operational Limits

This is a low-risk workflow skill. It does not access private project systems by itself, make schedule commitments, or send messages automatically. The PM should review any stakeholder-facing digest before posting it, especially when the update mentions customer impact, legal review, budget, compliance, or delivery-date changes.

Maintenance Expectations

Review this skill when the team’s project source systems, escalation rules, or stakeholder reporting format changes. The evals should also be refreshed when the team starts using a different release cadence, risk vocabulary, or owner model, because those details affect how the digest should classify blockers and follow-ups.

Related Existing Skills

These public skills and skill libraries are adjacent to this workflow. They are not airoweb artifacts, but they help readers compare what already exists before installing or adapting this skill.

• project-status on Smithery: an installable skill focused on checking or communicating project status.
• Digest command skill: a broader digest skill for recent activity, mentions, action items, decisions, and document updates across connected sources.
• Project Management for Claude Code: a broader project-management skill that covers task breakdown, PRDs, roadmap tracking, and project status.
• PM skills: a product-management skill library with reusable PM workflows and structured SKILL.md examples.