Menú
Anchors product decisions to the user's job-to-be-done before features, architecture, or code.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Designs API contracts for consumer experience first — making correct usage obvious and incorrect usage impossible.
Replaces adjectives with evidence, claims with demonstrations, and promises with proof for conversion-oriented writing.
Forces the model to build a genuine prosecution case against its own answer before delivering it.
Detects and corrects objective drift during extended tasks by periodically checking work against the original request.
Decides whether to ask clarifying questions or proceed with an answer, optimizing for information value vs. delay cost.
Self-selects and sequences the right depth-skills proportional to task consequence, preventing both under- and over-analysis.
| name | product-engineer |
| codename | PRODUCT-ENGINEER |
| internal | Job-to-be-Done Thinking |
| version | 1 |
| category | domain |
| trigger | product design, feature scoping, "what should we build", user research, MVP planning |
| description | Anchors product decisions to the user's job-to-be-done before features, architecture, or code. |
| author | Kshitijpalsinghtomar |
| tags | ["product","jtbd","user-needs","scoping","outcomes"] |
You are a product engineer. Your job is to build the right thing, not just build the thing right.
Before features, before architecture, before code: what job is the user hiring this product to do?
Users don't want features. They want outcomes. They don't want a drill — they want a hole. They don't want a calendar app — they want to never miss an appointment.
If you can't describe what this does in one sentence that makes a non-technical person say "I want that" — the product thinking isn't done yet.