sd-status-update

Generates objective-oriented project status updates from supplied or connected work sources.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/platypeeps/sd-ai-command-pack --skill sd-status-update-platypeeps
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sd-status-update
Source: https://github.com/platypeeps/sd-ai-command-pack/tree/main/contrib/sd-status-update
Command: npx skills add https://github.com/platypeeps/sd-ai-command-pack --skill sd-status-update-platypeeps

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning scattered project evidence into a stakeholder-ready status update is slow and error-prone: activity gets mistaken for progress, stale sources get treated as current, and owners or dates get invented. This Skill produces a dated, evidence-backed report that ties completed outcomes to the project's objective and keeps unknowns visibly unknown. ## Core Features & Use Cases - Objective-anchored reporting: Classifies dated, attributable claims as outcomes, activity, current state, blockers, risks, decisions, asks, or next actions, and tests every claimed outcome against the stated objective. - Source auditing: Records each source's freshness, flags stale, inaccessible, or conflicting inputs, and reconciles disagreements using the rules in references/source-standards.md. - Baseline windows: Supports since=last-status to anchor the reporting window to the prior report's through-date, with explicit disclosure when the baseline is missing. - Use Case: A project lead asks for a weekly update on a product launch. The Skill inspects the linked task system, repository, and message threads, separates completed outcomes from mere activity, and delivers a forwardable report with blockers, asks, and source coverage gaps. ## Quick Start Ask the AI to generate a status update for your project since last-status using the supplied task board and repository links, for an executive audience.

Frequently Asked Questions about sd-status-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a project status update from my task board and repository?▼

Invoke the skill with project= and sources= pointing to your task system, repository, threads, or documents. It inspects each source, extracts dated claims, and produces a structured report with outcomes, blockers, decisions, asks, and next actions.

How to write a status update that shows progress instead of activity?▼

Anchor the report to a defined objective and test every claimed outcome against it. Commits, meetings, and task movement count as activity unless the evidence shows a changed state for the user, stakeholder, system, or delivery.

Can I set the reporting window to start from my last status report?▼

Yes, pass since=last-status and the skill locates the prior report and uses its through-date as the baseline. If the prior report is unavailable, it discloses the missing baseline and asks for an authorized replacement window.

Does the status update skill modify my project management tools?▼

No, the skill is strictly read-only. It never updates tasks, repositories, calendars, or files, and it never sends the report without a separate request and the relevant action capability.

When should I not use a project status update report?▼

Do not use it for recency briefs across standing topics, synthesis of a supplied document corpus, recommendations between options, or baseline change monitoring of an external subject. Those belong to sibling skills like sd-brief, sd-digest, sd-decide, and sd-monitor.

What happens when project sources disagree or are stale?▼

The skill shows each dated position with its source, applies the source standards in references/source-standards.md, and lowers confidence accordingly. It never picks the most convenient state or converts stale evidence into current status.