Define: From Code (the fast-track)

This skill is the Define-phase counterpart of studio-design-design-system-from-code. Instead of going forward — blank worksheet → interview → filled offer — it goes backward: it reads the product that already exists (the codebase, the live app, the landing page, the listing) and extracts the strategy that's already implicit in it into the three Define worksheets. The forward skills are for greenfield ideas. This one is for members who arrive with something built and shouldn't spend their first week pretending they don't.

What this skill is not: a way to skip the thinking. The offer work is the most valuable session in the programme precisely because it forces clarity — so the fast-track ends in a critique, not a shrug. Everything this skill writes is an extracted draft, and the handoff to studio-define-offer-review is mandatory, not optional. Extraction gets the member to the valuable conversation in hours instead of days; it doesn't replace it.

Session shape: 45–60 minutes. Most of it is reading evidence and confirming inferences — short focused questions, never the full builder interview.

Inputs

Whatever exists, in priority order — read everything available before drafting anything:

1. The codebase — the repository surrounding productos/; read it directly, no path to ask for. Structure, features that demonstrably work, the core flow, auth/payment integrations (a Stripe integration is pricing evidence), copy strings and empty states (offer language hides in UI copy).
2. The live product / landing page / app store listing (get URLs). The public surfaces are the strongest offer evidence there is — they show what the product actually promises today: which customer it addresses, which pain it names, what price it dares to show.
3. Existing docs — READMEs, pitch decks, specs, notes. Secondary to the artifacts: what the member wrote about the product and what the product does often disagree, and the product wins.
4. The member. Real usage (who uses it, how they found it, what they say) and anything paid. Ask; don't infer user counts from code.

This skill runs read-only against the product — it never modifies the app code. The only files it writes are the three Define templates in productos/define/.