om-auto-write-spec

Autonomously converts a feature brief or issue into a spec document published on a ready pull request.

2.6k|159|Updated Mar 8, 2021
One-click install
npx skills add https://github.com/go-musicfox/go-musicfox --skill om-auto-write-spec-go-musicfox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: om-auto-write-spec
Source: https://github.com/go-musicfox/go-musicfox/tree/main/.agents/skills/om-auto-write-spec
Command: npx skills add https://github.com/go-musicfox/go-musicfox --skill om-auto-write-spec-go-musicfox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a rough feature brief or tracker issue into a reviewed, mergeable specification normally requires manual writing, branch management, PR creation, labeling, and evidence gathering. This Skill automates that entire pipeline so a user can start an unattended run and return to a published spec PR. ## Core Features & Use Cases - Autonomous spec authoring: Delegates document writing to om-spec-writing in --autonomous mode, resolving open questions with documented default assumptions posted for human override. - Full PR lifecycle: Creates an isolated git worktree and spec branch, commits the spec, opens a ready-for-review PR with SDLC labels, and emits machine-parseable chaining markers for follow-on implementation skills. - Visual evidence: For UI-facing specs, captures current-app screenshots and renders static HTML mockups attached to the PR as evidence. - Use Case: A product engineer files a feature request issue; the run claims the issue, writes the spec, attaches mockups, opens a labeled spec PR referencing the issue, and hands off to om-auto-implement-spec. ## Quick Start Ask the agent to write a spec for issue 42 and open a PR for it using om-auto-write-spec.

Frequently Asked Questions about om-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 an issue?

Run om-auto-write-spec with the issue id; it claims the issue, invokes om-spec-writing in autonomous mode to draft the spec, commits it on a spec branch, and opens a labeled ready-for-review PR referencing the issue.

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

Open questions are resolved with conservative documented defaults recorded in a Resolved Assumptions section and posted as an override-invitation comment on the PR. Any assumption flagged as needing human confirmation keeps the PR as a draft.

Does om-auto-write-spec require om-open-pr to be installed?

No, om-open-pr is optional. When it is absent, the skill falls back to inline PR creation through the tracker descriptor's create-pr operation, producing the same PR, labels, and summary comments.

Can the skill generate UI mockups without a browser provider?

No. Mockups and current-app screenshots require the om-prepare-test-env descriptor plus a configured browser provider. When either is missing, the skill skips visuals, notes the reason in the PR body, and still delivers a text-only spec PR.

Why does the spec PR use Refs instead of Closes for the issue?

The spec PR is design-only, so merging it must not close the feature request. It uses Refs #issueId to link the issue while leaving closure to the later implementation PR produced by om-auto-implement-spec.