decision-triage

Generate ADRs, edits, or work items for each decision inbox entry.

8|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/ninthwave-io/ninthwave --skill decision-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-triage
Source: https://github.com/ninthwave-io/ninthwave/tree/main/skills/decision-triage
Command: npx skills add https://github.com/ninthwave-io/ninthwave --skill decision-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill provides a structured, interactive workflow to drain the Ninthwave decision inbox by producing concrete artifacts (ADR, work items, or edits) for each decision and documenting why a choice was made.

Core Features & Use Cases

  • Parallel investigation: run grounded subagents to survey the consuming repo, its docs conventions, and related decisions.
  • Artifact generation: draft ADRs, code edits, or work-item records ready for review and commit.
  • Phase-driven workflow: phase 1 load, phase 2 investigate, phase 3 decide, phase 4 execute, phase 5 wrap.
  • Batch decision handling: present options A-G for each log and apply in a batch after user input.

Quick Start

Start by loading the Decisions inbox and begin parallel investigations, then review each decision and apply the chosen artifacts in batch.

Frequently Asked Questions about decision-triage

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

FAQPage Schema
How do I triage decisions and generate ADRs automatically?

Triage decisions by loading a decision inbox and generating concrete artifacts like ADRs, code edits, or work items. The workflow surveys the consuming repo to align with existing conventions before proposing batch changes.

What is the best way to document decision rationale for code edits?

Document decision rationale by producing concrete artifacts with recorded justifications. The workflow drafts ADRs or work items ready for review, ensuring the reasoning behind each code edit is preserved and aligned with repo conventions.

How do I manage a backlog of pending decisions across multiple files?

Manage a backlog of pending decisions by draining a decision inbox through a phase-driven workflow. It loads decisions, investigates in parallel, presents options A-G for each log, and applies changes in a batch after user input.

Can I generate work items with lineage tokens for batch execution?

Generate work items with lineage tokens by completing the investigation and decision phases. The workflow yields a concrete artifact payload and a batch plan for execution, embedding lineage tokens to track each work item.

Does this workflow align new ADRs with existing repository documentation conventions?

The workflow aligns new ADRs with existing repository documentation conventions by running grounded subagents. These subagents survey the consuming repo and its related decisions before proposing any artifact changes.

What are the limitations of automated decision triage for software engineering?

Automated decision triage requires a structured inbox and user input to select options A-G before execution. It does not autonomously commit changes; it proposes artifacts and a batch plan that require explicit review and approval.