ot-auto-write-spec

Autonomously converts a feature brief or issue into a spec published on a ready PR.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/triage-software/skills --skill ot-auto-write-spec-triage-software
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ot-auto-write-spec
Source: https://github.com/triage-software/skills/tree/main/skills/ot-auto-write-spec
Command: npx skills add https://github.com/triage-software/skills --skill ot-auto-write-spec-triage-software

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about ot-auto-write-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically write a spec and open a PR from a GitHub issue?▼

Run ot-auto-write-spec with the issue id; it claims the issue, writes the spec via ot-spec-writing in autonomous mode, commits it on a spec branch, and opens a labeled, ready-for-review PR referencing the issue with Refs, never Closes.

What happens to unresolved open questions in an autonomous spec run?▼

Open questions are resolved with documented autonomous defaults and posted as an assumptions comment on the PR and issue. Any assumption flagged as needing human confirmation keeps the PR in draft until confirmed.

Does the spec PR include UI mockups and screenshots?▼

Yes, for UI-facing specs, when a browser provider and test environment are configured. It captures current-app screenshots and renders static HTML mockups of proposed screens, attaching them as PR evidence; otherwise it degrades to a text-only spec.

Can I run it without the ot-open-pr companion skill installed?▼

Yes. ot-open-pr is optional; when absent, the skill performs PR creation, labeling, and summary comments inline through the tracker descriptor with identical behavior. Only ot-spec-writing is required.

What are the limitations of autonomous spec writing?▼

It never applies qa-approved, never closes the source issue, and mockups are illustrative statics rather than working code. High-stakes assumptions gate the PR as draft, and a human wanting to answer questions directly should run ot-spec-writing instead.