Act as a product-manager copilot that turns evidence into product decisions and artifacts: backlogs and prioritization, PRDs and user stories, metrics and OKRs, experiments, launch plans, feedback triage, and pricing/packaging, kept in a per-product workspace. Use whenever the user wants to decide what to build, spec it, or ship it: "write a PRD for…", "prioritize our backlog", "what should we build next", "plan OKRs", "define our north star metric", "design an A/B test", "plan the launch", "triage this customer feedback", "platform or feature?", in any language ("viết PRD", "ưu tiên tính năng nào", "quản lý sản phẩm", "プロダクト管理", "产品经理"), even when they never say "product manager". Also use when the user returns to a product workspace this skill created (a directory holding `product.md`, `state.md`, and `decisions.md`). Not for deep user discovery (design-thinking), desk market facts (market-researcher), or company-level bets (strategy-board).
「thinking」の検索結果
595 件 ・ 関連度順
概要と使いどころ
Audit the reasoning of a document or argument (memo, proposal, investment analysis, board paper, article, the user's own draft): claims, evidence, unstated assumptions, logical gaps, fallacies, and what would falsify it, each anchored to quoted text. Use whenever the user wants reasoning examined, in any language ("audit this argument", "is this analysis sound", "poke holes in this proposal", "review the logic of my draft"; Vietnamese "phản biện giúp tôi", "soi lập luận này", "tài liệu này có lỗ hổng gì", "góp ý bản nháp của tôi"), even when they never say "critical thinking". Also use when the user drops a document and asks whether to trust or act on it, or asks to see their reasoning profile. Not for company-level strategic bets (strategy-board) or learning a topic through dialogue (socratic-questor).
日本語の概要は準備中です。原文の説明を表示しています。
Computational thinking as a problem-solving discipline independent of programming languages. Covers the four pillars (decomposition, pattern recognition, abstraction, algorithm design), computational problem-solving methodology (understand, decompose, generalize, formalize, verify), abstraction levels (from hardware through user interface), modeling and simulation, automata and formal languages (DFA, NFA, regular expressions, context-free grammars, Turing machines), computational complexity classes (P, NP, NP-complete, undecidable), and constructionist pedagogy (learning by building, Logo, Scratch, physical computing). Use when approaching unfamiliar problems, teaching problem-solving strategies, analyzing problem complexity, or bridging between domain knowledge and computational solutions.
日本語の概要は準備中です。原文の説明を表示しています。
Three-dimensional art and sculptural thinking for art education. Covers additive and subtractive sculptural processes, armature construction, modeling in clay, carving principles, casting and moldmaking, assemblage and found-object sculpture, installation art as expanded sculpture, and the conceptual transition from pictorial to spatial thinking. Use when working with three-dimensional media, analyzing sculptural form, understanding spatial composition, or investigating the relationship between sculpture and site.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill for ANY financial market, investment, or macro-economic analysis. ALWAYS trigger this skill — do not skip it — when the user asks about: BTC, bitcoin, crypto, gold, silver, oil, stocks, forex, bonds, interest rates, Fed policy, inflation, deflation, stagflation, market structure, trading setups, portfolio allocation, asset allocation, investment strategy, price analysis, market outlook, geopolitics affecting markets, or any question involving "should I buy/sell/hold [any asset]", "what will [asset] do", or "analyze [market/asset]". Apply Genesis Protocol (First Principle + System Thinking) combined with SMC Layer analysis to produce structured insights with explicit scenarios, entry/exit zones, and uncertainty. For non-market strategic thinking, use genesis-mind-strategic-intelligence instead.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill for ANY financial market, investment, or macro-economic analysis. ALWAYS trigger this skill — do not skip it — when the user asks about: BTC, bitcoin, crypto, gold, silver, oil, stocks, forex, bonds, interest rates, Fed policy, inflation, deflation, stagflation, market structure, trading setups, portfolio allocation, asset allocation, investment strategy, price analysis, market outlook, geopolitics affecting markets, or any question involving "should I buy/sell/hold [any asset]", "what will [asset] do", or "analyze [market/asset]". Apply Genesis Protocol (First Principle + System Thinking) combined with SMC Layer analysis to produce structured insights with explicit scenarios, entry/exit zones, and uncertainty. For non-market strategic thinking, use genesis-mind-strategic-intelligence instead.
日本語の概要は準備中です。原文の説明を表示しています。
Use when Codex must make a high-quality judgment on any complex problem, not only technical problems. Trigger when a question has high complexity, uncertainty, cost of being wrong, long-term impact, value tradeoffs, possible structural causes, or when the user asks for 全面思考, 深度理解, 系统性分析, 帮我想清楚, 从根上看, 这件事到底怎么看, 方法论, 复杂问题拆解, 系统方案, 架构判断, 策略判断, or 根因分析. Also trigger for project and engineering high-risk scenarios such as multi-module, multi-environment, multi-data-source, multi-state, financial truth, live trading, ledger, revenue, customer assets, order governance, broker interfaces, online availability, major solution selection, and system closure.
日本語の概要は準備中です。原文の説明を表示しています。
Self-critique specification documents using extended thinking — surfaces hidden assumptions, contradictions, missing edge cases, and scope creep before implementation
日本語の概要は準備中です。原文の説明を表示しています。
Sequential thinking and structured problem solving. Break down complex problems into steps with revision and branching capabilities. Use for multi-step analysis, planning, and hypothesis verification.
日本語の概要は準備中です。原文の説明を表示しています。
当用户需要构建一个系统/理论/知识体系、寻找问题的底层原理、或在问"如何从根本原理出发推导一切""怎么找到事物的本质""为什么物理学/哲学思维有用"时激活。 核心信号：用户在做体系化思考、寻找"第一因"、或试图从少量前提推导出完整方案。 不适用于：纯粹的执行层面问题、不需要理论指导的实操任务。
日本語の概要は準備中です。原文の説明を表示しています。
当用户在反思自己的认知局限、质疑群体共识、或在问"如何独立思考""怎么判断自己是不是被洗脑了""为什么我总觉得自己是对的""怎么避免从众"时激活。 核心信号：用户在做"元认知"——审视自己的思维过程本身，或在群体压力下试图保持独立判断。 不适用于：需要快速决策的紧急情况、纯技术性问题、不需要反思的信息查询。
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Bloom's revised taxonomy to classify learning objectives and design assessments across six cognitive levels. Use this skill when the user needs to write learning objectives at specific cognitive levels, align assessment with instructional goals, or evaluate curriculum for cognitive complexity distribution — even if they say 'how to write learning objectives', 'what level of thinking does this require', or 'higher-order thinking skills'.".
日本語の概要は準備中です。原文の説明を表示しています。
Coordinate structured thinking and multi-agent parallel execution for complex tasks. Use when tackling multi-step projects, planning parallel work, breaking down complex problems, coordinating specialist tasks, facing architectural decisions, or when user mentions "workflow", "orchestration", "multi-step", "coordinate", "parallel execution", "structured thinking", "break this down", "plan this out", "how should I approach", or needs help planning complex implementations.
日本語の概要は準備中です。原文の説明を表示しています。
Run structured product thinking exercises before writing a spec. Use this skill when: - You need to think through a feature idea before writing a PRD - You want to run the 11-star experience exercise for a feature - You need a positioning statement using Geoffrey Moore's framework - You want to define product principles and success vision for a new feature - You have a raw feature idea and need to turn it into a structured brief
日本語の概要は準備中です。原文の説明を表示しています。
Use when stuck on approach, not debugging. Unstick via 7 techniques: simplification, collision-zone thinking, inversion, first principles, via negativa. For debugging use mk:sequential-thinking.
日本語の概要は準備中です。原文の説明を表示しています。
Use for strategic thinking, or when the user must choose a direction under constraints: "where should we focus?", "how do we win?", "roadmap for next year", "what should we not do?". Ends in explicit bets and risks. Skip for step-by-step implementation.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use for first principles thinking, or when the user questions an inherited default: "why do we do it this way?", "is this cost really necessary?", "should we copy what competitors do?". Strips analogies and rebuilds from fundamentals. Skip for convention-following checklists.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user describes a problem, decision or stuck situation but names no method: "how should I approach this?", "help me think this through", "we can't decide", "where do I start?". Picks the best-fit thinking method and runs it. Skip for plain execution tasks or when a method is named.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use for systems thinking, or when a change may ripple beyond its target: "what are the side effects?", "why does this keep coming back?", "how do these teams or services affect each other?". Maps loops, delays and leverage points. Skip for single-step fixes.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。