skills.rest
akornmeier
akornmeierCOMMUNITY
Explore all skills by this author →
𝕏@akornmeierGitHub

openspec-to-prompts

Convert OpenSpec change phases into PRD, UX, and build prompts.

4|Updated Nov 16, 2025
Search Tags:#UX#PRD#pipeline#prompts#openspec#build-prompts
One-click install
npx skills add https://github.com/akornmeier/claude-config --skill openspec-to-prompts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-to-prompts
Source: https://github.com/akornmeier/claude-config/tree/main/skills/openspec-to-prompts
Command: npx skills add https://github.com/akornmeier/claude-config --skill openspec-to-prompts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill translates OpenSpec change phases into actionable UI build prompts, enabling teams to move from specification to implementation with a repeatable, guided pipeline.

Core Features & Use Cases

  • Orchestrated 3-step pipeline: PRD generation, UX specification, and build prompts ready for UI tooling.
  • Input-driven workflow: Requires an OpenSpec change-id and phase number to tailor prompts to the exact feature phase.
  • Use Case: When starting a new OpenSpec feature phase, run this skill to produce a PRD draft, a UX spec, and a set of build prompts for frontend implementation.

Quick Start

Run the openspec-to-prompts workflow by providing a change-id and phase, e.g., change-id "add-launch-features" and phase "2".

Frequently Asked Questions about openspec-to-prompts

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

FAQPage Schema
How do I convert an OpenSpec change phase into UI build prompts?▼

To convert an OpenSpec change phase into UI build prompts, you run a three-step pipeline that processes your change-id and phase number to generate a PRD draft, a UX specification, and actionable build prompts.

What inputs do I need to generate UX and PRD documents from OpenSpec?▼

Generating UX and PRD documents from OpenSpec requires two specific inputs: an OpenSpec change-id, such as "add-launch-features", and a phase number corresponding to the exact feature phase you are implementing.

What is the OpenSpec to UI prompts pipeline used for?▼

The OpenSpec to UI prompts pipeline is used for translating feature specifications into actionable frontend implementation tasks, enabling teams to move from specification to implementation with a repeatable PRD and UX workflow.

When should I run the OpenSpec pipeline for build prompts?▼

You should run the OpenSpec pipeline for build prompts when you are starting a new OpenSpec feature phase and need to convert a specification into a PRD draft, a UX spec, and build prompts ready for UI generation tools.

Does the OpenSpec build prompt pipeline work without a phase number?▼

No, the OpenSpec build prompt pipeline does not work without a phase number, because it requires both a change-id and a phase number to tailor the generated PRD and UX prompts to the exact feature phase.

Related Skills

Explore More Software Engineering Skills→
tenondecrpctenondecrpc
3

openspec-propose

Generate change proposals with design, specifications, and implementation tasks.

Community
Advanced
akornmeierakornmeier
4

ux-spec-to-prompts

Convert UX specifications into self-contained prompts for UI generation tools.

Community
Advanced
hasnahasna

shadcn

Integrates reusable UI components into your Tailwind and React projects via the managed screen reader.

Official
Intermediate
gustavscirulisgustavscirulis
114

implementation-spec

Generate PRD, Architecture, UX/UI, Implementation, Test, and Release documents from a product plan.

Community
Advanced