What problem does it solve? Writing a design spec and getting it in front of reviewers involves drafting the document, resolving open questions, creating a branch, opening a PR, applying labels, and attaching visual evidence — a repetitive pipeline this Skill runs unattended end to end. ## Core Features & Use Cases - Autonomous spec authoring: Delegates document writing to ot-spec-writing --autonomous, resolving open questions with documented defaults and surfacing every assumption for override. - Full PR publication: Creates an isolated worktree and spec/<slug> branch, commits the spec, opens a ready-for-review PR with SDLC labels, and posts resolved-assumptions and run-summary comments. - Visual evidence for UI specs: Captures current-app screenshots and renders static HTML mockups of proposed UI, attaching them to the PR when a browser provider is configured. - Use Case: Point it at a feature request issue ("spec this issue") and return to a published spec PR with mockups, labels, and chaining markers ready for ot-auto-implement-spec. ## Quick Start Ask the agent to write a spec for a feature brief or tracker issue and open a PR, for example: run ot-auto-write-spec on issue 42 to produce a spec PR.