add-to-ledger

To track skill work across multiple repositories, you can create or update durable work-ledger records that persist across teams. This provides consistent visibility, ownership tracking, and governance for skill initiatives.

A work ledger is a central, auditable record that maintains skill initiatives across repositories. You need it when scope, ownership, and verification details must persist durably across teams and projects.

To create a new ledger item, provide the required inputs including skill_slug, title, repo, owner, status, priority, item_type, and impact_tie. This registers the skill work in the central work ledger.

Yes, you can revive dormant skills in the central work ledger by updating existing records with clearly defined scope and links to the canonical skill source of truth.

Registering a skill in the work ledger requires eight inputs: skill_slug, title, repo, owner, status, priority, item_type, and impact_tie. These enforce one-canonical-item workflow with status progression.

The best way to maintain scope changes for cross-repo skill work is updating existing ledger items to reflect status progression and verifications. This enforces a one-canonical-item workflow linked to central sources.