What problem does it solve? After updating a project's status.md file, it is easy for stale items, mixed facts and guesses, or formatting drift to creep in. This Skill performs a dedicated quality review of a project's status.md so the document stays readable and consistent for the next update cycle. ## Core Features & Use Cases - Structured Quality Review: Checks that sections like overview, current status, blockers, open questions, next observations, sources, and change history match the standard status.md template and the projects/README.md update rules. - Content Hygiene Checks: Detects decided or completed items still listed as open, facts mixed with speculation, pasted raw logs, relative dates, and non-relinkable sources such as pasted conversation summaries. - Safe In-Place Fixes: Applies safe corrections directly (formatting, moving stale items, removing linkless sources) while leaving judgment calls in a "points needing confirmation" section instead of guessing. - Use Case: After updating a project's status.md from the week's Slack and Linear activity, run this review to confirm the file still follows the vault's format, that the sources section only contains link-backed references, and that the change history records only what actually changed. ## Quick Start Use the review-project-status skill to review the status.md of my current project folder and report any fixes or points needing confirmation.
