Spec Kit should plan the UX in separate file

[anggaaryas]

In current implementation, we don't know how the new feature will be integrated with existing project. I want to review the UI UX first before generate task list. Like the entry point, design decision, etc.

[mnriem]

@anggaaryas My suggestion would be to review the spec and the plan and if needs be use clarify or checklistcommand or if that does not fit the build you could create an extension with a custom command that caters specifically to what you are looking for. If you do end up creating an extension for this please have it listed in the community catalog

[Quratulain-bilal]

This is a valid gap. Right now the flow goes specify → plan → tasks → implement, but there's no dedicated
step where you can visualize how the feature integrates with existing UI before committing to a task
breakdown.

A ux-review extension could generate a lightweight integration map — which screens are affected, what
entry points exist, and what the user flow looks like as a separate artifact before /speckit.tasks
runs.

The /speckit.clarify command helps with requirements, but it doesn't produce a visual or structural
output focused specifically on UI integration. A dedicated command for this would make the review step
concrete rather than implicit.

If anyone builds this, listing it in the community catalog would make it discoverable for the whole
community.