dcode:jtbd-prd-frame

Reframe PRDs from feature-centric to user-job-centric perspectives.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/madebynoam/dcode --skill dcode-jtbd-prd-frame
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dcode:jtbd-prd-frame
Source: https://github.com/madebynoam/dcode/tree/main/plugins/jtbd/skills/jtbd-prd-frame
Command: npx skills add https://github.com/madebynoam/dcode --skill dcode-jtbd-prd-frame

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams align on product development by reframing feature definitions and PRDs around the user's actual job-to-be-done, rather than the feature itself, ensuring development efforts directly address user needs.

Core Features & Use Cases

  • Job Statement Creation: Articulates the user's goal using the "When I'm... I want to... so I can..." framework.
  • PRD Reframing: Transforms feature-centric language in titles, problems, and success metrics into job-centric equivalents.
  • Placement Guidance: Helps determine the correct product placement for features based on the user job they serve.
  • Use Case: Before starting development on a new "Referrals Page," use this Skill to define the underlying job: "When I'm onboarding a new client, I want to send them a referral link so I can earn commission and they get set up."

Quick Start

Use the dcode:jtbd-prd-frame skill to reframe the feature idea "Referrals page" around the user's job.

Frequently Asked Questions about dcode:jtbd-prd-frame

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a jobs-to-be-done framework for product requirements?

A jobs-to-be-done PRD frame shifts product requirements from feature-centric language to user-job-centric goals, ensuring development efforts directly address core user needs rather than just building features.

How do I write user stories using the jobs-to-be-done structure?

You write user stories using the jobs-to-be-done structure by articulating the user's goal with the "When I'm... I want to... so I can..." format, which clarifies the context, action, and expected outcome for feature definition.

How do I reframe a feature-centric PRD into a user-job-centric perspective?

To reframe a feature-centric PRD, transform the titles, problem statements, and success metrics into job-centric equivalents by defining the underlying user job first, then guiding feature placement based on that job alignment.

Can I use this job-to-be-done framing for product scoping and feature placement?

Yes, this framing supports product scoping by guiding feature placement based on the specific user job alignment, helping teams determine where features belong within the product workflow.

When should I shift product management focus from features to user jobs?

You should shift focus to user jobs when feature definitions fail to address user needs directly, using job statements to align product management and design efforts with actual user goals before development.