Manage unresolved governance work with a central ledger.
npx skills add https://github.com/VictorHueni/homemade-claude-kit --skill util-open-items
Please help me install this Agent Skill. Skill: util-open-items Source: https://github.com/VictorHueni/homemade-claude-kit/tree/main/skills/util-open-items Command: npx skills add https://github.com/VictorHueni/homemade-claude-kit --skill util-open-items
This Skill provides a central ledger for managing unresolved governance work, allowing you to file, triage, close, and archive open items efficiently.
markdown and github backends for flexible integration.Use the util-open-items skill to file a new open item:
util-open-items sync --source-artefact docs/project-control/open-items/open-items.md \
--source-anchor "#q3" --source-heading "Q3 — How do partners authenticate?" \
--type decision-gap --summary "Auth model for partner API undecided" \
--resolution-path "Open ADR on token strategy" --priority high --owner victor \
--due 2026-06-15
High-intent search queries and answers about installing and using this skill.
You manage unresolved governance work using a central ledger by filing, triaging, closing, and archiving open items. This central ledger approach tracks decision gaps and resolutions throughout the review cycle.
The best way to triage open items in a governance review cycle is using a central ledger to file items with priorities, owners, and due dates. You then update their status until closure and archive them post-cycle.
Yes, the open items ledger works with both markdown and github backends for flexible integration. It requires specific configuration and mapping to utilize backend-specific features effectively.
You file a new open item for a governance decision gap by specifying a source artefact, anchor, type, summary, resolution path, priority, owner, and due date. The ledger syncs this data for tracking.
Yes, you can generate status reports for governance work directly from the central ledger. This feature allows you to track the progress of unresolved open items throughout the review cycle.
Yes, you need to configure backend mappings to archive open items. The system requires configuration and mapping for backend-specific features to properly archive items at the end of a review cycle.
BedaBeda-GrowthCreate and update work-ledger records for skill initiatives across repositories.
DethonParse code review feedback and apply fixes to cited files with verification and a completion report.
benjaminshoemakerAutomate Git-backed implementation of [ready] TODOs in TODOS.md files.
code-yeongyuAutomate GitHub issue triage with streaming per-issue background tasks.