Loading...
Loading...
Found 13 Skills
Guide discovery through questioning techniques and pattern recognition for Clean Code, GoF design patterns, and architectural decisions. Use when coaching developers, facilitating design discussions, or helping teams discover solutions.
모호한 요청을 소크라테스식 질문으로 인터뷰해 실행 가능한 요구사항으로 정리한다. 사용자가 deep-interview, 심층 인터뷰, 요구사항 명확화, 생각 정리를 요청하거나 목표, 범위, 제약, 완료 기준이 흐릿할 때 사용한다. 요청이 이미 구체적이거나 단순 오타, 작은 설정 변경, 테스트 보강처럼 물을 가치가 낮은 작업에는 사용하지 않는다.
Clarify WHAT a phase delivers with ambiguity scoring; produces a SPEC.md before discuss-phase.
Socratic questioning to examine beliefs, uncover assumptions, and develop deeper understanding. Use to challenge thinking, evaluate proposals, or teach without lecturing.
Socratic questioning protocol + user communication. MANDATORY for complex requests, new features, or unclear requirements. Includes progress reporting and error handling.
Guides structured ideation through Socratic questioning to explore problems, opportunities, and solutions. Use when brainstorming features, exploring use cases, or thinking through new ideas.
Interview about a plan file to refine it through in-depth questioning. Use when you have a plan that needs validation, refinement, or deeper exploration before implementation. Triggers on "interview me about", "refine this plan", "question this spec".
Through expert hypotheses, Socratic questioning, and critical evidence, help users quickly identify the truly worthwhile problem from vague confusion, anomalous results, hasty attributions, or self-labeling. Suitable for scenarios like "help me find the real problem," "don't give solutions yet, ask me step by step," "why did I do it but got no results," "I think maybe I'm not capable," "please check if my judgment holds," as well as when users provide chat logs, data, screenshots, or files and want the AI to locate the breakpoint based on the materials. Defaults to natural short conversations; not for pure factual queries, simple execution tasks, or when the user has already given a clear and verifiable problem and explicitly asks to solve it directly.
Apply Socratic questioning — systematic inquiry via clarification, assumption-probing, evidence-testing, perspective-shifting, implication-tracing, and meta-questions — to coach learning or surface hidden assumptions in a person's reasoning. Use this skill when the user is explicitly facilitating learning, coaching a person through their own thinking, or needs a structured questioning sequence to probe a held belief, even if they say 'play devil's advocate on this claim' or 'how should I coach my team through this problem via questions'. Do NOT use for open-ended brainstorming, information gathering, or requirements-discovery question lists where no belief is being probed.
Socratic deep interview with mathematical ambiguity gating before autonomous execution
When a request is vague, assumption-laden, or "obvious," ask the few load-bearing questions that expose hidden requirements before building or committing.
Socratic questioning discipline - the user is asked, not told, until they can state the rule themselves. Use when the user says "ช่วยถามคำถามหน่อย", "ถามให้คิด", "ask me questions", "grill me", "quiz me", "make me think"; when they own an artifact they do not understand - "ยังไม่ค่อยเข้าใจสิ่งนี้ที่ให้ AI ทำ", "I don't understand what was built for me", a plan/map/pipeline/codebase handed to them; before a sign-off, handover, or onboarding onto a system they now own. Not for explaining on request (feynman-explain) and not for challenging a plan before building it (grill-then-plan).