wtf.design-feature

Plan holistic feature designs and write Design Handoff into the Feature issue.

7|2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/xiduzo/wtf --skill wtf-design-feature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wtf.design-feature
Source: https://github.com/xiduzo/wtf/tree/main/skills/wtf.design-feature
Command: npx skills add https://github.com/xiduzo/wtf --skill wtf-design-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designers need to produce a holistic design for a full feature before breaking it into tasks, ensuring a complete design handoff and stable scope for downstream work.

Core Features & Use Cases

  • Holistic feature design covering all user stories, screens, and cross-screen states, and writing the Design Handoff back into the Feature issue.
  • Supports integration with design tokens, design system patterns, and Gherkin-aligned acceptance criteria for downstream task creation.
  • Use Case: A designer receives a feature request and runs this skill to generate a full design handoff, ensuring all edge cases and domain events are represented.

Quick Start

Create a complete feature design handoff by outlining the full user journey and updating the Feature issue.

Frequently Asked Questions about wtf.design-feature

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

FAQPage Schema
How do I create a complete design handoff for a full feature before breaking it into tasks?

To create a design handoff, outline the full user journey across all screens and states, then write the handoff back into the Feature issue to stabilize scope for downstream tasks.

What is holistic feature design and when do I need it for UX handoff?

Holistic feature design covers all user stories, screens, and cross-screen states from discovery through handoff. You need it to ensure edge cases and domain events are fully represented before task creation.

How do I ensure my UX design covers all edge cases and domain events for downstream development?

Validate coverage by applying accessibility constraints and design tokens from the steering doc, ensuring all cross-screen states and domain events are represented before finalizing the feature design.

Can I integrate design system patterns and tokens into my feature design handoff?

Yes, you can leverage design tokens and design system patterns directly from the steering doc, aligning the feature design with Gherkin-aligned acceptance criteria for downstream task creation.

Do I need Gherkin acceptance criteria to generate a design brief for the Definition of Ready?

You do not need Gherkin criteria to generate briefs, but integrating them ensures the feature design supports the Definition of Ready and aligns downstream task creation with domain events.

What is the best way to transition from feature discovery to actionable development tasks?

The best way is to execute a holistic feature design that validates coverage across all user stories, then generate scaffold briefs and write the handoff back into the Feature issue.