Define Product

Analyze repositories to generate user-centric product.md documentation with personas and journeys.

1|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/yangsi7/skill-builder --skill define-product
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Define Product
Source: https://github.com/yangsi7/skill-builder/tree/main/.claude/skills/define-product
Command: npx skills add https://github.com/yangsi7/skill-builder --skill define-product

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires project-intel.mjs, AskUserQuestion, Read, Write, and includes examples (resource) components.

What problem does it solve?

This Skill addresses vague product definitions that lack user focus, often leading to misaligned development and wasted effort. It ensures your product strategy is grounded in clear user needs and pain points, providing a solid foundation for development.

Core Features & Use Cases

  • Intelligence-First Product Discovery: Analyzes your codebase and documentation to infer product characteristics, user signals, and existing patterns.
  • User Persona & Journey Mapping: Generates detailed user personas with concrete pain points (using the Jobs-to-be-Done framework) and maps user journeys with CoD^Σ notation.
  • Strategic Clarity: Articulates the product's "Our Thing" (key differentiator) and North Star Metric, providing a clear, user-focused strategic compass.
  • Use Case: You're starting a new project or need to re-align an existing one. Use this Skill to generate a comprehensive product.md that defines your target users, their pains, and how your product solves them, all without any technical jargon.

Quick Start

To define your product's core strategy and user needs:

Ensure your repository has some code or documentation.

Then, simply invoke the skill:

/define-product

Frequently Asked Questions about Define Product

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

FAQPage Schema
How do I create a user-centric product definition from my codebase?

Define a user-centric product definition by invoking the Skill to analyze your repository, infer product goals and user needs, then generate comprehensive product.md documentation with user personas, pain points, and user journeys—no technical jargon required.

What should a product definition include for Jobs-to-be-Done mapping?

A JTBD-focused product definition maps user personas to their core jobs, pains, and desired resolutions. This Skill generates 3+ personas with explicit pain-to-resolution mappings and user journeys using CoD^Σ notation, grounding strategy in measurable user needs.

Can I define my product's North Star Metric and key differentiator without technical details?

Yes. This Skill articulates your product's "Our Thing" differentiator and North Star Metric purely from user-focused analysis, delivering strategic clarity centered on target users and their pain points rather than implementation specifics.

How do user journeys and personas help clarify product strategy?

User journeys map how personas move through your product to resolve their pains, while personas capture concrete user segments with specific jobs and pain points. Together, they align development effort to real user needs and prevent misaligned feature work.

What prerequisites does my repository need to generate a product definition?

Your repository needs some existing code or documentation so the Skill can perform intelligence gathering and infer product characteristics. No special setup required—invoke the Skill directly to begin analysis.