19 件 ・ 関連度順
概要と使いどころ
/cs:office-hours <topic> — YC-style 6-question founder interrogation before any advice. Forces clarity on problem, customer, distribution, defensibility, capital, and founder fit. Use when a founder question is too vague to route — e.g. 'should we grow faster?' — or before drafting a strategy brief.
日本語の概要は準備中です。原文の説明を表示しています。
MANUAL TRIGGER ONLY: invoke only when user types /office-hours. YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to "brainstorm this", "I have an idea", "help me think through this", "office hours", or "is this worth building". Proactively suggest when the user describes a new product idea or is exploring whether something is worth building — before any code is written.
日本語の概要は準備中です。原文の説明を表示しています。
MANUAL TRIGGER ONLY: invoke only when user types /office-hours. YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to "brainstorm this", "I have an idea", "help me think through this", "office hours", or "is this worth building". Proactively suggest when the user describes a new product idea or is exploring whether something is worth building — before any code is written.
日本語の概要は準備中です。原文の説明を表示しています。
YC Office Hours — product validation for a new product, feature, or side-project concept. Startup mode tests demand; Builder mode develops an unvalidated product idea. Use when the user asks whether something is worth building or has an idea whose problem/value is not yet validated. Proactively suggest when the user describes a new product idea or is exploring whether something is worth building — before any code is written. Use BEFORE a plan exists. For reviewing an existing plan, use /mk:plan-ceo-review.
日本語の概要は準備中です。原文の説明を表示しています。
GStack office-hours method for early product ideas, startup demand checks, builder-mode brainstorming, narrow wedge selection, and pre-architecture clarification before plan review.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to brainstorm, evaluate whether an idea is worth building, run office hours, or think through a new product idea or design direction before any code is written.
日本語の概要は準備中です。原文の説明を表示しています。
YC Office Hours — two modes. (gstack)
日本語の概要は準備中です。原文の説明を表示しています。
/cs:brief <topic> — Generate a one-page strategy brief from an office-hours intake. First step in the strategic sprint pipeline. Use when a strategic question needs to be framed before boardroom deliberation — e.g. locking options, assumptions, and success criteria for a pricing change or a market-entry decision.
日本語の概要は準備中です。原文の説明を表示しています。
YC-style product validation using six forcing questions. Pressure-tests a feature idea before it becomes a requirement — ensuring real demand, a clear wedge, and evidence behind assumptions.
日本語の概要は準備中です。原文の説明を表示しています。
YC Office Hours — product idea diagnostic before writing code. Two modes: Startup (6 forcing questions with rigorous pushback) and Builder (generative brainstorming). Outputs design doc. Includes landscape research, premise challenge, alternatives generation, visual wireframe sketching, and optional cross-model second opinion.
日本語の概要は準備中です。原文の説明を表示しています。
YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use before /plan-ceo-review or /plan-eng-review.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to brainstorm, evaluate whether an idea is worth building, run office hours, or think through a new product idea or design direction before any code is written.
日本語の概要は準備中です。原文の説明を表示しています。
YC Office Hours-style validation for a new idea before code exists: tests demand (Startup mode) or develops an unvalidated idea (Builder mode). For reviewing an existing plan use mk:plan-ceo-review.
日本語の概要は準備中です。原文の説明を表示しています。
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when asked to "think bigger", "expand scope", "strategy review", "rethink this", or "is this ambitious enough". Proactively suggest when the user is questioning scope or ambition of a plan, or when the plan feels like it could be thinking bigger. Use AFTER a plan exists. For validating the idea itself before planning, use /mk:office-hours first.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a raw idea into ONE honest recommendation: interview one question at a time until the problem, requirements, goals, non-goals, and constraints are CONFIRMED, then deliver a single verdict — do, don't, cheaper alternatives, trade-offs, ordered checklist, success metrics. Required: the user wants exactly ONE recommendation — not options, not a debate — and their framing is open to challenge (advise may answer a different question than the one asked). Triggers on "what should I do about X", "advise me on X", "am I approaching this right", "is this the right move". Do NOT use to be interrogated with no recommendation (→ mk:grill) — advise also interviews one question at a time, but only to reach a verdict. Do NOT use when the framing is settled and only the options are open (→ mk:brainstorming). Do NOT use to decide whether something is worth building (→ mk:office-hours). Do NOT use when you want several perspectives to argue it out (→ mk:party).
日本語の概要は準備中です。原文の説明を表示しています。
Relentlessly interview the user about THEIR plan or design — one question at a time — resolving each branch of a decision tree until shared understanding. Claude is the interviewer; the user is the interviewee. Triggers on "grill me", "stress-test this plan", "get grilled on my design", "interrogate my plan". Checkpoints every answer to docs/knowledge/<slug>.md so progress survives a context-window reset. Flags knowledge the user cannot answer as a gap to chase. Do NOT use to PROPOSE solutions or compare approaches (→ mk:brainstorming). Do NOT use to validate "is this worth building?" (→ mk:office-hours). Do NOT use when Claude should ANSWER questions about the repo (→ mk:ask-me). Do NOT use for a one-shot review of an existing plan (→ mk:plan-ceo-review). Do NOT use to apply named reasoning lenses to findings (→ mk:elicit).
日本語の概要は準備中です。原文の説明を表示しています。
YC-style product strategy assessment with forced questions and CEO scope modes — adapted from gstack /office-hours pattern
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to brainstorm, evaluate whether an idea is worth building, run office hours, or think through a new product idea or design direction before any code is written.
日本語の概要は準備中です。原文の説明を表示しています。
YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to "brainstorm this", "I have an idea", "help me think through this", "office hours", or "is this worth building". Proactively invoke this skill (do NOT answer directly) when the user describes a new product idea, asks whether something is worth building, wants to think through design decisions for something that doesn't exist yet, or is exploring a concept before any code is written. Use before /plan-ceo-review or /plan-eng-review. (gstack)
日本語の概要は準備中です。原文の説明を表示しています。