okhp3-triage-and-file

Assigns recorded lifecycle dispositions to project inbox items during triage reviews.

1|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/OKHP3/refoldec --skill okhp3-triage-and-file-okhp3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: okhp3-triage-and-file
Source: https://github.com/OKHP3/refoldec/tree/main/.agents/skills/okhp3-triage-and-file
Command: npx skills add https://github.com/OKHP3/refoldec --skill okhp3-triage-and-file-okhp3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project inboxes accumulate captures, notes, and ideas with no clear owner or next step, leading to duplicated efforts and lost context. This Skill reviews each inbox item and assigns exactly one recorded, approval-aware disposition so nothing is silently deleted or moved without authorization. ## Core Features & Use Cases - Disposition Assignment: Routes each item to exactly one of MERGE, ACTIVATE, GRADUATION CANDIDATE, ARCHIVE, or NEEDS INPUT, with evidence and source path preserved. - Approval-Aware Safety: Returns BLOCKED when project root, inbox path, lifecycle-record paths, or owner authority are missing, and never deletes or moves files without explicit authorization. - Lifecycle Record Keeping: Updates the owner-approved effort register and decision register when efforts change state or non-trivial decisions are made. - Use Case: During a weekly inbox sweep, review ten captured notes: merge three into an active effort, flag one as a graduation candidate routed to the graduation gate, archive two with revival conditions, and mark the rest as NEEDS INPUT with the specific owner decision required. ## Quick Start Use the okhp3-triage-and-file skill to review the items in my project inbox and record one disposition with evidence for each.

Frequently Asked Questions about okhp3-triage-and-file

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

FAQPage Schema
How do I triage a project inbox with an AI agent?▼

Provide the project root, inbox path, and lifecycle-record paths, then ask the agent to review each item. It assigns one disposition per item (MERGE, ACTIVATE, GRADUATION CANDIDATE, ARCHIVE, or NEEDS INPUT) with evidence and the source path preserved.

What dispositions can an inbox item receive during triage?▼

Each item receives exactly one of five dispositions: MERGE into an active effort, ACTIVATE as a new effort, GRADUATION CANDIDATE routed to the graduation gate, ARCHIVE with a revival condition, or NEEDS INPUT with the owner decision stated.

Can the triage skill delete or move inbox files automatically?▼

No. The skill never deletes sources without explicit authorization and only creates or moves files when owner authority is granted. Without the required paths or authority, it returns BLOCKED and leaves everything in place.

What happens when the inbox path or owner authority is missing?▼

The skill returns BLOCKED, names the missing path or authority, and does not create, move, or modify any files. This prevents unapproved changes to project content.

How are duplicate or related captures handled during triage?▼

Similarity alone does not prove duplication. The skill proposes MERGE only with a recorded rationale, preserves both sources, and logs non-trivial merge decisions in the owner-approved decision register.

What are the limitations of automated inbox triage?▼

It does not publish or move work outside the project, replace domain-specific project review, or imply an automatic archiver exists. Owner approval is still required for state changes recorded in the effort register.