add-work-priority

Collect required and optional fields and write a work-ledger item via add_ledger_item.py.

Updated Feb 3, 2026

Search Tags:#automation #planning #priority #task-tracking #ledger #work-management

Ready to run

npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill add-work-priority

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-work-priority
Source: https://github.com/BedaBeda-Growth/bedabeda-growth-site/tree/main/skills/add-work-priority
Command: npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill add-work-priority

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating prioritized work items by automatically populating and appending to the work ledger when a new priority item is requested.

Core Features & Use Cases

Guides Kai through collecting required fields (title, owner, impact_tie, repo) and optional fields (item_type, priority, blast_radius, done_criteria) for a ledger item.
Persists the new item using scripts/add_ledger_item.py, ensuring consistency and traceability of work items.
Use Case: When a product/ops lead asks to add a priority, automatically create and log a ledger entry for review and execution.

Quick Start

Provide the item title, owner, and impact details, then run the script to add the ledger item.

Frequently Asked Questions about add-work-priority

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate logging a priority request into a work ledger?▼

To automate logging a priority request into a work ledger, you need to collect the required fields like title, owner, impact_tie, and repo, then execute a script to persist the new tracked ledger entry.

What information is needed to create a tracked work-ledger item?▼

Creating a tracked work-ledger item requires four mandatory fields: title, owner, impact_tie, and repo. You can also include optional fields like item_type, priority, blast_radius, and done_criteria for better work management.

How does formalizing a priority request into a ledger entry work?▼

Formalizing a priority request into a ledger entry works by guiding you through collecting mandatory and optional work management metadata, then writing the structured item into your tracking ledger via an automated script.

Can I add optional fields like blast radius and done criteria to my task-tracking ledger?▼

Yes, you can add optional fields like blast_radius, done_criteria, item_type, and priority to your task-tracking ledger item alongside the required fields to improve consistency and traceability across projects.

What is the best way to track priority work items across multiple projects?▼

The best way to track priority work items across multiple projects is to formalize requests into a structured ledger schema, ensuring every entry captures required owner and impact details for consistent execution.

Do I need a specific repository setup to use automated work management logging?▼

Yes, you need to specify a target repo as one of the required fields to successfully write and persist new priority work items into your task-tracking ledger.