using-startup-superpowers

Use a shared conventions skill that defines a single source of truth like startup/core.md with YAML frontmatter and structured key-value fields. Every conversation reads that file first and proposes changes before writing, keeping the project definition consistent.

Voice transcription often mangles proper nouns like competitor names, URLs, and technical terms. The correct behavior is to ask the founder to clarify or spell the term rather than guessing and writing incorrect data into project files.

Store each hypothesis as a separate markdown file with YAML frontmatter containing a status field (untested, confirmed, invalidated), an H1 title stating the testable assumption, a type tag, and an optional notes section.

Dispatch a research subagent when the task goes beyond a quick search, such as competitive landscape discovery, problem space validation, or market signals. Save the research output as dated markdown files so expensive research is preserved for future reference.

No. The skill states there is no telemetry and nothing is sent automatically. The only external link is an optional, anonymous feedback form offered at specific milestones, and founders can opt out permanently.