How do I install the Duo Product skill?

Run npx skillmds@latest add hktitan/duo-product in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Duo Product safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Duo Product?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Duo Product free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Duo Product?

HKTITAN (@hktitan) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Duo Product by hktitan — Agent Skill

Name: Duo Product
Author: HKTITAN

Duo Product

Make product decisions the way Duolingo does — long-view over short-term, ruthless prioritization, ship-and-learn over plan-and-ship, dogfooding, and the "intuitive by default" quality bar. Use when the user is roadmapping, deciding what to cut, debating whether to ship, defining a quality bar for a feature, or trying to install a "product-led" culture in a team that defaults to feature factories. Source the Duolingo Handbook principles 1, 2, and 3 (Take the Long View, Raise the Bar, Ship It).

HKTITAN Updated Sep 17, 2026

File contents

Duolingo Product — Map of Content

Three of the five handbook principles describe how Duolingo decides what to build and what good looks like. This skill collects the decision rules so a small team can borrow the operating system without copying the product.

This skill is structured as a graph: scan the descriptions below, follow only the [[wikilinks]] you need.

The three decision lenses

[[references/take-the-long-view]] — Principle #1: if it helps short-term but hurts long-term, it's not right.
[[references/raise-the-bar]] — Principle #2: every feature must be intuitive, delightful, useful, and polished.
[[references/ship-it]] — Principle #3: clock-speed, ruthless prioritization, kill what isn't working.

Long-view applied

[[references/hundred-year-brand]] — the asset class the long view is investing in.
[[references/intuitive-by-default]] — products shouldn't have to explain themselves.

Bar-raising applied

[[references/dogfooding]] — using the product daily as a quality forcing function.
[[references/polish]] — what "polished" actually means in review, with concrete tests.
[[references/ownership-clarity]] — every critical task has one owner; ambiguous ownership is the bug.

Ship-it applied

[[references/ruthless-prioritization]] — how to cut, not how to fit more in.
[[references/kill-criteria-product]] — the rules for stopping a project, not just an experiment.

Sibling skills

[[../duo-retention/SKILL]] — the long view is a retention bet; nodes interlock.
[[../duo-experimentation/SKILL]] — Ship It runs on the Show Don't Tell protocol.
[[../duo-culture/SKILL]] — Raise the Bar is a hiring problem before it's a product problem.

Sources

Duolingo Handbook (2025), Principles #1–3

---name: duo-productdescription: Make product decisions the way Duolingo does — long-view over short-term, ruthless prioritization, ship-and-learn over plan-and-ship, dogfooding, and the "intuitive by default" quality bar. Use when the user is roadmapping, deciding what to cut, debating whether to ship, defining a quality bar for a feature, or trying to install a "product-led" culture in a team that defaults to feature factories. Source the Duolingo Handbook principles 1, 2, and 3 (Take the Long View, Raise the Bar, Ship It).license: MIT---# Duolingo Product — Map of ContentThree of the five handbook principles describe how Duolingo *decides what to build* and *what good looks like*. This skill collects the decision rules so a small team can borrow the operating system without copying the product.This skill is structured as a **graph**: scan the descriptions below, follow only the `[[wikilinks]]` you need.## The three decision lenses- [[references/take-the-long-view]] — Principle #1: if it helps short-term but hurts long-term, it's not right.- [[references/raise-the-bar]] — Principle #2: every feature must be intuitive, delightful, useful, and polished.- [[references/ship-it]] — Principle #3: clock-speed, ruthless prioritization, kill what isn't working.## Long-view applied- [[references/hundred-year-brand]] — the asset class the long view is investing in.- [[references/intuitive-by-default]] — products shouldn't have to explain themselves.## Bar-raising applied- [[references/dogfooding]] — using the product daily as a quality forcing function.- [[references/polish]] — what "polished" actually means in review, with concrete tests.- [[references/ownership-clarity]] — every critical task has one owner; ambiguous ownership is the bug.## Ship-it applied- [[references/ruthless-prioritization]] — how to cut, not how to fit more in.- [[references/kill-criteria-product]] — the rules for stopping a project, not just an experiment.## Sibling skills- [[../duo-retention/SKILL]] — the long view *is* a retention bet; nodes interlock.- [[../duo-experimentation/SKILL]] — *Ship It* runs on the *Show Don't Tell* protocol.- [[../duo-culture/SKILL]] — *Raise the Bar* is a hiring problem before it's a product problem.## Sources- Duolingo Handbook (2025), Principles #1–3

Frequently asked questions