130건 · 관련도순
Choose a named creative method suited to the project and stage of work. Generate, expand, compare, or refine ideas with concrete mechanisms, honest tradeoffs, and at least one practical option with a first step.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Run a brainstorming session with creative techniques suited to a topic and goal. Choose guided questioning, collaborative ideation, or autonomous idea generation, while keeping a session log that supports resuming work after an interruption.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Develop and prioritize early research ideas through independent brainstorming, structured discussion, evidence checks, and critical review. Keep assumptions, uncertainty, dissent, and scoring reasons visible, then record the human decision and appropriate next steps.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Choose research problems, refine new ideas, or rethink stalled projects through structured conversation. Assess feasibility, potential impact, and risks, then develop success criteria, decision points, and backup plans for a clearer research strategy.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Generate improvement ideas for an existing product from product management, design, and engineering perspectives. Produce five ideas per perspective, then select the top five based on goals, potential impact, feasibility, and differentiation, with reasons and assumptions to test.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Explore features for a new product through product management, design, and engineering perspectives. Generate five ideas from each viewpoint, then select five priorities with reasoning and assumptions to test before developing the concept further.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Develop a game concept through guided discussion of player experiences, preferences, and practical constraints. Compare ideas, define repeated player actions and design priorities, and produce either a concise game brief or a detailed concept document.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Generate improvement ideas grounded in the project or topic, critique every candidate, and rank the survivors with explanations. Produce a document that helps users choose which ideas deserve further exploration before defining requirements.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Develop solution ideas through repeated rounds of research, cross-domain borrowing, recombination, and evaluation. Receive ranked candidates with feasibility and novelty scores, supporting and opposing arguments, and a record of where each idea came from and how it changed.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Explore a development idea through probing questions before committing to a plan. The skill can initiate research when needed and route the resulting ideas into GSD notes, tasks, research questions, requirements, or development phases.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Clarify what a product interface should be and what users should accomplish before design or prototyping begins. Ask only about missing information, summarize the brief and assumptions, then continue into the appropriate design workflow.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
This skill should be used when the user asks to "brainstorm research ideas", "use 5W1H framework", "identify research gaps", "conduct gap analysis", "start research project", "conduct literature review", "define research question", "select research method", "plan research", or mentions research project initiation phase. Provides comprehensive guidance for research startup workflow from idea generation to planning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run one unattended IMPLEMENTATION iteration of the autonomous value-creation loop — steward any in-flight PR, fix interrupts (red CI / security / human bugs), or else build ONE queued `idea` issue on a branch off auto-dev and open a PR that squash-merges on green CI. Ideation lives in the next-idea skill; this skill consumes its queue. Use when the user says "次のタスク", "next task", "続きをやって", or wants autonomous progress without specifying what to do.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run one unattended IDEATION iteration of the autonomous value-creation loop — invent improvements a user of cc-wf-studio would notice, judge them against the value bar, and file the winners as locked `idea` issues. Never implements anything; the next-task skill builds from the queue this skill fills. Use when the user says "アイデア出して", "next idea", or wants proposals without implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run one unattended IDEATION iteration of the quality-assurance loop — find the highest-value untested behavior in the codebase, judge it against the QA value bar, and file ONE locked `qa` issue specifying the test to write. Never writes code or tests; the next-qa skill builds from the queue this skill fills. Use when the user says "QAアイデア", "next qa idea", or wants the QA backlog refilled without implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when the user asks to "brainstorm research ideas", "use 5W1H framework", "identify research gaps", "conduct gap analysis", "start research project", "conduct literature review", "define research question", "select research method", "plan research", or mentions research project initiation phase. Provides comprehensive guidance for research startup workflow from idea generation to planning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Divergent research ideation — generate many candidate directions, then adversarially filter to the strongest
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured hypothesis formulation from observations. Use when you have experimental observations or data and need to formulate testable hypotheses with predictions, propose mechanisms, and design experiments to test them. Follows scientific method framework. For open-ended ideation use scientific-brainstorming; for automated LLM-driven hypothesis testing on datasets use hypogenic.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interactive system flow tracing across CODE, API, AUTH, DATA, NETWORK layers with SQLite persistence and Mermaid export. Use for security audits, compliance documentation, flow tracing, feature ideation, brainstorming, debugging, architecture reviews, or incident post-mortems. Triggers on audit, trace flow, document flow, security review, debug flow, brainstorm, architecture review, post-mortem, incident review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Parallel divergent ideation for coding agents. Spawns N isolated branches under different cognitive frames (regulator, biology, speedrunner, 10-year-old, $0 budget), scores, clusters, prunes traps, and deepens top survivors. Use on /adhd, "ADHD mode", brainstorm/ideate intents, or open-ended design, architecture, naming, API/SDK surface, and fuzzy-debugging decisions. Skip for syntax, lookups, bugs with known root cause, or closed phrasing ("quick", "standard", "canonical", "textbook"). Full pre-flight gate is in the skill body.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Brainstorm creatively with pattern spotting and paradox hunting — use for ideation and exploration
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Structured hypothesis formulation from observations. Use when you have experimental observations or data and need to formulate testable hypotheses with predictions, propose mechanisms, and design experiments to test them. Follows scientific method framework. For open-ended ideation use scientific-brainstorming; for automated LLM-driven hypothesis testing on datasets use hypogenic.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Open-ended scientific ideation partner. Use for research gaps, mechanism exploration, interdisciplinary connections, assumptions, possible research directions, and lightweight literature matrix or A+B paper-combination idea mapping. For structured testable hypotheses and validation plans, use hypothesis-generation instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.