Loading...
Loading...
Found 7 Skills
Guide PMs through MITRE's Problem Framing Canvas with structured questions across Look Inward, Look Outward, and Reframe to produce a clear, bias-resistant problem statement.
Extract and structure fuzzy product ideas into validated problem statements, target users, and jobs-to-be-done. Use when a user has a raw idea, concept, or solution in mind but hasn't clearly articulated the problem, target user, or assumptions. This skill helps users communicate context to coding agents more effectively, reducing iteration cycles and "that's not what I meant" moments.
Identify the core constraints that truly define a domain, profession, role, product, or debate. Classify these constraints into World/Rules/Interpretation (Hard/Soft/Self-imposed) categories, then analyze how this set of constraints defines identity, completes the problem statement, frames the solution space, and explains actual behaviors. It is particularly useful for distinguishing solution divergences caused by different constraints despite the same goal, and identifying old interpretations that are mistakenly treated as hard facts. USE WHEN the user says 'constraint', 'find constraints', 'what are the constraints of this domain', 'essential constraints', 'what defines its boundaries', 'is this a hard constraint or self-imposed constraint', 'where are the boundaries', 'why does this behavior happen', 'constraint', '/ljg-constraint', or provides any domain/profession/role/product/debate and requests mapping of its defining constraints and solution space. NOT FOR deep-dive generators (use ljg-rank, which focuses on generative power rather than boundaries), vertical deep dives into a single viewpoint (use ljg-think), book decomposition (use ljg-book), or concept dissection (use ljg-learn).
Articulate a problem from the user's perspective using an empathy-driven framework that captures who they are, what they're trying to do, what's blocking them, why, and how it makes them feel. Use thi
Define the framing of a problem. Change the statement, change the solution space. Use when starting work, when solutions feel wrong, or when you suspect an X-Y problem.
Frames product design problems before solutions exist. Synthesizes research, sizes opportunities, defines hypotheses, scopes projects, and maps customer journeys. Use this skill for new project kickoffs, ambiguous business asks, translating research into briefs, strategic framing sessions, opportunity assessments, project scoping, stakeholder alignment, and competitive analysis—even if the user doesn't explicitly say "strategize."
Challenges stakeholder requests to identify real needs and propose optimal solutions. Use when receiving vague feature requests, reframing a problem before implementation, or when user mentions problem framing, XY problem, stakeholder request, or solution discovery. WHEN NOT: Well-defined technical tasks with clear requirements, bug fixes with known root causes, or routine CRUD operations.