「plan」の検索結果

Argues the strongest honest case against a decision, plan, belief, hire, pricing move, strategy, or piece of work the user is leaning toward. Steelmans the other side, ranks at most three objections by consequence, runs a short pre-mortem, credits what the user got right, and ends with what would have to be true for their choice to work. Calibrated and collegial, never combative; says plainly when the position is strong. Use whenever the user says "play devil's advocate", "argue the other side", "poke holes in this", "what am I missing", "am I making a mistake", "talk me out of it", "stress-test this idea", "tell me why this is a bad idea", or asks for pushback on something they have mostly decided. Supports gentle, standard, and hard intensity. Not for interrogating requirements before a build (grill-the-brief) or staging a multi-persona debate (debate-simulator).

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

Create timelines for house down payment, retirement, college fund. Monthly savings targets, investment strategies, milestone tracking.

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

Analyzes a deal in progress and generates a comprehensive closing strategy. Researches the target company, maps the buying committee, builds objection responses, creates competitive positioning, and outputs a tactical deal-playbook.md with next-best-actions and a mutual close plan.

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

Point Cowork at a folder of medical bills and insurance EOBs -- matches every bill to its explanation of benefits, catches duplicate charges, balance-billing, and bills that ignore your insurance, then drafts the dispute letters and phone scripts. Most medical bills contain errors; this finds them.

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

Cleans up CRM data from HubSpot, Salesforce, Pipedrive, Zoho, Close, Attio, or any CRM CSV export. Finds duplicate contacts and companies with fuzzy matching (not just exact email), normalizes emails, phones to E.164, names, domains, states, and countries, flags stale, invalid, role, and test records, finds broken contact-company associations, and produces a reviewable merge plan plus import-ready files without touching the live CRM. Use this skill whenever the user wants to dedupe, find or merge duplicate contacts, merge companies or accounts, clean up a CRM, prep a CRM migration or re-import, or says the CRM export is a mess. Also use it when they mention only one symptom, like "the same person is in here three times", "half our leads are junk", or "our company records don't match".

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

Designs relational and document database schemas from requirements or an existing app - tables and collections, keys, relationships, constraints, indexes driven by real query patterns, ERDs, and reversible migration scripts - with PostgreSQL (including Supabase) as the default and MySQL, SQLite, and MongoDB supported. Use when the user wants to model data for a new app or feature, review or fix an existing schema, choose keys or indexes, plan multi-tenancy, normalize or denormalize, or write CREATE TABLE statements or migrations, even if they just describe their app and ask "how should I store this". For moving data between database providers, use database-migrator.

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

Interview the user one question at a time to resolve remaining ambiguity before implementation. Use when planning or brainstorming is done but unknowns remain, or when the user asks to be interviewed about a task or spec.

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

Test a consequential technical assumption with a small, falsifiable experiment before committing to an approach. Use when a plan depends on uncertain runtime, integration, or data behavior that inspection alone cannot establish. Not for preference interviews or routine implementation.

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

Vegetation and foliage authoring for Blender including trees, plants, grass cards, canopy LODs, and game-friendly leaf atlases via MCP.

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

Use when starting any Blender asset task, planning a production pipeline, coordinating multiple disciplines, or matching a reference photo/concept art. Invoke for game-ready assets, hard surface, environment, character, creature, export, or any multi-skill Blender workflow.

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

テスト計画書・テストケース・テストレポートの生成に使用。 「テスト計画を作って」「テストケースを生成して」「E2Eテストを書いて」等で発動。

マーケティング計画策定・プロダクトマーケティングコンテキスト作成スキル。 「マーケ計画」「ポジショニング」「ペルソナ作成」「競合分析」「コンテンツ戦略」等で発動。 product-marketing-context.mdを生成し、他のマーケティングスキルの土台を作る。

Generate QA Contract with numbered Gherkin scenarios (G#N) and acceptance criteria (AC#N)

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

Use when drafting an IRB or ethics research protocol. Writes Background, Study Design, Sample Size and Statistical Plan in full prose and leaves institution-specific sections as TODO skeletons. Filling an institutional Word form is /fill-protocol.

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

Use when the user describes a research goal without naming a skill, or the task spans several skills. Classifies the request, plans the order and routes to the right medsci-skills skill(s) instead of producing their output itself.

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

Use when a paper needs publication-ready figures or a visual abstract. Makes ROC, forest, calibration, Kaplan-Meier and Bland-Altman plots, CONSORT/STARD/PRISMA flow diagrams, confusion matrices, pipeline diagrams and journal visual abstracts, checking the journal's AI-image policy first.

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

Use when drafting a grant or challenge proposal for a radiology or medical AI project, including a Korean government industry-academia plan. Structures significance, innovation, approach, aims, milestones and consortium roles, keeping claims evidence-based and executable.

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

Use when planning how many patients or cases a study needs before data collection (power analysis, IRB justification). Walks a decision tree to the right test and returns reproducible R/Python code and IRB-ready justification text. Analyzing collected data is /analyze-stats.

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

Creates clear, testable specifications from feature descriptions with user stories. Use when starting a new feature and needing a spec before planning.

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

Plans, drafts, and refines technical tutorials for developers. Use when writing step-by-step guides or getting-started walkthroughs backed by working code.

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

Designs memory palace structures with spatial layouts and domain organization. Use when creating a new palace or planning knowledge architecture by hand.

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

Inverts burden of proof for code additions. Use when reviewing PRs, planning refactors, or running unbloat to challenge every addition's necessity.

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

Transforms project briefs into testable specifications with user stories and acceptance criteria. Use after brainstorming, before planning.

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

Guides project ideation via Socratic questioning to produce a validated brief. Use before specification when requirements are unclear.

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