ui-to-issues

Convert UI specs and redline audits into GitHub issue drafts.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/ThorStarlord/interface-skills --skill ui-to-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-to-issues
Source: https://github.com/ThorStarlord/interface-skills/tree/main/skills/ui-to-issues
Command: npx skills add https://github.com/ThorStarlord/interface-skills --skill ui-to-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Converts UI spec packages, redline audits, and acceptance checklists into discrete, independently implementable GitHub issue drafts so teams and agents can execute without rereading entire specs.

Core Features & Use Cases

  • Vertical-slice implementation planning: Breaks work into user-verifiable outcomes end-to-end rather than horizontal “touch points” across layers.
  • Redline-to-issue coverage mapping: When inputs come from a UI redline audit, produces a complete coverage table that assigns each redline item to a specific issue, deferred state, justification, or not-applicable outcome.
  • Actionable issue drafts with verification: Each issue includes scope, requirements, acceptance-derived criteria, spec links, and a clear “How to verify” step.

Quick Start

Ask the agent to run ui-to-issues using your acceptance.md (or a redline-audit.md plus the full spec package) to produce a vertical-slice Markdown implementation plan as a set of issue drafts.

Frequently Asked Questions about ui-to-issues

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

FAQPage Schema
How do I turn UI specifications into GitHub issues?

To turn UI specifications into GitHub issues, you provide the agent with your acceptance.md or redline-audit.md to generate vertical-slice Markdown issue drafts containing scope, requirements, and acceptance criteria.

How do I map redline audit items to actionable issues?

Mapping redline audit items to actionable issues requires providing the full spec package and audit file, which produces a complete coverage table assigning each redline item to a specific issue, deferred state, or not-applicable outcome.

What is vertical-slice implementation planning for UI specs?

Vertical-slice implementation planning for UI specs breaks work into user-verifiable outcomes end-to-end rather than horizontal touch points across layers, ensuring each issue is independently implementable.

Can I generate acceptance criteria from a UI spec package?

Yes, you can generate acceptance criteria from a UI spec package by processing it into issue drafts that derive verification steps and required spec-linked references directly from the provided artifacts.

Do I need a full spec package to plan post-redline remediation?

Yes, post-redline remediation planning requires the full spec package alongside the redline-audit.md to enforce a complete coverage map and generate accurate, independently implementable GitHub issue drafts.

What is the best way to create sprint tasks from UI redlines?

The best way to create sprint tasks from UI redlines is processing the audit inputs to produce a Markdown implementation plan, grouping items into vertical slices with clear How to verify steps.