What problem does it solve? Project status updates drift toward narrative: milestones get reported as "almost done" without proof, and stalls stay hidden until they block decisions. This Skill produces status briefs that separate claimed progress from evidenced progress, so every status line rests on a verifiable artifact. ## Core Features & Use Cases - Claimed-vs-evidenced split: Every milestone is marked claimed (words only) or evidenced (demo link, passing check, merged change, log excerpt), with the artifact named or its absence stated. - Delta tracking: Against a previous brief, each milestone is classified as moved, reworded, or stalled, exposing reworded status that hides a lack of progress. - Unreachable-source handling: Sources requiring sign-in or unavailable systems are recorded as unreachable with a note on what access would settle them, never inferred from chatter. - Use Case: Before a milestone review meeting, ask for a status brief on a Grok Build project and receive a markdown table showing which milestones have real evidence, what moved since the last check, and the sharpest risk blocking the next decision. ## Quick Start Track the Grok Build project at this link and produce a status brief showing which milestones are claimed versus evidenced.
