umbel: Skill for Claude Code

Position: Who is this for, what job do they hire it for

Owns: catalog.personas[] (id, name, description, archetype, jobs[]) and catalog.opportunities[] (id, description, value, confidence, source, signals, personas: string[]) on the garden polyglot.

Job indexing is a load-bearing contract. Each persona's jobs[] is an ordered array. Downstream checks anchor to a specific job via validates_job: "<persona_id>:<job_index>" — "founder:0" means "persona founder, first Klement Job Story." Reordering jobs after publication silently retargets every check pointing at them, so treat the array like an append-only list once features start referencing it. If a job must be reordered or removed, /tend change requires an explicit reindex map so it can rewrite every dependent validates_job.

What this skill assumes

• The garden polyglot exists and has at least a draft bet (the project knows roughly what it is).
• The user has some sense of who the project is for — at minimum a few interview notes, sales-call snippets, or strong founder intuition. This skill structures what the user already knows; it does not generate ICPs from nothing.
• It's OK if the catalog has shallow personas (name only) — this skill fills in archetype, jobs[], and opportunity.personas from there.
• Downstream skills (/tend brainstorm, /tend audit) will be unwired without this skill's output. Run this before they need it.

Purpose

Tend's six slots tell you what you're building and why technically. They don't tell you who you're building it for or what job that person hires your product to do in a specific moment of their week. Without that, every downstream artifact — feature pages, narratives, evals — drifts toward technical-taxonomy voice.

This skill plants the spine:

• ICP archetypes — one phrase per persona that names a real human with real stakes. Not roles ("Backend Engineer"), but situated archetypes ("Solo founder running a SaaS side project on weekends; values speed over polish; can't justify a day of tooling").
• Klement Job Stories — 3–5 per persona, in the form: "When [situation], because [motivation], we believe [outcome]. We'll know we got it right when [validation]."
• Refined opportunities — pains felt by which persona, value level, confidence (and source / signals if known).
• Scenario seeds — 2–3 concrete moments per persona (a sentence or two each), captured in the persona's description or jobs. These are the openers tend-narrate uses to start feature pages with a story rather than a label.