← HUMMBL OperationsCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to HUMMBL Operations
Snapshot Sep 30, 2026 · 23:15 UTC · version 0.1.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Convert an authorized backlog or intake set into a defensible priority queue with blockers, dependencies, and next actions. Use for backlog review, intake sorting, or focus decisions; do not silently modify task systems.",
"included_files": [],
"name": "work-triage",
"skill_md_contents": "---\nname: work-triage\ndescription: Convert an authorized backlog or intake set into a defensible priority queue with blockers, dependencies, and next actions. Use for backlog review, intake sorting, or focus decisions; do not silently modify task systems.\n---\n\n# Work Triage\n\nProduce a focused execution queue from the work evidence in scope.\n\n## Normalize the evidence\n\nCapture only attributes supported by the source: identifier, intended outcome, status, owner, priority, due date, dependencies, blockers, and source. Mark consequential gaps as unknown. Flag duplicates, stale entries, and conflicting records for review rather than altering them.\n\n## Make priority legible\n\nUse the factors that materially distinguish the work:\n\n- user, mission, or business impact;\n- deadlines and external commitments;\n- risk reduction and reversibility;\n- dependency leverage or unblock value;\n- readiness and confidence in the next action;\n- effort and opportunity cost.\n\nAvoid pseudo-precise scores unless the user already has a scoring model. State the decisive rationale behind each important placement.\n\nOrganize the result as:\n\n- **Now** — a deliberately small set of immediately executable work;\n- **Next** — ready or nearly ready after current dependencies;\n- **Later** — valid work without present urgency or leverage;\n- **Resolve** — duplicate, stale, underspecified, or closure-candidate work.\n\nList blocked work separately from active work. For each Now and Next item, give its outcome, owner if known, timing, dependencies, blockers, and one-sentence priority rationale. End with decisions needed, unowned work, and the smallest useful next actions.\n\nThis triage is a proposal. Do not create, edit, close, assign, or notify through an external system unless the user explicitly approves the final mutation set. Re-read targets before any later write and stop on conflicting changes.\n"
}SHA-256 of public snapshot: d53f87d9476f5196351e6cd4fcf664f5953dde2f69fd74832b822fb7ccf13d42