logvalet:decisions

Extract and summarize decision logs from Backlog issue timelines.

4|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/youyo/logvalet --skill logvalet-decisions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logvalet:decisions
Source: https://github.com/youyo/logvalet/tree/main/skills/decisions
Command: npx skills add https://github.com/youyo/logvalet --skill logvalet-decisions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams quickly uncover and summarize the decision history hidden in Backlog issue timelines—who decided what, when, and why—so stakeholders have a clear record of rationale.

Core Features & Use Cases

  • Identify decision signals in comments and update events to extract when decisions were made.
  • Produce a structured, chronological decision log with fields for When, Who, What, Why, and Context for issues or projects.
  • Use in retrospectives, audits, or progress reviews to understand the evolution of a solution and the rationale behind state changes.

Quick Start

Generate a decision log from a Backlog timeline for a specific ISSUE_KEY, then review the summarized rationale and dates.

Frequently Asked Questions about logvalet:decisions

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

FAQPage Schema
How do I extract a decision log from a Backlog issue timeline?

Extracting a decision log from a Backlog issue timeline involves parsing timestamps, authors, and decision signals from comments and update events to produce a structured chronological record of who decided what, when, and why.

What is the best way to summarize project decisions for a retrospective?

The best way to summarize project decisions for a retrospective is to analyze issue timelines to identify decision signals and state changes, revealing the rationale behind the evolution of a solution.

Can I analyze multiple issue timelines to generate a project-wide decision summary?

Yes, you can analyze multiple issue timelines to generate a project-wide decision summary by parsing comments and status-change events across relevant issues to surface decisions and rationales.

How does analyzing issue timelines reveal the rationale behind state changes?

Analyzing issue timelines reveals the rationale behind state changes by parsing timestamps and comments to identify decision signals, extracting the context of when and why a state was modified.

Does this decision summarization approach work for auditing Backlog progress reviews?

Yes, this decision summarization approach works for auditing Backlog progress reviews by outputting a structured log with fields for When, Who, What, Why, and Context for clear records.