om-auto-implement-spec

Implements an existing spec into a reviewed, UI-verified 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-implement-spec-go-musicfox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: om-auto-implement-spec
Source: https://github.com/go-musicfox/go-musicfox/tree/main/.agents/skills/om-auto-implement-spec
Command: npx skills add https://github.com/go-musicfox/go-musicfox --skill om-auto-implement-spec-go-musicfox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning an approved design spec into working code normally requires manually coordinating branches, PRs, code review, and UI verification. This Skill automates that entire handoff: it resolves a spec by path, name, issue, or spec-PR number, delegates implementation to engine skills, and returns a ready, reviewed PR with screenshots of the working app. ## Core Features & Use Cases - Spec Resolution: Locates the spec from a repo-relative path, name/slug, issue id, or spec-PR number, stopping cleanly with candidate suggestions when nothing matches. - Engine Delegation: Routes fresh work to om-auto-create-pr (or its loop variant for long plans) and resumes existing implementation PRs via om-auto-continue-pr, never duplicating PRs. - UI Verification: Runs om-auto-qa-pr on user-facing changes to boot the app, drive changed flows, and attach screenshot evidence to the PR. - Use Case: After a teammate merges a spec PR for a new settings page, you tell the agent to implement that spec; it opens a separate implementation PR referencing the spec PR, runs validation and review loops, and posts screenshots proving the page works. ## Quick Start Ask the agent to implement the spec at .ai/specs/2024-05-01-settings-page.md and ship it as a verified pull request.

Frequently Asked Questions about om-auto-implement-spec

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

FAQPage Schema
How do I implement a spec into a pull request automatically?

Pass the spec as a repo-relative path, name, issue id, or spec-PR number. The skill resolves it, invokes om-auto-create-pr or om-auto-continue-pr to build the implementation, then runs review and UI verification before reporting the ready PR.

What happens when the spec cannot be found?

The run stops cleanly with a blocked status and lists the closest candidate specs it searched. It never guesses or writes a spec itself; creating specs is the job of om-auto-write-spec.

Does the implementation land on the spec PR branch?

No. The spec PR stays design-only. Implementation always ships on its own separate PR that references the spec PR with a Refs line and a Source doc line, keeping exactly one implementation PR per spec.

Can I skip UI verification for backend-only changes?

Yes. Pass the --no-ui flag to skip end-of-run UI verification, or let the skill detect a purely backend, API, or docs change and mark UI verification as not applicable in its report.

What if an implementation PR for the spec already exists?

The skill resumes the existing PR via om-auto-continue-pr instead of opening a duplicate. It detects the PR by searching for the Source doc path or spec PR reference in open pull requests.