What problem does it solve? Long-running engineering work produces status updates that are either too vague to act on or too long to read. This Skill enforces a fixed report shape — one objective line, three to six key results scored against declared thresholds, the blocker, and what is needed from the reader — so a busy human can grasp where work stands in ten seconds while all evidence stays available below a divider. ## Core Features & Use Cases - Capped report head: The human-readable section is limited to 14 lines and 900 characters, with uncapped evidence (actions, omissions, provenance) placed below a --- rule. - Three-status scoring: Key results are marked achieved, missed, or unmeasured, with a strict rule that unverified claims can never be marked achieved. - Comparable reporting: Key results are reused from the work's acceptance criteria and re-scored each report, making two reports on the same work directly comparable. - Use Case: An agent running a multi-session refactoring initiative reports progress at each milestone: the reader sees the objective, which thresholds were met or missed, the current blocker, and exactly what decision is needed — without reading the full evidence log. ## Quick Start Use the state skill to report where this work stands, with one objective line, key results scored against their thresholds, the blocker, and what you need from me.