spec-gen

Start or resume a spec refinement workflow — converts a vague idea into an implementation-grade specification through structured interview, research, and iterative refinement.

Reads all research artifacts (NOTION.md, SLACK.md, WEB.md) and produces a concise DISTILLED_CONTEXT.md containing only decision-relevant facts, constraints, prior decisions, and open questions. Surfaces conflicts between sources.

Searches a Notion workspace for context relevant to a specification being refined. Prioritizes task databases and sprint pages based on detected keywords, then broadens to a general workspace search because information may be scattered.

Continuously reconciles the evolving spec against open questions. Reads the current SPEC.md and OPEN_QUESTIONS.md, marks answered questions as resolved, and adds newly discovered questions. Maintains OPEN_QUESTIONS.md as the authoritative list.

Searches Slack channels and threads for context relevant to a specification being refined. Performs broad search across accessible channels with a default 3-month window, expanding if results are sparse or context clearly predates that window.

Researches patterns, best practices, common gotchas, and prior art on the web for topics relevant to a specification being refined. Focuses on actionable technical guidance, not general overviews.

Use when the user starts a new feature, project, or task with a vague or incomplete goal. Use when the user says "refine a spec", "help me define requirements", "I have an idea", "let's spec this out", "what should we build", or invokes /spec-gen:refine. This skill enforces a structured refinement workflow that converts an amorphous idea into an implementation-grade specification with explicit constraints, tracked unknowns, and cited context — before any code is written.