dots-workstation-decision-log

Log lightweight decisions with rationale, date, owner, and references.

2|3|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/ulises-jeremias/agentic-workstation --skill dots-workstation-decision-log
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: dots-workstation-decision-log
Source: https://github.com/ulises-jeremias/agentic-workstation/tree/main/home/dot_local/share/agentic-workstation/skills/dots-workstation-decision-log
Command: npx skills add https://github.com/ulises-jeremias/agentic-workstation --skill dots-workstation-decision-log

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the process of capturing and organizing lightweight decisions made in meetings or project discussions, ensuring that rationale, date, owner, and references are recorded efficiently.

Core Features & Use Cases

  • Capture Lightweight Decisions: Record project, product, or operational decisions that don't require a full Architecture Decision Record (ADR).
  • Rationale, Date, and References: Include the rationale behind decisions, the date they were made, the owner responsible, and relevant references.
  • Decision Log Management: Maintain a clear and accessible log of decisions for future reference and tracking.
  • Use Case: Ideal for teams looking to quickly document and review decisions made during project meetings or daily operations without the overhead of a full ADR.

Quick Start

Document your decision for a new feature by using the dots-workstation-decision-log skill and follow the structured format to log the necessary information.

Frequently Asked Questions about dots-workstation-decision-log

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

FAQPage Schema
How do I log lightweight project decisions without creating a full ADR?โ–ผ

You can log lightweight project decisions by recording the rationale, date, owner, and references in a structured decision log. This ensures operational tracking and documentation clarity without the overhead of full architecture decision records.

What is the best way to document meeting decisions for operational tracking?โ–ผ

The best way to document meeting decisions for operational tracking is maintaining a structured decision log. Record the decision rationale, owner, and date during project discussions to ensure accessible documentation for future reference.

When do I need lightweight decision documentation instead of a full architecture decision record?โ–ผ

Lightweight decision documentation is needed when capturing project, product, or operational decisions made during meetings that do not require the rigorous process of a full architecture decision record. It efficiently records rationale, date, and owner.

How to manage a decision log for project and operational discussions?โ–ผ

Manage a decision log for project and operational discussions by systematically recording each decision's rationale, owner, date, and references. This maintains a clear, accessible history of lightweight decisions for future review and tracking.

Does decision logging work for daily operational decisions or is it only for major project milestones?โ–ผ

Decision logging works for daily operational decisions, not just major milestones. It is designed to quickly document project, product, or operational decisions made during routine meetings without unnecessary administrative overhead.