/feature-design
Plan a feature's design before anyone builds it.
(What it does)
Structured design thinking for a new feature. /feature-design takes a problem statement and works out the shape of the solution: a step-by-step user flow with the reason for each step, component choices compared with world-class products, a CRISP check on every step, and the open questions to answer before anyone builds.
It does not generate wireframes. Every decision is justified against a CRISP dimension, and any step that fails one is flagged with a proposed fix before the design moves on.
(When to use it)
Use it at the start of feature work, before any code:
- A product brief or user problem needs turning into a designed flow
- You are about to replace a manual workaround with a real feature
- An AI agent is about to build a feature and you want the design decided first, not improvised mid-build
- You have
/crisp-researchoutput and want to turn it into a design
(What you get)
- User flow with the reason for each decision
- A CRISP check on every step
- Component recommendations
- Questions to test with research
(Example output)
✓ Seamless
⚠ Avoid if possible
Illustrative example only. This is not a real audit.
(What it refuses to skip)
It frames the problem first. If these questions are unanswered, it asks them before designing anything:
- Who has this problem: their role, experience level, and situation
- What they are trying to do: the job, not the feature
- What they do today: the workaround this replaces
- What success looks like: an outcome you can observe, not "feature shipped"
- What constraints exist: technical, timeline, or design system
(Common questions)
Does it produce wireframes or mockups?
No. It produces the thinking a wireframe should be based on: flows, states, component choices, edge cases, and reasons. Pair it with /handoff to turn the approved design into a spec developers can build from.
What if I only have a vague idea?
Run /crisp-brief first. It turns a vague request into a scoped .brief.md, which /feature-design reads alongside .crisp.md. Starting from a clear brief means you design for a real problem, not an assumption.
How does it use /crisp-research output?
Directly. The patterns, benchmarks, and open questions from /crisp-research are formatted to paste into /feature-design, so the design starts from evidence of how world-class products solve the same problem.
What does the CRISP compliance summary add?
Every step of the flow is checked against the five dimensions, and risks are named. This catches a classic feature design failure before it is built: a flow that works when everything goes right, but fails Contextual in the empty state or Responsive under load.
(Install)
Installs all fourteen CRISP skills and detects which AI coding tool you use. Run /crisp-teach once per project, before the other skills.
(Related skills)