board-reconcile
Skill1 starsChanged 36 days agoNo licenceView on GitHub
Check whether a task board still tells the truth, by diffing it against version control and the project's own `.product/` state. Use this whenever the recorded status of work might have drifted from reality — triggers on "does the board match reality", "reconcile the board", "sync the tasks", "is the board up to date", "what's actually done", "the tracker is out of date", "clean up the backlog", "check the sprint board", or before any status review or stakeholder checkpoint where you are about to present progress. Works from an export (xlsx/csv/json) of any tracker — Jira, Linear, Asana, Trello, Planner, GitHub Issues — so it needs no API access or integration. It reports drift in BOTH directions: cards left open that were actually shipped, cards marked done with nothing behind them, work with no plan, plan with no card, and items stale long enough to need a decision. It fixes `.product/` itself and RECOMMENDS the card movements for a human to apply — it is deliberately one-way and never writes to the tracker. Use intake-triage instead when the items are NEW and need deciding; this one is for items that already exist and whose recorded status is in question. Use product-guide if the question is "what should I do next" rather than "is what I'm looking at true".
- Commits and pushes
In this repository35 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- change-scoperSkill
- codebase-cartographerSkill
- commit-conventionsSkill
- debuggerSkill
- dynamo-bootstrapSkill
- dynamo-bootstrapSkill
- dynamo-designSkill
- dynamo-designSkill
- dynamo-probeSkill
- dynamo-probeSkill
- dynamo-rebuildSkill
- dynamo-rebuildSkill
- dynamo-repairSkill
- dynamo-repairSkill
- dynamo-reworkSkill
- dynamo-submissionSkill
- dynamo-submissionSkill
- dynamo-verifySkill
- dynamo-verifySkill
- feature-grafterSkill
- feature-integratorSkill
- grillingSkill
- intake-triageSkill
- phase-executorSkill
- pr-descriptionSkill
- product-architectSkill
- product-guideSkill
- product-state-initSkill
- quality-gateSkill
- refactor-stewardSkill
- regression-guardSkill
- root-cause-investigatorSkill
- safety-net-builderSkill
- surgical-fixerSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.