duet
Two-party posture — user as director, agent as executor; every fork, tradeoff, or choice surfaced via batched AskUserQuestion with a recommended default. Use when the user invokes /duet, says "ask before" / "pair with me" / "human-in-the-loop", or for aesthetic/architectural/irreversible decisions.
npx skills add majiayu000/claude-skill-registry --skill duet --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Duet Two-party working posture: **user is the director, agent is the executor.** ## Why this exists Working with agents has two chronic failure modes: 1. **Review bottleneck** — the agent does everything, the user becomes a reviewer of a giant diff at the end. Review is slow, exhausting, and frequently misses things the user would have caught at the moment of the choice. 2. **Codebase-understanding debt** — when the agent silently picks architecture, libraries, boundaries, and names on the user's behalf, the user ends up *owning code they do not understand*. The debt compounds: every future change requires the user to re-learn what the agent decided for them. Duet addresses both by doing one simple thing: **surface every genuine fork as a pick, in plain structural language, at the moment of the decision.** Review gets distributed across the task — there is no giant diff at the end because every call was already consented to. And because the *user* picked, the user *remembers* — the mental model is built as the code is built, not reconstructed afterward. This is the load-bearing principle. Everything below is mechanics. ## Role inversion - **Agent** → executor. Carries the jargon,
- Why this exists
- Role inversion
- Antipatterns and shape discipline [LOAD-BEARING]
- VS-gated question protocol [MANDATORY]
- When it applies
- The three-phase loop
- Phase 1 — Intent elicitation (adaptive)
- Phase 2 — Execution with fork-surfacing
- Phase 3 — Irreversible checkpoints
- Fork taxonomy
- Presentation protocol
- Batching rules
- Failure modes and antidotes
- Anti-patterns (do not do)
What does the duet skill do?
Two-party posture — user as director, agent as executor; every fork, tradeoff, or choice surfaced via batched AskUserQuestion with a recommended default. Use when the user invokes /duet, says "ask before" / "pair with me" / "human-in-the-loop", or for aesthetic/architectural/irreversible decisions.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill duet --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.