spec-from-stream

Convert spoken product descriptions into BRD, SRS, and NFR Obsidian notes.

11|Updated Nov 14, 2025
One-click install
npx skills add https://github.com/bug-ops/claude-plugins --skill spec-from-stream
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-from-stream
Source: https://github.com/bug-ops/claude-plugins/tree/main/rust-code/skills/spec-from-stream
Command: npx skills add https://github.com/bug-ops/claude-plugins --skill spec-from-stream

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill bridges the gap between initial product ideas and a structured specification package, converting spoken descriptions into a BRD, SRS, or NFR, formatted as Obsidian notes.

Core Features & Use Cases

  • Stream-of-Consciousness Input: Transforms user's unstructured ideas into formal specifications.
  • Spec Generation: Outputs BRD, SRS, and NFR documents for product management and software development.
  • Obsidian Integration: Outputs documents formatted for Obsidian knowledge bases.
  • Use Case: A project manager explains a feature over the phone. The Skill listens to the description and outputs a formatted BRD document ready for the team to review.

Quick Start

Describe your product idea to the spec-from-stream skill, and let it create a specification document for you.

Frequently Asked Questions about spec-from-stream

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

FAQPage Schema
How do I convert spoken product ideas into structured specifications?

To convert spoken product ideas into structured specifications, you provide a natural language description of your concept and the Skill generates formatted Business Requirements Documents, Software Requirements Specifications, and Non-Functional Requirements.

Can I generate an Obsidian notes BRD from unstructured stream-of-consciousness input?

Yes, you can generate an Obsidian notes BRD from stream-of-consciousness input. The Skill transforms unstructured, natural language product descriptions into formal specification documents formatted specifically for Obsidian knowledge bases.

Does the specification generation process require input in English?

Yes, the specification generation process requires input in English. While it supports natural language and handles various levels of input detail, providing your spoken product descriptions in English is necessary for accurate processing.

What is the best way to create SRS and NFR documents from a verbal feature description?

The best way to create SRS and NFR documents from a verbal feature description is to explain your product idea naturally. The Skill listens to the description and outputs formatted Software Requirements Specifications and Non-Functional Requirements ready for team review.

What types of product requirements documents can I generate for my Obsidian knowledge base?

You can generate Business Requirements Documents, Software Requirements Specifications, and Non-Functional Requirements for your Obsidian knowledge base. These documents are created from your spoken product ideas and formatted as structured notes.

Can I use this for product specification if my input lacks detailed technical structure?

Yes, you can use this for product specification even if your input lacks detailed technical structure. The Skill is designed to handle various levels of input detail and transforms unstructured ideas into formal documents.