create-decision-log

Compile meeting, Slack, and PR decisions into a GitHub Discussion.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/semicolon-devteam/semo --skill create-decision-log
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-decision-log
Source: https://github.com/semicolon-devteam/semo/tree/main/packages/biz/management/skills/create-decision-log
Command: npx skills add https://github.com/semicolon-devteam/semo --skill create-decision-log

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

회의, Slack, PR 등에서 내린 의사결정을 GitHub Discussion으로 투명하게 기록합니다.

Core Features & Use Cases

  • 의사결정 템플릿 생성 및 Discussion 작성
  • 의사결정 로그 URL 반환

Quick Start

제목, 출처, 참가자 등 정보를 바탕으로 Discussion을 생성합니다.

Frequently Asked Questions about create-decision-log

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

FAQPage Schema
How do I create a centralized decision log from Slack and GitHub discussions?

Create a decision log by compiling scattered discussions into a GitHub Discussion using a standardized template. This Skill generates a templated body with mandatory fields (title, category, source, context, decision, participants) and optional notes, then publishes to your command-center repository with a traceable URL for audit purposes.

What information do I need to document a decision in GitHub Discussion?

You need title, category, source (meeting, Slack, PR), context, decision, and participants. Optional fields include notes and related_issue links. The Skill enforces these mandatory fields to ensure every decision log entry contains complete traceability and context.

Can I use this to track decisions from meetings, Slack, and pull request discussions?

Yes, this Skill applies to multiple decision-making channels including meetings, Slack conversations, and PR discussions. It consolidates decisions from these scattered sources into a single GitHub Discussion with consistent formatting and traceability.

How does a decision log improve team transparency?

A centralized decision log creates an auditable record accessible to all team members. By moving decisions from ephemeral channels (Slack, meetings) into GitHub Discussions, you establish permanent traceability, context, and searchability for past decisions and their rationale.

What's the output after creating a decision log entry?

The Skill returns a standardized GitHub Discussion URL pointing to your decision log entry in the command-center repository. This URL serves as the permanent reference for the decision, its context, and participants.