hforge-decide

Create durable ADR/ASR records under .hforge/runtime/decisions/.

3|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/ldilov/harness-forge --skill hforge-decide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hforge-decide
Source: https://github.com/ldilov/harness-forge/tree/main/.agents/skills/hforge-decide
Command: npx skills add https://github.com/ldilov/harness-forge --skill hforge-decide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn meaningful architectural choices into durable decision artifacts to preserve reasoning across sessions and tool resets.

Core Features & Use Cases

  • Create ASR/ADR records for architecture-significant findings within Harness Forge workspaces.
  • Automatically organize decisions under .hforge/runtime/decisions/ and link related decisions.
  • Provide a reproducible decision trail for future audits, reviews, and onboarding.

Quick Start

Ask it to record a decision topic and it will generate a durable ADR/ASR under .hforge/runtime/decisions/.

Frequently Asked Questions about hforge-decide

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

FAQPage Schema
How do I record an architecture decision so it survives across sessions?

To record an architecture decision, you create an ADR or ASR artifact that captures the reasoning. This skill writes durable decision records under .hforge/runtime/decisions/ to preserve your architectural choices across sessions and tool resets.

What is the best way to maintain a decision trail for repository governance?

Maintaining a decision trail requires storing governance choices as durable artifacts. This skill automatically organizes decisions under .hforge/runtime/decisions/ and links related findings, providing a reproducible audit trail for onboarding and reviews.

How do I create an ADR for architecture reviews in my workspace?

You create an ADR by asking this skill to record a decision topic. It generates a durable architecture decision record within your Harness Forge workspace, automatically organizing and linking the file to related findings for traceability.

Do I need a specific workspace structure to store architecture decision records?

Yes, storing architecture decision records requires a Harness Forge workspace. The skill writes decision artifacts specifically to the .hforge/runtime/decisions/ directory, organizing them automatically to ensure traceability and auditability across sessions.

When should I use an ASR instead of just saving architecture notes?

You should use an ASR when you need durable, traceable artifacts rather than temporary notes. This approach preserves architectural reasoning across sessions, automatically links related findings, and provides a reproducible decision trail for audits.