sea-conversation-to-spec

Convert domain-expert conversations into formal SEA specifications.

1|Updated Oct 1, 2025

Search Tags:#specification #PRD #governance #ADR #requirements-gathering #SEA-DSL #generator-builder

Ready to run

npx skills add https://github.com/GodSpeedAI/SEA --skill sea-conversation-to-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sea-conversation-to-spec
Source: https://github.com/GodSpeedAI/SEA/tree/main/.claude/skills/sea-conversation-to-spec
Command: npx skills add https://github.com/GodSpeedAI/SEA --skill sea-conversation-to-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill translates conversational input from domain experts into formal SEA specifications (ADR → PRD → SDS → SEA-DSL), enabling generator-driven development without hallucinations.

Core Features & Use Cases

Automates the transition from stakeholder conversations to structured SEA specifications.
Generates ADR, PRD, SDS, and SEA-DSL artifacts, linking to semantic references in the Knowledge Graph.
Triggers generator creation (sea-generator-builder) when coverage gaps are detected.
Supports end-to-end governance, traceability, and artifact generation.

Quick Start

Engage with domain experts to capture requirements, then run the spec drafting workflow to generate ADR/PRD/SDS/SEA-DSL and connect to the knowledge graph.

Frequently Asked Questions about sea-conversation-to-spec

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

FAQPage Schema

How do I convert stakeholder conversations into formal software specifications automatically?▼

To convert stakeholder conversations into formal software specifications, this Skill transforms domain-expert dialogue into structured ADR, PRD, SDS, and SEA-DSL artifacts through automated requirements extraction and spec drafting workflows.

What is the best way to generate ADR and PRD documents from domain expert discussions?▼

Generating ADR and PRD documents from domain expert discussions involves running a spec drafting workflow that extracts requirements and links semantic references directly into a knowledge graph for end-to-end traceability.

How does spec-first governance work when extracting requirements from meeting transcripts?▼

Spec-first governance works by enforcing a strict transition pipeline from dialogue to deployable specifications, translating discovery conversations into validated ADR, PRD, SDS, and SEA-DSL artifacts without hallucinations.

Can I trigger a generator builder when specification coverage gaps are detected?▼

Yes, you can trigger a generator builder when coverage gaps are detected; the Skill automatically initiates the sea-generator-builder to fill missing specification elements during the validation phase.

Does the requirements-gathering process support linking to a knowledge graph for traceability?▼

The requirements-gathering process supports traceability by linking generated ADR, PRD, SDS, and SEA-DSL artifacts to semantic references within a knowledge graph, ensuring full governance across the specification lifecycle.