「interview」の検索結果

Transcribe audio files to text with optional diarization and known-speaker hints. Use when a user asks to transcribe speech from audio/video, extract text from recordings, or label speakers in interviews or meetings.

日本語の概要は準備中です。原文の説明を表示しています。

Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

日本語の概要は準備中です。原文の説明を表示しています。

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

日本語の概要は準備中です。原文の説明を表示しています。

A relentless interview to sharpen a plan or design.

日本語の概要は準備中です。原文の説明を表示しています。

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

日本語の概要は準備中です。原文の説明を表示しています。

Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.

日本語の概要は準備中です。原文の説明を表示しています。

Help users discover what to build on Stellar. Use when a user says "what should I build on Stellar", "Stellar app ideas", "I want to build on Stellar but don't know what", "Stellar startup ideas", "find me a Stellar project idea", "I'm new to Stellar and want to build something", or "what's hot on Stellar right now". Interviews user sharply, then proposes ranked ideas grounded in real ecosystem gaps from the LumenLoop 728-project database and current SCF funding patterns.

日本語の概要は準備中です。原文の説明を表示しています。

Interviews the user section by section to collaboratively produce design documents. Use when creating a design doc, starting feature design, or when the user invokes the design command.

日本語の概要は準備中です。原文の説明を表示しています。

Use to run or continue domain exploration with the product owner as domain expert — event storming interviews, hotspots (HS), ubiquitous language, UX review of the domain, checking or resolving open MQ/UX items, or a status summary of documents/ddd. Also use when the user starts explaining their business, purpose or workflow. Never edit documents/ddd directly; go through this skill.

日本語の概要は準備中です。原文の説明を表示しています。

提案書と初期調査結果からインタビューガイド（質問リスト）を作成するスキル。「インタビューガイドを作成して」「質問リストを作って」「ヒアリング項目を整理して」などのリクエスト時に使用。提案書の論点に対応した検証・補強事項を整理し、想定インタビュー対象者のペルソナと具体的な質問設計を行う。論点に対して明確な答えを得られる構成で設計する。

クライアントの与件情報と打ち合わせメモから、意思決定に直結する調査プロジェクト提案書（スライド骨子/Markdown）を一発で作成するスキル。「提案書を作成して」「提案書を作って」「プロポーザルを作成して」などの依頼、または与件ファイル（例：与件.md）を指定して提案書作成を依頼された場合に使用する。単なる章立てではなく、調査の観点・仮説・参入障壁や供給構造・会議転用可能なアウトプットまで落として提案する。インプットや指示からデプスインタビューが必要と推測できる場合のみ、インタビュー前提の設計を含める。

インタビューガイドの対象者タイプと候補者リストから最適な対象者を選定・評価するスキル。「インタビュー対象者を選定して」「候補者を評価して」「エキスパートリストから対象者を選んで」などのリクエスト時に使用。論点への対応力を軸に適合性を評価し、優先順位付けされた推奨候補リストを作成する。

インタビュー文字起こしと質問リストから詳細な議事録を作成するスキル。「インタビュー議事録を作成して」「インタビューメモから議事録を作って」「ヒアリング内容を整理して」「文字起こしから議事録を作って」などのリクエスト時に使用。インタビュー・ヒアリング・文字起こしが対象。会議やミーティングの議事録には meeting-minutes-creator を使用すること。質問リスト（.md/.txt）とインタビュー文字起こし（音声認識出力など）を入力として、プロフィール、ファクトサマリ、インタビュー内容、逐語録を含む包括的な議事録を生成する。

Plan the first months at a new Japanese employer after an offer is accepted, listing every expectation and promise made in interviews, the offer, or negotiation with its source, separating what is in writing from what was only said and what has no agreed measure, working out when the probation period ends and whether its criteria and conditions are known, and scheduling who to confirm what with before and after the start date. Use when a user has accepted an offer and wants to prepare for joining, make sure verbal promises such as remote days or a future role are confirmed, or understand what the probation period means for them; do not use to predict whether they will fit in or pass probation, to judge their manager or colleagues, to rule on the legality of probation terms, or to contact the new employer.

日本語の概要は準備中です。原文の説明を表示しています。

Lay out how a job search will actually run alongside a current job: the hours available each week and what they go to, how weekday daytime slots for interviews will be found, which routes to use (direct applications, job boards, scout sites, agents, referrals, public employment services) and what each one discloses to whom, how to keep the search from reaching the current employer through public profiles or workplace equipment, a single tracker of every application's stage, next action, and deadline, and a date and conditions for reviewing, reducing, or pausing the search. Use when someone has decided to start looking, or to gather information while employed, and asks how to fit it in, which routes to use, whether the applications they are running fit the time they have, or how to keep track of them; do not use to decide whether to change jobs, to pick or rate employers or job postings, to predict outcomes, or to send applications, publish profiles, or contact agents on the user's behalf.

日本語の概要は準備中です。原文の説明を表示しています。

Check the working conditions of a Japanese job offer item by item against the conditions an employer states in writing, compare the offer letter or 労働条件通知書 with the job posting and what was said in interviews, and separate what is confirmed in writing from what is still only verbal. Use when a user has received an offer, a working-conditions notice, or an employment contract and wants to know what is missing, what conflicts with earlier statements, and what to confirm before the acceptance deadline; do not use to rule on whether the terms are lawful, to decide whether to accept or decline, or to contact the employer on the user's behalf.

日本語の概要は準備中です。原文の説明を表示しています。

Prepare a request to change the terms of a Japanese job offer before accepting it, sorting what the user wants changed (pay components, start date, work style, location, title, probation) by priority, tying each ask to a basis the user can show (the written offer, the job posting, what was said in interviews, their own records), working the timing back from the acceptance deadline, and drafting the message to the employer or recruiting agent. Use when a user has an offer and wants to ask for higher pay, a later start date, more remote days, or other changed terms, or wants to know how to raise it without losing the offer; do not use to predict whether the request will succeed, to set a target figure from market rates, to fabricate a competing offer, to decide whether to accept, or to send anything to the employer.

日本語の概要は準備中です。原文の説明を表示しています。

Interview the user in rounds until no branch of the design tree stays open.

日本語の概要は準備中です。原文の説明を表示しています。

A serif-led magazine aesthetic: terracotta accent on warm off-white paper. Good for long-form, editorial, and brand-led marketing pages. "A New Yorker interview column online.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants to evolve the features of a PRD roadmap with user stories — 'refinar as histórias da feature', 'escrever histórias de usuário', 'critérios de aceite', 'regras de negócio da feature', 'deixar a feature pronta', 'user stories for FT01' — one feature at a time, interviewing the human until each story meets the Definition of Ready: persona, value, INVEST, CA (Gherkin, happy and error paths) and RN from the PRD. Do NOT use to create the roadmap (prd-roadmap) or to change requirements without stories (prd-refine).

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants a new Product Requirements Document — 'criar um PRD', 'escrever os requisitos de', 'new PRD for', 'documento de requisitos' — through a 12-step interview, one question at a time, ending with an approval gate. Do NOT use to change an existing PRD (prd- refine) or to plan implementation.

日本語の概要は準備中です。原文の説明を表示しています。

Discover and approve feature requirements through focused interviewing and repository research. Use when the user has a feature idea, unclear scope, conflicting requirements, or needs Flow context artifacts before design.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user wants a full feature action plan (backend + frontend + tests) with the PWDEVIA 7-question method before any code is written — 'planejar a feature X', 'criar plano de feature', 'plan the user CRUD'. Interviews the human (max 2 rounds) and writes .planning/feat/features/{slug}/plan.md. Do NOT use to write code (feat-exec), for small 1–3 file changes (feat-quick), backend-only or UI-only scope (feat-backend / feat-frontend), tests for existing code (feat-test) or code review (feat-review).

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see page-cro.

日本語の概要は準備中です。原文の説明を表示しています。