CtrlK
BlogDocsLog inGet started
Tessl Logo

giuseppe-trisciuoglio/developer-kit

Comprehensive developer toolkit providing reusable skills for Java/Spring Boot, TypeScript/NestJS/React/Next.js, Python, PHP, AWS CloudFormation, AI/RAG, DevOps, and more.

89

Quality

89%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Risky

Do not use without reviewing

Overview
Quality
Evals
Security
Files

devkit.write-a-minute-of-a-meeting.mdplugins/developer-kit-project-management/commands/

description:
Generates professional meeting minutes from transcripts or notes. Use when you need to create structured meeting documentation after a meeting.
argument-hint:
[transcript-file] [meeting-title] [date]
allowed-tools:
Read, Write

Overview

Generates professional meeting minutes from transcripts or notes. Use when you need to create structured meeting documentation after a meeting.

Act as an expert administrative assistant specialized in creating meeting minutes. Analyze the provided transcript or notes and produce a clear, concise, and professional meeting minute document.

Usage

/devkit.write-a-minute-of-a-meeting $ARGUMENTS

Arguments

ArgumentDescription
$ARGUMENTSCombined arguments passed to the command

Execution Instructions

Agent Selection: To execute this task, use the following approach:

  • Primary: Use general-purpose agent with appropriate domain expertise
  • Or use specialized agent if available for the specific task type

Input

Read the meeting transcript from: $1

Meeting Information Template

Use these details or ask for them if not provided:

  • Meeting Title/Subject: $2
  • Date and Time: $3
  • Location/Platform: (e.g., Teams, Zoom, in-person)
  • Attendees: (list participants)
  • Meeting Objective: (purpose of the meeting)

Document Structure

Create the meeting minutes with the following sections:

1. Executive Summary

Begin with a brief paragraph (3-4 sentences maximum) summarizing the main outcomes and key decisions from the meeting.

2. Agenda Items Discussed

For each agenda item, create a dedicated section that includes:

  • Clear and concise summary of the discussion
  • Significant contributions from participants, properly attributed
  • Conclusions reached for each item

3. Decisions Made

Extract and list all final decisions approved during the meeting. For each decision, specify:

  • The decision itself
  • Who proposed/approved the decision

4. Action Items

Create a table with the following columns:

ActionResponsibleDeadline
Description of the taskPerson or team assignedCompletion date

5. Open Issues/Next Steps

List any unresolved issues or topics to be discussed in future meetings.

6. Next Meeting

Include date and time of the next meeting if established.

Style Guidelines

  • Use professional, clear, and objective language
  • Avoid unnecessary jargon and unexplained acronyms
  • Use bullet points to improve readability
  • Maintain a neutral and factual tone
  • Format using proper Markdown syntax

Examples

/devkit.write-a-minute-of-a-meeting example-input

plugins

developer-kit-project-management

commands

devkit.write-a-minute-of-a-meeting.md

README.md

CHANGELOG.md

context7.json

CONTRIBUTING.md

README_CN.md

README_ES.md

README_IT.md

README.md

tessl.json

tile.json