Compatibility entrypoint for the Shape UX Requirements skill bundle. Use for end-to-end enterprise UX requirement shaping that spans requirement baseline, happy-path review, ASCII interaction design, and final specification delivery. For one bounded phase,…
Turn shaped and confirmed UX requirements into atomic specifications, acceptance criteria, traceability, reader-first Markdown artifacts, validation results, and final review/handoff. Use for final document composition or auditing existing deliveries. Do not…
Turn confirmed requirements and happy paths into information architecture, task and decision flows, interaction logic, and progressively confirmed ASCII UI/state contracts. Use for UX structure and behavior, not visual styling or final specification packaging.
Derive and challenge primary successful user paths from a confirmed or explicitly provisional requirement/story baseline. Use for first-principles happy-path analysis, adversarial review, branch inventory, and DEC-HAPPY confirmation. Do not design pages,…
Assess raw or revised enterprise product input against repository and source evidence, then shape problem framing, users, scenarios, concepts, scope, requirements, and stories into a confirmable baseline. Use before happy paths or interface design. Do not…
Orchestrate end-to-end enterprise UX requirement shaping across evidence-grounded baseline confirmation, happy-path review, ASCII interaction design, and final specification delivery. Use when a request spans multiple phases or needs one coordinated artifact.…