본문으로 건너뛰기
cccskills
무료GitHub에 공개

lateral-thinking

Use for lateral thinking, or when ideas feel stuck or incremental: "we've tried everything", "need a surprising angle", "break the pattern", "give me a wild idea that could work". Uses provocations and reframes. Skip for rule lookups or strict logical proofs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(2)

  • SKILL.md3.5 KB
  • references/example.md1.4 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Lateral Thinking

Edward de Bono's method for escaping a rut: movement before judgment. A provocative line is a stepping stone, never a final position.

When to use

  • Brainstorming stalled or every option is a small variation of the current one.
  • The user wants a surprising angle, a reframe, or to challenge an assumption they call "just how it works".
  • Conventional ideation already ran and produced nothing fresh.

Skip: a single compliant rule lookup, a tight logical proof, or users with no appetite for playful what-if moves.

Before you start

  1. State in one block: Stuck point (which pattern or assumption feels rigid) and Pass: Provocation, Extract principle, Concept fan, Candidates (or the alternate path below).
  2. Gather first. If you can read the project or earlier attempts, check what was already tried so you do not repeat it. Ask up to 3 questions only for safety or legal limits that tools cannot answer.
  3. Light path. Small ask: one Po, one principle, 2 ideas per fan level, 3 candidates.

Alternate paths (use only when the user asks):

  • Random entry: replace Provocation with one random noun or image, then bridge in 3 steps (property, analogy, mechanism, application).
  • Challenge implicit rules: list the rules everyone follows; for each give Challenge / Reframe / Smallest test; pick the load-bearing rule and give two ways to sidestep it; then Candidates only from that thread.

Moves

1. Provocation

One primary Po (it may be illogical or impossible):

Po: ... - Movement idea: what useful idea does this suggest if treated as a springboard?

2. Extract principle

From the movement idea, state one operating principle that could work in the real world, even if the Po itself is absurd.

3. Concept fan

Step back from the principle to broader aims, then fan forward. Three levels, per de Bono:

  • Directions: the broadest approaches ("make the problem disappear", "make waiting pleasant").
  • Concepts: general methods under each direction.
  • Ideas: specific, actionable ways to carry out a concept.

Give a few branches at each level. If nothing is good enough, step back one more level and fan out again.

4. Candidates

Several actionable ideas, each tagged near-term, stretch or experimental.

Rules

  1. Never present a Po as a recommendation. Always pair it with its movement idea or principle.
  2. If a provocation touches safety, ethics or law, stop and name the conflict. Do not rationalize harm.
  3. Judge only in Candidates, and only for tagging feasibility.

Pitfalls

  • A Po that is merely a bad idea. It should shift your thinking, not be wrong for its own sake.
  • Jumping to Candidates from the Po and skipping the principle. The principle is what makes it portable.
  • Fan levels that all say the same thing. Each level should widen or narrow, not repeat.

Worked example: references/example.md.

Checklist

  • Stuck point and Pass stated (alternate path noted if used)
  • Po paired with a movement idea, or the alternate path completed
  • Fan covers Directions, Concepts and Ideas
  • Candidates tagged near-term, stretch or experimental
  • No Po presented as policy

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Use for analytical thinking, or when a question needs breaking down and evidence: "why did metric X drop?", "what drives this?", "break this down", "what data do we need?". Builds a tree, hypotheses and evidence, ends with an answer and key uncertainty. Skip for quick verdicts.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ysskrishna/ai-agent-skills172026년 10월 17일 업데이트

Use for creative thinking, or when the user wants many fresh options before choosing: "give me ideas", "brainstorm names", "other ways to do this", "think outside the box". Diverges first, then picks. Skip when one answer is wanted or the task is pure execution.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ysskrishna/ai-agent-skills172026년 10월 17일 업데이트

Use for critical thinking, or when the user wants a claim, plan or decision checked for weak spots: "is this right?", "what am I missing?", "poke holes", "sanity check", "devil's advocate", "red team this". Skip for execution-only tasks and wording edits.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ysskrishna/ai-agent-skills172026년 10월 17일 업데이트

Use for design thinking, or when a product or service problem needs user understanding before solutions: "what do users really need?", "how might we...", "plan a discovery sprint", "validate this concept". Skip when the spec is frozen or the task is code maintenance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ysskrishna/ai-agent-skills172026년 10월 17일 업데이트

Use for ethical thinking, or when a plan could harm or unfairly burden people: "should we do this?", "is this fair?", "privacy or bias risk", "who gets hurt?". Maps stakeholders, harms, power and consent. Skip for legal advice, neutral fact lookups and implementation-only work.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ysskrishna/ai-agent-skills172026년 10월 17일 업데이트

Use for Fermi estimation, or when a rough number is needed fast: "roughly how many...", "ballpark the cost", "estimate capacity or market size", "is this even feasible?". Decomposes, uses ranges and sanity-checks. Skip when exact data is available or a precise calculation is wanted.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ysskrishna/ai-agent-skills172026년 10월 17일 업데이트

ysskrishna의 스킬 모두 보기

이 스킬의 문제 신고