umbel: Skill for Claude Code

Brainstorm: Idea or Document -> Feature Polyglot

Owns: feature creation, the six slot strings (what / why / impact / fit / where / how), checks[], smoke, personas / solves / journey_phase, entry_condition / exit_condition, and the project-level catalog (components, personas, opportunities, journey_phases). Optionally offer a dek after the slots land — 2–3 sentences weaving what/why/impact into prose. It renders as the page's standfirst and as the lead of the masthead band (the full-width header), both populated deterministically at render time — never write masthead HTML. tend-narrate owns revisiting the dek at polish; offering it at creation is a courtesy, not a gate.

What this skill assumes

• The garden's catalog.personas[] has entries with archetype and jobs[] populated. If empty, redirect to /tend position — checks need bound persona-jobs to point at via validates_job.
• The garden's catalog.opportunities[] entries carry personas[]. New opportunities created during brainstorm are required to bind one or more personas.
• The user can articulate the feature in some form — an idea, a doc, or a list. If the user can't, that's a /tend position redirect (the spine question is upstream of feature-level work).
• Test-first discipline is non-negotiable: every check has a verification_recipe, every feature has a smoke or an explicit no-smoke decision logged.
• WWIFWWh slots are for capability bets. Persona / opportunity polyglots (those whose oo-data has data.persona or data.opportunity set) use their own field set — edit those via /tend position, not /tend brainstorm. Brainstorm refuses to slot a catalog description.

Purpose

Take any input - a fresh idea or an existing doc - and produce a writable, approved feature polyglot. The work is half capture, half interrogation: every check is a real assertion you can verify, with a one-line verification recipe attached. We're not just writing what the feature is; we're forcing the question of how anyone would prove it works.