process-meeting-script

Translate meeting scripts into summary, requirements, sales feedback, and project-requirements.json artifacts.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/rachel353/fullty-plan --skill process-meeting-script
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: process-meeting-script
Source: https://github.com/rachel353/fullty-plan/tree/main/.claude/skills/process-meeting-script
Command: npx skills add https://github.com/rachel353/fullty-plan --skill process-meeting-script

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill processes meeting scripts to produce a consistent, auditable set of artifacts including a summary, requirements, client feedback, and a structured project-requirements.json. It ensures alignment between notes, decisions, and requested actions across meetings and stakeholders.

Core Features & Use Cases

  • Automatically generates summary.md from finalized meeting content, prioritizing client-approved statements.
  • Produces requirements.md with categorized items and REQ IDs, including unconfirmed items for follow-up.
  • Creates sales-feedback.md to document stakeholder gaps, improvement suggestions, and client feedback.
  • Updates project-requirements.json with versioning and a changeLog to track the evolution of the project scope.

Quick Start

Run the skill on a newly saved meeting script to automatically generate the four artifacts and push them to the project workspace.

Frequently Asked Questions about process-meeting-script

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

FAQPage Schema
How do I turn meeting scripts into structured project requirements and documentation?▼

Meeting scripts are translated into structured artifacts by generating summary.md, requirements.md, sales-feedback.md, and project-requirements.json. The skill applies input validation and template-based generation to produce auditable, ready-to-use docs.

Can I re-process edited meeting scripts to update existing requirements documentation?▼

Yes, the skill supports re-analysis of edited meeting scripts. It updates project-requirements.json with versioning and a changeLog, ensuring the evolution of project scope is tracked across new scripts and edits.

What is the best way to generate a project-requirements.json file from meeting notes?▼

The best way to generate project-requirements.json is by running the skill on a finalized meeting script. It automatically extracts decisions and requested actions, applying versioning and a changeLog to track project scope evolution.

Does this approach work for categorizing unconfirmed requirements from meeting transcripts?▼

Yes, processing meeting scripts produces requirements.md with categorized items and REQ IDs. It explicitly includes unconfirmed items for follow-up, prioritizing client-approved statements while documenting stakeholder gaps.

How do I document client feedback and stakeholder gaps from internal and client meetings?▼

You document client feedback by running the skill on your meeting scripts. It creates sales-feedback.md to record stakeholder gaps, improvement suggestions, and client feedback, applying to both internal and client contexts.

Do I need any external dependencies to automate meeting documentation generation?▼

No external dependencies are required to automate meeting documentation generation. The skill independently performs input validation and template-based generation to output summary, requirements, and feedback files directly to your project workspace.