clavix-summarize

Extract structured requirements from conversations into mini-PRD files.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/alysonhower/dupcheck --skill clavix-summarize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clavix-summarize
Source: https://github.com/alysonhower/dupcheck/tree/main/.agent/skills/clavix-summarize
Command: npx skills add https://github.com/alysonhower/dupcheck --skill clavix-summarize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extract structured requirements from conversations into mini-PRD format to capture what was discussed during exploratory sessions and planning.

Core Features & Use Cases

  • Pre-validate conversation to ensure minimum viable requirements exist.
  • Extract key points: identify features, constraints, scope with confidence.
  • Generate output files: create mini-PRD, quick-prd, and original-prompt and save to .clavix/outputs/{project}/.
  • Quality check and save for planning.
  • Supports on-demand reference to previous conversations.

Quick Start

Summarize the discussion to produce three structured artifacts: mini-prd.md, quick-prd.md, and original-prompt.md that are stored in the project outputs.

Frequently Asked Questions about clavix-summarize

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

FAQPage Schema
How do I extract requirements from conversations to create a mini-PRD?

To extract requirements from conversations into a mini-PRD, the Skill pre-validates the discussion to ensure viable requirements exist, then identifies features, constraints, and scope with confidence indicators before generating structured markdown files.

Can I convert exploratory discussions into structured project planning documents?

Yes, you can convert exploratory discussions into structured project planning documents. The Skill processes conversation text to capture key points and outputs a mini-prd.md and quick-prd.md specifically for planning purposes.

What files are generated when summarizing conversations into project requirements?

Summarizing conversations into project requirements generates three files: mini-prd.md for structured planning, quick-prd.md for fast reference, and original-prompt.md, all stored under the .clavix/outputs/{project}/ directory.

Does the requirement extraction process handle edge cases and uncertainty?

Yes, the requirement extraction process handles edge cases and uncertainty. It includes confidence indicators alongside identified features and scope, applying quality checks to manage edge cases during the extraction workflow.

What is the best way to pre-validate conversations before generating a PRD?

The best way to pre-validate conversations before generating a PRD is to run the discussion through an automated check that ensures minimum viable requirements exist, preventing empty or insufficient planning artifacts from being created.

Are previous conversation summaries stored for on-demand project reference?

Yes, previous conversation summaries are stored for on-demand project reference. The generated mini-PRD and prompt files are saved directly under the .clavix/outputs/{project}/ path for later retrieval.