Skill Detail

Keep Agent Engineering Decisions Current with Haft

Use Haft when an agent needs source-backed decision framing, comparison, authorization records, and stale-evidence checks across supported coding-agent hosts.

Developer ToolsMulti-Framework
Developer Tools Multi-Framework Published
⭐ 1.4k GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill keep-agent-engineering-decisions-current-with-haft Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
Haft CLI; one supported agent host such as Claude Code, Codex, Cursor, Gemini CLI, Grok CLI, Hermes, Zed, Antigravity, or OpenCode; Git and a local project workspace.
Install & setup
Install with curl -fsSL https://raw.githubusercontent.com/m0n0x41d/haft/main/install.sh | bash, then initialize explicitly in the project with a host flag such as haft init –codex, haft init –claude, haft init –all, or haft init –core-only.
Author
m0n0x41d
Publisher
Open Source
Last updated
Aug 11, 2026
Quick brief

Use Haft when an engineering agent needs to frame a decision, compare options under explicit parity rules, record the authorization behind a plan, or verify whether a previous decision is still supported by current evidence. The operator installs Haft, initializes it in a project, configures the chosen host adapter, and runs focused workflows such as /h-frame, /h-explore, /h-compare, /h-decide, /h-verify, and /h-status. Use this skill to run, configure, review, and manage project decisions that future agent work will depend on.

How it works

What this skill actually does

Invoke this instead of a normal note, a generic memory store, or an ad hoc prompt when later agent work must rely on a decision and needs replayable context: what was decided, what evidence supported it, whether the evidence has decayed, and whether a human decision or revised plan is now required.

The scope boundary is agent-assisted engineering decision governance inside a project. This is not a generic framework card, a broad CLI listing, or a replacement for the supported coding agents themselves. It is a local-first decision and project-memory layer for agents that need durable, source-backed reasoning records.