What problem does it solve? After a design conversation, teams still need a written specification that lives in one authoritative place. This Skill turns the current conversation into a structured spec and publishes it, either as a tracker issue or as proposals in Spec Universe, without re-interviewing the user. ## Core Features & Use Cases - Spec synthesis from context: Reads the existing conversation and codebase state to produce a specification with problem statement, user stories, implementation and testing decisions, and scope boundaries. - Dual publish modes: Detects the spec_product key in .harness-version and either publishes a tracker issue (dormant mode) or writes node proposals to Spec Universe via the shared client script (connected mode). - Conflict sweep: In connected mode, lists every existing spec node the change touches or contradicts, ordered by strictness, and routes contradictions through a documented conflict protocol before drafting. - Use Case: After a /grilling design discussion about a new feature, run this Skill to produce the spec, sweep for conflicts against existing requirements, and publish proposals keyed to the change so later phases like /to-tickets and /release can consume them. ## Quick Start Ask the assistant to turn the current design conversation into a specification and publish it using the to-spec skill.
