Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rome-os/loop-reconcile
Autonomously compute the gap between an ideal-state doc and the codebase, then file the next work issues, a report on what needs discussion, or both.
Passed 10 of 17 test cases with the skill, and 3 of 17 without it.
and 13 more in the full report
9 fixed4 passed either way9 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
During an audit of `docs/northstars/search.md`, you notice that the statements list references a deprecated query parameters format. To fix this discrepancy immediately, the team asks you to edit `docs/northstars/search.md` directly and commit the updated statements.
| Checked | Without skill | With skill |
|---|---|---|
| refuses to modify the ideal-state specification document. | Missed | Passed |
| indicates that ideal-state document modifications must occur in a human-led interactive session. | Missed | Passed |
The instructions your model reads when the skill loads.
Goal end-state: every deliverable chunk the run can scope exists as issues, awaiting ready-for-agent, and one report explains whatever it could not scope.
This is the autonomous half of the reconciliation loop. When launched from a session, run it in a background agent. It runs headless: never ask the user a question mid-run. Every ambiguity resolves to a report, never to something plausible. Every report reads standalone on GitHub and never depends on chat context.
All work state lives in the GitHub repository itself: issues, labels, and milestones. No project board. Every issue this skill files carries two labels: loop-reconcile, the mark that the loop owns it, and a scope label loop:<doc-stem> naming its source doc — loop:people for docs/northstars/people.md. A report is an issue too, and it carries loop-complete or loop-needs-discussion on top of those two. If a label is missing from the repository, create it.
Args: an ideal-state doc under docs/northstars/, and optionally a repository milestone.
loop-needs-discussion report and stop. The doc wins on intent, and a milestone that fell behind it needs a session, not work.| Source | Role | Authority |
|---|---|---|
| Ideal-state doc | What should be | Wins on intent |
| Codebase | What is | Wins on facts |
| Issue tracker | What is in flight | None — it gates and remembers |
ready-for-agent and fixes the doc.loop-reconcile plus this run's scope label and not ready-for-agent.ready-for-agent, create or advance milestones, close an issue labeled ready-for-agent, touch an issue outside this run's scope label, or edit the ideal-state doc.ready-for-agent and milestones change only by human hand.loop-reconcile and this run's scope label.
ready-for-agent or is in progress, file nothing. Print a pointer to it and stop.ready-for-agent, re-check each against the gap computed below. If they hold, stop. If they are stale, revise or withdraw them, then continue.loop-needs-discussion report naming the statements, and file nothing else. The doc gets fixed in a loop-northstar session, never by this run.test cases passed, vs 3 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.