h-reason

Frame problems and guide structured reasoning for architecture decisions.

1.4k|102|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/m0n0x41d/haft --skill h-reason
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: h-reason
Source: https://github.com/m0n0x41d/haft/tree/main/internal/cli/skill/h-reason
Command: npx skills add https://github.com/m0n0x41d/haft --skill h-reason

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Think clearly before building. This skill provides structured reasoning prompts and a disciplined workflow to help engineers frame problems, explore options, and justify architecture decisions.

Core Features & Use Cases

  • Structured reasoning modes (Understand, Explore, Choose, Execute, Verify) to frame problems and guide decisions.
  • Context-aware prompts and decision documentation to capture rationale and align stakeholders.
  • Guidance on when to delegate reasoning vs. perform autonomous reasoning and how to persist decisions for traceability.

Quick Start

Initiate a reasoning frame for a proposed architecture decision and outline options with criteria for evaluation.

Frequently Asked Questions about h-reason

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

FAQPage Schema
How do I frame architecture decisions and evaluate engineering trade-offs?▼

To frame architecture decisions, use structured reasoning modes like Understand, Explore, Choose, Execute, and Verify to outline options with evaluation criteria and document rationale for trade-offs.

What is structured reasoning for software architecture choices?▼

Structured reasoning for architecture choices is a disciplined workflow that uses context-aware prompts to guide problem framing, explore options, and capture decision documentation for stakeholder alignment.

When do I need structured problem framing for engineering decisions?▼

You need structured problem framing for engineering decisions when facing non-trivial choices involving architecture options, process improvements, or trade-offs where framing directly affects the outcome.

How do I document architecture evaluation criteria and decision rationale?▼

Document architecture evaluation criteria by applying serial reasoning modes to compare options and persisting the resulting decision documentation to ensure traceability and align stakeholders.

Can I use structured reasoning for process improvements and option comparisons?▼

Yes, you can use structured reasoning for process improvements and option comparisons, as the workflow explicitly applies to non-trivial engineering decisions where evaluating alternatives and framing affects outcomes.

When should I not use autonomous reasoning for trade-off evaluation?▼

Avoid autonomous reasoning for trade-off evaluation when explicit problem framing is required, opting instead to delegate reasoning modes and persist decision documentation to maintain traceability and stakeholder alignment.