
mixed-initiative-flow
When the AI leads vs. when the user leads, and how to hand off control.
- Installs
- 284
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/owl-listener/ai-design-skills --skill mixed-initiative-flow- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads mixed-initiative-flow automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Mixed-Initiative Flow
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.
Initiative Spectrum
Interactions sit on a spectrum:
- User-driven: The user gives instructions, the AI executes. The user controls pace, direction, and scope.
- AI-driven: The AI leads — asking questions, making suggestions, guiding the user through a process.
- Shared: Both parties contribute. The AI proposes, the user edits. The user starts, the AI finishes. Most AI products default to user-driven. The interesting design space is in shared and AI-driven modes.
Designing Initiative Handoffs
The moment control shifts from one party to the other is where most interactions fail. Design these transitions:
- Explicit handoff: "I've drafted three options. Which direction do you want to go?" — the AI clearly passes control.
- Implicit handoff: The AI stops generating and waits, signalling the user's turn through UI affordance.
- Negotiated handoff: "I could take this further or stop here for your input. What do you prefer?"
- Forced handoff: The AI encounters a decision it can't make and must hand back to the human.
When the AI Should Lead
The AI should take initiative when:
- The user is uncertain or exploring and needs guidance
- The task has a known best-practice sequence the AI can walk through
- The user has explicitly asked for help or coaching
- Proactive suggestions would save time without being intrusive
When the User Should Lead
The user should retain control when:
- The task involves subjective judgment or creative direction
- Stakes are high and errors are costly
- The user has strong domain expertise
- Privacy or consent decisions are involved
Anti-Patterns
- Initiative whiplash: Control bouncing back and forth too rapidly
- Passive AI: Never taking initiative even when it would help
- Overbearing AI: Taking over when the user wants control
- Unclear ownership: Neither party knows whose turn it is
Design Artefacts
- Initiative maps showing who leads at each stage
- Handoff trigger definitions (what causes a transfer of control)
- Autonomy level specifications per feature area
FAQ
What does the mixed-initiative-flow skill do?
When the AI leads vs. when the user leads, and how to hand off control.
How do I install mixed-initiative-flow?
Run npx skills add https://github.com/owl-listener/ai-design-skills --skill mixed-initiative-flow in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/mixed-initiative-flow/ (personal) or .claude/skills/mixed-initiative-flow/ (project).
Which AI agents can use mixed-initiative-flow?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is mixed-initiative-flow safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains mixed-initiative-flow?
It is published by owl-listener in owl-listener/ai-design-skills. It has 284 recorded installs.
More from owl-listener/ai-design-skills
system-prompt-structure
owl-listener/ai-design-skills
Anatomy of effective system prompts — role, context, constraints, format.
guardrail-design
owl-listener/ai-design-skills
Defining behavioral boundaries — what the AI should and shouldn't do.
constraint-specification
owl-listener/ai-design-skills
Defining output format, length, tone, and content boundaries within prompts.
generative-ui
owl-listener/ai-design-skills
Designing interfaces where AI generates UI components dynamically.
conversation-patterns
owl-listener/ai-design-skills
Turn-taking, repair sequences, grounding, and dialogue structure for human-AI interaction.
progressive-disclosure
owl-listener/ai-design-skills
Revealing AI capability gradually to match user mental models.
Popular other skills
hyperframes-cli
heygen-com/hyperframes
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
triage
mattpocock/skills
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
ask-matt
mattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
to-questionnaire
mattpocock/skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
loop-me
mattpocock/skills
Grill me about specs for the workflows I want to build, within this workspace.