om-ux-shape

Shape vague product and AI feature ideas into decided, implementation-ready directions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product, UI/UX, and AI feature ideas often arrive vague, overcomplicated, or unjustified, leading teams to build screens before deciding anything. This Skill turns that ambiguity into a concrete product decision with evidence, scope, states, and validation plans. ## Core Features & Use Cases - Three working modes: Shape a vague idea into a direction, Review an existing concept or flow with a keep/simplify/rethink/stop verdict, or produce a Handoff with behavior, states, and acceptance criteria for engineering. - AI necessity gate and human-AI guidelines: Decides whether AI belongs at all, chooses automation versus augmentation, and designs failure, control, and trust calibration before polish. - Evidence discipline and quality rubric: Separates known facts from assumptions, tags claims with evidence tiers, and blocks delivery when diagnosis, outcome, scope, or concreteness score zero. - Use Case: A PM asks whether to add an AI assistant to a settings page. The Skill runs the necessity gate, recommends a rules-based alternative, defines the smallest coherent feature with named screens and actual copy, and proposes the cheapest validation test. ## Quick Start Use om-ux-shape to turn this feature idea into a decided direction with scope, states, and a validation plan.

Frequently Asked Questions about om-ux-shape

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

FAQPage Schema
How do I turn a vague feature idea into a product decision?

Use Shape mode: it frames the actor, job, and friction, builds an evidence ledger separating facts from assumptions, compares two or three mechanisms, and recommends one direction with the decisive trade-off. The output includes scope split into now, later, and not doing.

How do I decide whether a feature should use AI?

The Skill runs an AI necessity gate that asks what problem exists independently of AI and whether a deterministic rule or conventional UI solves it more cheaply. It then chooses explicitly between no AI, rules first, AI-assisted, AI-collaborative, or AI-automated.

What is the difference between Shape, Review, and Handoff modes?

Shape turns a vague idea into a decided direction, Review evaluates an existing concept or flow with a keep, simplify, rethink, or stop verdict, and Handoff specifies behavior, states, and acceptance criteria once the direction is decided. Modes combine only when the request genuinely spans them.

Does this Skill write code or implement features?

No, it writes no code and touches no tracker items. Its Handoff output is written to be consumed by implementing skills or engineers, and it chains no further skills unless the user explicitly asks to continue into implementation.

When should I not use a full feature-shaping process?

Skip the full process for small, low-risk, reversible decisions, where the Skill scales down to a short answer with recommendation, assumptions, flow, scope, and next test. Depth follows risk, so consequential or novel work gets the complete workflow.