clavix-summarize

Extract structured requirements from conversations into mini-PRD, quick-PRD, and original prompt files.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/mbed92/phd --skill clavix-summarize-mbed92
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clavix-summarize
Source: https://github.com/mbed92/phd/tree/main/.skills/clavix-summarize
Command: npx skills add https://github.com/mbed92/phd --skill clavix-summarize-mbed92

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of capturing and structuring requirements discussed in natural language conversations, preventing loss of detail and ensuring clarity for development.

Core Features & Use Cases

  • Requirement Extraction: Identifies and extracts key features, constraints, and objectives from conversations.
  • Structured Output Generation: Creates three distinct files: a detailed mini-prd.md, a concise quick-prd.md, and the original-prompt.md.
  • Quality Assurance: Includes pre-validation checks and a self-correction protocol to ensure accuracy and completeness.
  • Use Case: After a product discovery call, use this Skill to automatically generate a Product Requirements Document (PRD) draft, saving significant manual effort and time.

Quick Start

Use the clavix-summarize skill to extract requirements from our last conversation.

Frequently Asked Questions about clavix-summarize

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

FAQPage Schema
How do I extract structured requirements from a product discovery conversation?

You can extract structured requirements from a conversation by processing the conversational data to identify features, constraints, and objectives, then generating a mini-PRD, quick-PRD, and original prompt format.

Can I automatically generate a PRD draft from conversational data?

Yes, automatically generating a PRD draft from conversational data creates a detailed mini-prd.md and a concise quick-prd.md file, preventing loss of detail and ensuring clarity for development.

How does conversation analysis validate completeness for requirements gathering?

Conversation analysis validates completeness for requirements gathering by running pre-validation checks, assigning confidence levels to extracted data, and enforcing a self-correction protocol for identified mistakes.

What is the best way to turn natural language conversations into structured output?

The best way to turn natural language conversations into structured output is to parse the dialogue for key objectives, validate the findings, and generate project-specific output files in a designated directory.

What quality assessment metrics are provided when extracting a mini-PRD?

When extracting a mini-PRD, quality assessment metrics are provided alongside pre-validation checks and a self-correction protocol to ensure the extracted features and constraints are accurate and complete.

Do I need a specific format for prompt engineering outputs?

You need a specific format for prompt engineering outputs, specifically generating an original-prompt.md file alongside mini-prd.md and quick-prd.md to capture structured requirements from your conversational data.