Shape engineering problems into structured frames with signals, constraints, and acceptance criteria.
npx skills add https://github.com/m0n0x41d/haft --skill h-frame
Please help me install this Agent Skill. Skill: h-frame Source: https://github.com/m0n0x41d/haft/tree/main/internal/cli/skill/h-frame Command: npx skills add https://github.com/m0n0x41d/haft --skill h-frame
Engineering requests often arrive as premature solutions or vague redesign proposals before the actual problem is understood. This Skill separates observed signals from assumed causes, restores overloaded terminology, and produces a clear problem frame with scope, constraints, and acceptance criteria before any solution work begins.
Ask the agent to frame the problem behind a proposed change, for example: "Frame the problem behind the request to rewrite our caching layer before we commit to a design."
High-intent search queries and answers about installing and using this skill.
Start by separating the observed signal from the assumed cause and proposed fix, then name the affected object and bounded context. State scope, hard constraints, and optimization targets, and draft an observable acceptance condition for operator correction.
A ProblemCard is a durable Haft record of a framed problem including signal, constraints, acceptance basis, and affected entity. Create one only on explicit save intent or when a concrete receiving use needs transfer, replay, audit, or costly-reversal protection.
Use h-frame when the problem itself is under-articulated and needs shaping before any work. Hand off to h-diagnose when there is a concrete failure with unclear cause and rival hypotheses are the live question.
The conversational framing procedure works without persistence, but FPF pattern queries, project memory resolution, and ProblemCard recording require the Haft MCP tools haft_query and haft_problem.
The projection is underdetermined when no exact current entity reference and bounded context are available to bind the card. The card is still saved honestly; this is not a failure and must be reported rather than hidden.
sparkline-venturesCluster collected evidence into problem-framed themes with confidence analysis.
maestria-coFrame design problems and document architecture decisions as ADRs.
tyhuffman7Guide structured four-phase bug investigations to diagnose root causes.
ComputerConnectionRestrict Edit and Write operations to a user-specified directory.
