Verified:GitHub

spec-from-conversation

Extract structured specifications and implementation plans from conversation transcripts.

Updated Sep 14, 2026

Search Tags:#documentation #specification #implementation plan #conversation #decision log #requirements extraction #chat transcript

Ready to run

npx skills add https://github.com/Lawrence908/chiron --skill spec-from-conversation-lawrence908

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-from-conversation
Source: https://github.com/Lawrence908/chiron/tree/main/plugins/writing/skills/spec-from-conversation
Command: npx skills add https://github.com/Lawrence908/chiron --skill spec-from-conversation-lawrence908

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Valuable decisions, requirements, and technical details discussed in chat conversations often get lost or remain undocumented, forcing teams to re-discuss or reconstruct context later. ## Core Features & Use Cases - Requirement Extraction: Pull functional and non-functional requirements, constraints, and decisions out of unstructured chat history. - Structured Output: Produce formatted specification documents with sections for overview, requirements, design, API details, open questions, and action items. - Decision Logging: Capture decisions with their rationale while clearly marking open questions and ambiguities. - Use Case: After a brainstorming session about adding JWT authentication to an API, convert the entire conversation into a formal feature specification with endpoints, database schema, and a task checklist. ## Quick Start Convert this conversation transcript about the new authentication feature into a structured specification document with requirements and action items.

Frequently Asked Questions about spec-from-conversation

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

FAQPage Schema

How do I turn a chat conversation into a technical specification?▼

Provide the conversation transcript along with project context and the desired output format. The skill identifies key topics, extracts requirements and decisions, and organizes them into structured sections like Overview, Requirements, Design, and Action Items.

How to extract requirements from meeting or chat transcripts?▼

Requirements extraction works by reading the full conversation, identifying stated goals, features, and constraints, then listing them as functional and non-functional requirements. Technical details like libraries, schemas, and endpoints mentioned in the discussion are preserved.

Does the generated spec include decisions that were not finalized?▼

Yes, open questions and ambiguities are explicitly marked rather than resolved silently. The output clearly distinguishes decided items from unresolved topics so stakeholders know what still needs discussion.

What inputs are needed to generate a specification from a conversation?▼

You need the conversation transcript, relevant project or domain context, the desired output format such as spec or ticket, and optionally key topics or stakeholders to focus on. More context produces more accurate and complete specifications.

What are the limitations of generating specs from conversations?▼

The output only reflects what was actually discussed and will not invent missing requirements. Gaps in the conversation appear as open questions, so critical details never mentioned in chat must be added separately.