UX Prototyping for user validation prior to /plan & /tasks?

[craigkitterman]

I love spec kit. It's a great tool but the one step that seems to be really missing from this workflow from a modern product perspective is the UX prototype. Going through the standard steps for a complex feature is going to require a LOT of code to be written before even getting a first look at UX. We need a simple command to generate clickable prototypes (using existing app UX patterns) that we can put in front of users, test all user stores and refine - baking that feedback back into spec.md before moving forward in the workflow.

Has anyone built this? What are the best practices? Ideally this /ux-prototype command can take user feedback and just re-crank new UI daily baking in the latest feedback, and output artifacts that can be used by /plan and /tasks for building final full-fledged implementation. Thoughts?

[wilsonneto-swe]

Exploring it in small projects, one way was to handle the PoC (or prototype) as one separate spec-kit feature.

[craigkitterman]

Yes, that is what I have been doing too. Sure would be nice to just have this part of the normal workflow.