repo-status-skill

Repository state estimation assesses baseline, branches, governance signals, and milestone context using standard repo-level artifacts. You need it to understand current code repository conditions before deciding the next action, ensuring the Harness proceeds from Observe to Decide with confidence.

To generate a repository status snapshot, run an observation round using standard repo-level artifacts like goal/charter, snapshot/status, and milestone backlogs. This produces a narrow, structured summary that relies on checkpoint hash consistency for idempotency.

Baseline-driven reasoning uses standard repository-level artifacts such as goal/charter, snapshot/status, and milestone artifacts to estimate current conditions. It avoids self-reported or locally-maintained signals, ensuring the Harness evaluates actual repository scope state via structured summaries.

You cannot fully assess repository status with missing artifacts. The observation enforces explicit stop conditions when evidence is missing, stale, or contradictory, flagging insufficient observation to justify stopping rather than guessing the repository baseline state.

The limitation of a narrow repository status snapshot is its read-mostly observation boundary. It enforces a limited scope and flags boundary-crossing requirements, meaning it answers what the repository baseline state is right now, not what you should do next.