better-thinking-recipes

# Recipes Given a named external framework — or a request to browse what's available — load its mapping from `recipes/` and run the mapped skill sequence as one continuous, orchestrated pass. ## Why A recipe doc under `recipes/` states which skills implement each stage of a framework like Design Thinking, but a doc sitting unread doesn't run itself — without an orchestrator, it's reference material a human has to manually walk. This skill is the bridge: it makes a named framework actually executable, the same way a composite skill makes its own procedure executable. A user who doesn't yet know this collection's recipe names, or the frameworks' jargon, also needs a way to discover them without reading `recipes/README.md` directly — so browsing and running live in one place. ## Use when / Don't use when - **Use when:** the user names a known external framework explicitly, describes its stages without naming it, asks what recipes/frameworks exist, or wants to browse options before committing to one. - **Don't use when:** no matching recipe exists in `recipes/` — fall back to `better-thinking`'s normal routing instead of forcing an ill-fitting framework onto the task. Don't use for a task that's already better served by a single atomic or composite skill directly. ## Inputs → Outputs - **Inputs:** either a named framework (or a description matching one's stages) and the task to run it on, or no framework at all — just a request to see what's available. - **Outputs:** if br...