creative-method-selector

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# Creative Method Selector

## Goal

Choose the minimum useful creative method or method sequence for the current problem.

The job of this skill is not to dump frameworks. The job is to classify the problem, pick the right route, and explain why that route fits better than the alternatives.

This skill selects methods. It does not execute the full downstream methodology unless explicitly asked or paired with the selected child skill.
It also does not decide whether the whole proposal should proceed; if a proceed / revise / stop verdict is needed, use `quality-gate`.

## Default Posture

- classify before ideating
- prefer one method before many
- prefer staged routing over method pile-up
- match method to problem type, not to taste
- keep the route minimal and explainable

## When To Use

Run this skill when:

- the user wants a creative solution but the right method is unclear
- several methodologies could apply and a choice is needed
- the task mixes framing, ideation, contradiction, and systems effects
- the team is stuck and needs a better thinking mode
- a phase transition changes which method should lead

This is a mandatory routing gate before:

- invoking a creativity-related skill family
- combining multiple creative methods in one task
- escalating from simple ideation to a structured innovation workflow

## Scope Boundaries

In scope:

- classify the problem
- choose the minimum useful route
- name the next best method or sequence
- explain why competing methods were not chosen

Out of scope by default:

- running the full selected methodology
- generating the final solution itself
- combining many methods "just in case"

## Problem Types

Classify the task into one primary type first:

- `problem_is_unclear`
- `need_more_options`
- `has_contradiction`
- `thinking_is_stuck`
- `system_effects_dominate`
- `need_full_process`

Add a secondary type only if it materially changes routing.

## Phase Types

Identify the current phase:

- `framing`
- `divergence`
- `resolution`
- `validation`

If phase is unclear, default to `framing`.

## Core Routing Map

- `problem_is_unclear` -> `jtbd`
- `need_more_options` -> `scamper`
- `has_contradiction` -> `triz`
- `thinking_is_stuck` -> `lateral-thinking`
- `system_effects_dominate` -> `systems-thinking`
- `need_full_process` -> `creative-problem-solving`

## Routing Modes

Use one of:

- `single`
  - one primary method only
- `paired`
  - one primary method plus one support method
- `staged`
  - an ordered sequence across phases
- `hold`
  - pause routing and send the task back to clarification

Decision rule:

- use `single` when one problem type dominates
- use `paired` when one secondary type clearly blocks progress
- use `staged` when the task must move through distinct phases
- use `hold` when the problem cannot be classified with enough confidence

## Pairing Rules

Allowed examples:

- `jtbd + scamper`
- `triz + systems-thinking`
- `lateral-thinking + creative-problem-solving`

Disallowed by default:

- three or more methods at once
- methods with overlapping roles and no order
- any pair without a clear primary method

## Staged Routing Rules

From Alubiama/awesome-cognitive-skills, MIT.

More from Alubiama/awesome-cognitive-skills