dev:ideation

Convert product ideas into structured specifications with JTBD analysis and SLC framing.

3|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/ryryo/dot-claude-dev --skill dev-ideation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev:ideation
Source: https://github.com/ryryo/dot-claude-dev/tree/main/.claude/skills/dev/ideation
Command: npx skills add https://github.com/ryryo/dot-claude-dev --skill dev-ideation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps convert raw product ideas into structured product specifications by performing JTBD analysis, competitor research, and SLC-style requirement drafting. It clarifies what to build and how to evaluate success.

Core Features & Use Cases

  • JTBD-driven Problem Definition: Extract target users, core jobs, and pain/gain insights from ideas.
  • Competitor & Alternatives Analysis: Identify direct/indirect competitors and differentiators.
  • SLC-based Product Spec Drafting: Define core scope, mandatory features, and success criteria.
  • Use Case Sample: Convert an idea into PROBLEM_DEFINITION.md, COMPETITOR_ANALYSIS.md, and PRODUCT_SPEC.md.

Quick Start

To begin, run /dev:story to capture a user story, then use /dev:ideation to generate the three docs under docs/ideation. Review and iterate with /dev:feedback.

Frequently Asked Questions about dev:ideation

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

FAQPage Schema
How do I convert a raw product idea into a structured product spec?

To convert a raw product idea into a structured product spec, this skill uses JTBD analysis and SLC framing to generate mandatory PROBLEM_DEFINITION.md, COMPETITOR_ANALYSIS.md, and PRODUCT_SPEC.md documents. It clarifies what to build and how to evaluate success.

What is JTBD analysis and how does it help define a problem definition?

JTBD analysis extracts target users, core jobs, and pain/gain insights from your ideas to build a formal PROBLEM_DEFINITION.md. It clarifies the exact problem a product should solve before committing to implementation scope.

How do I perform competitor analysis when planning product features?

You perform competitor analysis by identifying direct and indirect competitors to establish market differentiators. This skill outputs a COMPETITOR_ANALYSIS.md document detailing alternatives and differentiators for your product idea.

Can I use SLC framing to define mandatory core features and exclusions?

Yes, you can use SLC framing to define core scope, mandatory features, and explicit exclusions. This skill enforces SLC quality criteria to draft a PRODUCT_SPEC.md that outlines what must be built and what to exclude.

Do I need a user story before generating product specifications?

You need a user story before generating product specifications because this skill requires problem definition input to perform JTBD analysis. Run a story capture workflow first to provide the context needed for ideation outputs.

What are the limitations of using automated ideation for product specs?

A limitation of automated ideation is that it requires structured input and cannot replace human judgment on market viability. It outputs formal documents enforcing SLC criteria, but you must review and iterate on the generated specs manually.