engineering-decision-brief

Compile repository and incident evidence into layered decision briefs with source links.

1|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/getyak/talent-signal --skill engineering-decision-brief-getyak
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: engineering-decision-brief
Source: https://github.com/getyak/talent-signal/tree/main/.agents/skills/engineering-decision-brief
Command: npx skills add https://github.com/getyak/talent-signal --skill engineering-decision-brief-getyak

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Technical investigations often produce scattered notes where observations, opinions, and decisions blur together, forcing leaders and engineers to reconstruct the same analysis. This Skill turns repository, product, delivery, or incident evidence into one traceable decision brief readable at three depths. ## Core Features & Use Cases - Claim Ledger: Classifies every material claim as observation, interpretation, recommendation, decision, or outcome, with exact evidence locators and freshness tracking. - Three Reading Depths: Compiles an executive brief, an engineering dossier, and an evidence trail from a single claim ledger without duplicating claims. - Structured Brief Contract: Provides a typed content model (Brief, Finding, EvidenceRef) with quality gates for persistent pages, reports, or data models. - Use Case: After a CI/CD failure, use this Skill to diagnose the causal chain from symptom to system condition, compare remediation options with tradeoffs, and render a decision page where every finding links to commit-pinned source evidence. ## Quick Start Use the engineering-decision-brief skill to analyze this repository's flaky test failures and produce an executive brief, engineering dossier, and evidence trail.

Frequently Asked Questions about engineering-decision-brief

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

FAQPage Schema
How do I write an engineering decision brief for leadership?▼

State one decision question, freeze the snapshot being assessed, and build a claim ledger separating observations from interpretations. Then compile an executive projection with at most three headline findings, one recommended sequence, and an explicit decision request.

How to document a technical incident with traceable evidence?▼

Record each finding with its claim type, impact, supporting and contradicting evidence, and a verification condition. Use commit-pinned URLs or repository paths with line locators so every observation resolves to evidence in no more than two steps.

What is the difference between an observation and an interpretation in a technical report?▼

An observation is directly present in code, tests, runtime behavior, or an authoritative source, while an interpretation is a causal or comparative reading of observations. Confidence or polished prose must never promote an interpretation into an observation.

When should I use a decision brief instead of an ADR?▼

A decision brief is a dated projection supporting a specific decision across multiple evidence sources. Once a consequential choice is accepted, put its rationale in an ADR as the canonical record and mark the brief superseded rather than keeping competing truth.

What are the limitations of an engineering decision brief?▼

A brief is a dated projection, not a system of record, and a rendered page does not advance its status. It must expose missing, stale, or contradictory evidence and cannot turn one local bug into a strategic transformation without supporting evidence.