bias-detection-design
Designing review workflows to surface and mitigate bias in AI outputs.
When the AI leads vs. when the user leads, and how to hand off control.
$ npx -y skills add owl-listener/ai-design-skills --skill mixed-initiative-flow --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/mixed-initiative-flowContext preview
The summary Claude sees to decide when to auto-load this skill.
When the AI leads vs. when the user leads, and how to hand off control.
name: mixed-initiative-flow description: When the AI leads vs. when the user leads, and how to hand off control.
Mixed-initiative interaction is when both the human and the AI can take the lead. The designer decides who drives at each moment — and how control transfers between them.
Interactions sit on a spectrum:
Most AI products default to user-driven. The interesting design space is in shared and AI-driven modes.
The moment control shifts from one party to the other is where most interactions fail. Design these transitions:
The AI should take initiative when:
The user should retain control when:
Part of the Designer Skills suite. Install this collection and four more with one command in Claude Code: /plugin marketplace add Owl-Listener/designer-skills This repo still works on its own. The suite just gives everyone one front door.
Designing review workflows to surface and mitigate bias in AI outputs.
Designing for informed user consent, opt-out, and human override.
When and how AI should escalate to humans, refuse, or ask for clarification.
Defining behavioral boundaries — what the AI should and shouldn't do.
Proactively identifying failure modes, misuse, and unintended consequences.
Showing users what the AI knows, doesn't know, and how confident it is.