The problem

Founder brainstorming often happens in stream-of-consciousness voice memos or messy transcripts. Converting these "rambles" into actionable technical specs manually is time-consuming and leads to "hallucinated" requirements where the dev fills in gaps without asking.

What it does

• Analyzes voice transcripts to detect if the user needs a PRD, a Decision Memo, or a Skill Brief.
• Extracts raw signals including nouns, verbs, constraints, and contradictions from unstructured text.
• Maps missing information to ⚠️ not stated markers within the document.
• Generates a dedicated "Open Questions" block to surface contradictions and blocking unknowns.
• Enforces strict artifact templates to ensure consistency across product documentation.

Why this beats prompting it yourself

Generic prompts often try to "fix" a founder's contradictions, leading to wrong assumptions and wasted dev cycles. This skill is hardcoded to surface contradictions and gaps as explicit questions rather than quietly patching them with AI-generated fluff.

Use cases

• Turn a 5-minute Loom transcript into a structured PRD with clear acceptance criteria.
• Convert a "should we use X or Y" rambling Slack message into a formal Decision Memo.
• Draft a prompt engineering brief for a new agent based on a founder's verbal description.
• Audit a recorded meeting to identify conflicting requirements between stakeholders.

Known limitations

Not intended for client-facing polished docs or task prioritization. It focuses on raw spec-shaping for internal founder-to-developer handoffs.