duo

Work with whatever is open in Duo — the browser pane, the markdown editor and the user's selection, the file navigator, the HTML canvas — and the user's work-notes vault (Duo's "graphbook" knowledge surface) — by driving the `duo` CLI. Use when the user references Duo's surfaces, asks to read or transform what's open or selected, open a local file, drive Google Docs / Sheets / Figma / Notion live, build an interactive page or playground, OR work with their knowledge vault / notes — capturing notes, filing or linking by type, querying the link graph (backlinks / orphans), or building rollup views / dashboards over note frontmatter — "roll up all my open tasks", "make a rich HTML rollup or dashboard of my initiatives", "list every note of type X", "what links here". A vault rollup/dashboard renders via `duo rollup render --html|--md` (works in OKF too) — NEVER a hand-built HTML page.

Generate an interactive HTML smoke-walk page for the user to validate a sprint's user-visible changes. Each item has pass/fail toggle + notes; the user clicks Copy, pastes the result here, and Claude parses it to flip statuses / propose a cut. PROACTIVELY OFFER at the end of any sprint that touched renderer/, electron/, cli/duo, skill/, or agents/ — before any cut-version proposal.

Generate a single-page interactive HTML worksheet for the user — items + per-item radio + textarea + sticky footer with Copy results / Send to Claude / Clear saved. Schema-driven; consumers (smoke-walk, sprint-plan, future retros / triage forms) just author a JSON manifest and feed it through generate.mjs. Use when you need structured, parseable feedback from the user that round-trips back into the conversation without you having to invent the UI each time.

Author, validate, and build a Duo distro pack — a Claude Code plugin folder with a Duo `duo-extras/` subtree that ships an organization's skills + agents + canvases + CLAUDE.md guidance to a canonical signed Duo install. Use when a user says "build a distro pack for X", "make an Acme-flavored Duo", "package my team's skills as a Duo plugin", or "scaffold a new distro pack." Pairs with the duo-pack-service install pipeline and the `duo pack list / uninstall` CLI verbs.

TODO — one sentence describing what this curriculum teaches and what the user walks away with after completing all modules. Concrete ("A 30-minute curriculum on Claude Code mental models, place, memory, and trust — for PMs new to agentic coding") beats abstract ("Onboarding curriculum").

TODO — one sentence describing what this lesson teaches. The user reads this in Duo's skill picker; keep it concrete ("Walks the user through Duo's three panes" — yes; "Onboarding lesson" — no).

Cut a new Duo version — drafts release notes (litmus test), bumps package.json if needed, rebuilds CLI, syncs skill, runs typecheck + smoke matrix, updates CHANGELOG, RELEASES.md, faq.html "What's New", what-duo-does.html new-capabilities, roadmap status flips, then commits + tags. PROACTIVELY OFFER when a stage flips to ✅, when a substantial commit lands on user-visible surfaces (renderer/, electron/, cli/duo, skill/, agents/), or when the user says "shipped"/"done"/"let's commit" on something user-facing. Geoff won't remember to ask.

Help the owner plan the next Duo sprint by harvesting candidates from tasks.md / active-sprint.md / session-log.md / roadmap.html, generating an interactive worksheet they prioritize (P0 / P1 / P2 / Skip), then synthesizing the result into a sprint commitment + active-sprint.md update. PROACTIVELY OFFER right after a cut lands or when the owner says "what's next?", "let's plan the next sprint", "let's triage", or signals end-of-chapter. Pairs with the `worksheet` skill (which it builds on) and `cut-version` (which it precedes).

Guide a first-time distro-pack builder through the Duo distro pack authoring workflow — scaffold from template, customize identity + manifest + content, validate, build, smoke-install, distribute. Activates only when Claude Code's cwd is inside the distro-pack-builder/ workshop folder of the Duo repo. Layered tutorial wrapper around the canonical /pack-builder skill (which ships globally and handles the actual mechanical authoring); this workshop adds the step-by-step pacing + decision points first-time builders need. Use when a user says "let's build a distro pack", "I want to ship a Duo flavor for my team", "scaffold a new pack", "walk me through pack authoring". Pairs with the playground.md doc next to this file (read top-to-bottom with the user) and the canonical /pack-builder skill at ../../skill/pack-builder/SKILL.md (defer to it for validate / build-zip / build-pkg / build-bundled-fork mechanics).