h-note
h-note captures lightweight micro-decisions and observations into the decision graph when an operator identifies something noteworthy. Use it to record factual choices (choosing X over Y with rationale), observations with reasoning (performance baseline change), or tactical insights, but require explicit rationale for every note and reject vague statements. Route binding decisions to h-decide and full problem frames to h-frame instead.
git clone --depth 1 https://github.com/m0n0x41d/haft /tmp/h-note && cp -r /tmp/h-note/packages/haft-pi/skills/h-note ~/.claude/skills/h-noteSKILL.md
# h-note — Save a lightweight fact Use `haft_note` only when the operator asks to remember/save something or a current Work supplies a concrete operator-named or agent-inferred receiving use that needs an addressable fact. Keep observations atomic, state why they matter, and anchor them to relevant artifacts and stable implementation files. A note is not a choice, ProblemCard, evidence verdict, approval, or WorkPlan. Tool arguments and generated references are not proof that the operator asked to persist. Use `task_context` only to correlate the saved fact with its receiving task, not as an authority receipt. Set `valid_until` when the fact has a known expiry or review boundary. When the exact current concern is known, include `entity_ref` with `ref_kind_id="U.EntityRef"` plus `bounded_context_ref`. Preserve the returned `Haft.ProjectRecordRef` exactly for later typed relations; never derive a record ID from the note artifact ID. Without exact concern basis, the note may persist while typed projection remains underdetermined.
|
|
Manual-only skill that creates bounded execution authority from an explicit operator grant. Never auto-trigger or infer approval from prompt text or tool schemas.
Compare two or more existing candidates under an explicit characteristic space, parity basis, and predeclared selection policy. Return trade-offs and a non-dominated set; persistence is conditional and a binding choice requires a direct unambiguous operator request.
Route one direct, unambiguous operator request for a bounded binding choice. A manual h-decide invocation is a compatible shortcut, not an authorization receipt.
Diagnose a concrete failure with rival-hypothesis testing. Stabilize the symptom, generate distinct explanations, test discriminating observations read-only in parallel, and rank by evidence while retaining losing rivals.
Generate 3-5 genuinely distinct candidate approaches for a current question, with the weakest link of each visible. May work from an inline question or a durable ProblemCard; persistence is conditional.
Shape an under-articulated engineering problem without assuming a solution or forcing a project phase. Default to a conversational frame; create a ProblemCard only on explicit save intent or when current Work supplies a concrete operator-named or agent-inferred receiving use that needs a durable accepted problem statement.