create-jtbd-canvas
Create JTBD Canvas
Overview
Generate a Jobs-to-be-Done canvas that maps the full job landscape for a persona or problem space — functional jobs (what they are trying to accomplish), emotional jobs (how they want to feel), and social jobs (how they want to be perceived). Each job includes the current solution, pain points, desired outcomes, situation-based triggers, and hiring/firing criteria. This canvas is the foundation for opportunity identification and solution design.
Workflow
-
Read product context — Load
.chalk/docs/product/0_product_profile.md, any existing research syntheses, interview guides, and prior JTBD docs. If research synthesis docs exist, they are the primary input — JTBD canvases should be grounded in evidence, not speculation. If no product context exists, work from what the user provides and flag that the canvas is hypothesis-based. -
Identify the persona — Parse
$ARGUMENTSto determine the target persona or problem space. If the user specifies a persona, use it. If they specify a problem space (e.g., "expense reporting"), identify the primary persona who experiences that problem. If neither is clear, ask: "Who is the person struggling with this? What is their role and context?" -
Map the main job — Identify the overarching job the persona is trying to get done. This is not a task or feature — it is the higher-order goal. Use Alan Klement's format: "When [situation], I want to [motivation], so I can [desired outcome]." The main job anchors the entire canvas.
-
Map functional jobs — Break down the practical things the persona needs to accomplish. For each functional job:
- Job statement: concrete action they need to perform
- Current solution: how they solve this today (including workarounds, manual processes, competitor products)
- Pain points: what is frustrating, slow, expensive, or broken about the current solution
- Desired outcome: what success looks like when this job is done well
More from generaljerel/chalk-skills
python-clean-architecture
Clean architecture patterns for Python services — service layer, repository pattern, domain models, dependency injection, error hierarchy, and testing strategy
24create-handoff
Generate a handoff document after implementation work is complete — summarizes changes, risks, and review focus areas for the review pipeline. Use when done coding and ready to hand off for review.
16create-review
Bootstrap a local AI review pipeline and generate a paste-ready review prompt for any reviewer agent. Use after creating a handoff or when ready to get an AI code review.
15fix-findings
Fix findings from the active review session — reads reviewer findings files, applies fixes by priority, and updates the resolution log. Use after pasting reviewer output into findings files.
15fix-review
When the user asks to fix, address, or work on PR review comments — fetch review comments from a GitHub pull request and apply fixes to the local codebase. Requires gh CLI.
15review-changes
End-to-end review pipeline — creates a handoff, generates a review (self-review or paste-ready for another provider), then offers to fix findings. Use when you want to review your changes before pushing.
13