4,594 件 ・ 関連度順
概要と使いどころ
Write a vulnerability report. Use when the user says "vulnerability report", "vuln report", "security finding", "write up this finding", "pentest finding", "bug bounty report", "security disclosure", "CVE writeup", "document this vulnerability", "how to report a security issue", or needs to formally document a security vulnerability with evidence, impact, and remediation guidance - even if they don't explicitly say "report".
日本語の概要は準備中です。原文の説明を表示しています。
Write a compelling sales proposal. Use when the user says "write a sales proposal", "put together a proposal", "draft a proposal for this prospect", "create a business case", "write up our recommendation", "how to structure a proposal", "proposal template", "executive summary for a deal", or wants to create a written document that moves a prospect toward a decision.
日本語の概要は準備中です。原文の説明を表示しています。
Plan a webinar end-to-end using April Dunford's Obviously Awesome positioning framework to find the topic angle that makes the webinar obviously valuable to the right audience. Produces topic positioning, abstract, speaker brief, registration page, promotion sequence, day-of run-of-show, and post-webinar follow-up. Use when the user asks to plan a webinar, virtual event, online workshop, "we need a webinar on X", host a webinar, online masterclass, or any live virtual event with promotion and follow-up. Reads ICP, services, and brand voice from knowledge/. For the promotion emails, see email-nurture. For the deck, see ppt-maker. For the social promotion plan, see social-calendar.
日本語の概要は準備中です。原文の説明を表示しています。
Structure and run a post-interview candidate debrief. Use when the user says "run the debrief", "how do we decide on this candidate", "let's calibrate", "we need to make a hire/no-hire call", "prep the debrief meeting", or wants to structure the decision-making process after interviews are complete - even if they don't explicitly say "debrief". Also use when a recruiter wants to prevent groupthink or HiPPO effect (highest paid person's opinion) from dominating the decision.
日本語の概要は準備中です。原文の説明を表示しています。
Allocate testing effort based on risk and failure likelihood using Google's SET/SWE/TE model. Use when user says "risk-based testing", "where should I focus testing", "test coverage strategy", "prioritize what to test", "high risk areas", or needs to decide how to distribute QA effort across a codebase - even if they don't explicitly say "risk-based".
日本語の概要は準備中です。原文の説明を表示しています。
Write SEO-optimized long-form articles targeting specific keywords using the They Ask You Answer Big 5 framework (Marcus Sheridan). Articles are categorized by Big 5 type (Cost, Problems, Versus, Best/Reviews, How-To) and structured accordingly. The "answer first" rule applies to every article. Use when the user asks for an SEO article, blog post for ranking, "rank for keyword X", organic content, search-optimized post, pillar page, or content for organic traffic. Includes keyword targeting, search intent matching, internal linking suggestions, and meta tags. For improving an existing article, see copy-review. For deciding what to write about, see social-calendar pillars and icp-research. For repurposing it, see content-repurposer.
日本語の概要は準備中です。原文の説明を表示しています。
Run product discovery to identify what to build. Use when the user says "product discovery", "how do I know what to build", "validate this idea", "talk to customers", "are we building the right thing", "discovery process", or wants to reduce the risk of building something users don't want - even if they don't say "discovery".
日本語の概要は準備中です。原文の説明を表示しています。
Build a velocity-based release roadmap with risk buffers. Use when the user says "release plan", "when will we ship", "plan the next release", "map sprints to milestones", "estimate our release date", "how many sprints until done", or wants to translate a backlog into a delivery timeline - even if they don't say "release planning". Based on "Agile Estimating and Planning" by Mike Cohn (velocity, story points, cone of uncertainty, risk buffers).
日本語の概要は準備中です。原文の説明を表示しています。
Build Opportunity Solution Trees using Teresa Torres' framework for structured product discovery. Use this skill when: - You need to map a desired outcome to opportunities, solutions, and experiments - You want to decide WHAT to build next based on user research and discovery data - You have workshop findings, pilot feedback, or user research to structure into actionable options - You need a visual tree diagram showing the path from outcome to testable experiments
日本語の概要は準備中です。原文の説明を表示しています。
Rate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".
日本語の概要は準備中です。原文の説明を表示しています。
Write an empowered team brief. Use when the user says "team brief", "product brief", "give the team a problem", "empowered team", "how do I brief engineering", "delegate to the team", "product mission", or wants to give a team clear goals without dictating the solution - even if they don't say "team brief".
日本語の概要は準備中です。原文の説明を表示しています。
Write a clear pull request description. Use when the user says "write a PR description", "PR template", "pull request description", "how do I describe this change", "commit message for this", "document this change", "open a PR for", or is about to merge code and needs to communicate what changed and why - even if they don't explicitly say "PR description".
日本語の概要は準備中です。原文の説明を表示しています。
Write a blameless postmortem after an incident. Use when the user says "postmortem", "post-incident review", "PIR", "what happened in that incident", "incident review", "blameless postmortem", "5 whys", "how do we prevent this again", or needs to document learnings from a production incident - even if they don't explicitly say "postmortem".
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user says "write a cold email to investors", "investor outreach email", "how do I cold email a VC", "fundraising cold outreach", "email to angel investor", "reach out to investors", "get a meeting with investors", "intro email for fundraising", "follow up with investor", "warm intro email", or wants to draft any outbound investor communication to generate a first meeting or advance a fundraising conversation.
日本語の概要は準備中です。原文の説明を表示しています。
Assess whether your leadership behaviors amplify or diminish your team using Liz Wiseman's Multipliers framework. Use when a leader asks "am I a good manager", "why isn't my team performing at their potential", "I feel like I'm doing all the thinking for my team", "my team seems dependent on me", "I want to be a better leader", "how do I empower my people", or "my team is smart but underperforming". Also trigger when someone describes always having the best ideas in the room, team members not taking initiative, reports waiting for direction before acting, or a leader who feels exhausted from carrying the team. Diminisher patterns are often invisible to the leader exhibiting them.
日本語の概要は準備中です。原文の説明を表示しています。
Design clean and consistent APIs. Use when the user says "design an API", "API design review", "design these endpoints", "REST API for X", "GraphQL schema", "API contract", "how should this endpoint work", "review my API design", or wants to create or improve an API interface - even if they don't explicitly say "API design".
日本語の概要は準備中です。原文の説明を表示しています。
Critique a design for usability, hierarchy, and accessibility. Use when the user says "critique this design", "review this screen", "what's wrong with this UI", "design feedback", "UX review", "how can I improve this", "review my mockup", "is this good UX", or shares a design and wants structured feedback - even if they don't explicitly say "design critique".
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user says "write my investor update", "monthly update for investors", "quarterly investor email", "investor communication", "LP update", "board update", "shareholder update", "what do I tell my investors this month", "how do I write a good investor update", or wants to communicate progress, metrics, and needs to existing investors or board members on a recurring basis.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user says "write my pitch", "help me tell my startup story", "craft my investor narrative", "why now slide", "what's our secret", "how do I explain what we do", "make my pitch compelling", "pitch deck story", "elevator pitch", "why will we win", "contrarian insight", or wants to build a persuasive, coherent narrative around their startup for investors, press, or recruiting.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze competitors using Blue Ocean Strategy's ERRC Grid and Strategy Canvas (W. Chan Kim and Renee Mauborgne) to identify uncontested market space, not just who is better on the same axes. Produces an ERRC Grid, Strategy Canvas, positioning matrix, messaging comparison, and differentiation map. Use when the user asks for competitive analysis, competitor research, "how do we compare to X", positioning vs competitors, market landscape, "analyze our competition", "where is the blue ocean", or wants to update competitor docs. Writes to knowledge/markets/competitors.md. For a lightweight competitor summary in the knowledge base, see brand-context. For positioning against them, see positioning-doc.
日本語の概要は準備中です。原文の説明を表示しています。
Structure and run effective 1:1 meetings with direct reports using Camille Fournier's Manager's Path and Andy Grove's High Output Management frameworks. Use when a manager says "help me structure my 1:1s", "my 1:1s feel like status updates", "I don't know what to talk about in 1:1s", "my reports don't open up", "how do I make 1:1s useful", "what questions should I ask in 1:1s", or "I need a 1:1 template". Also trigger when someone mentions their 1:1s feel transactional, that they keep canceling them, or that they're not sure if their report is happy.
日本語の概要は準備中です。原文の説明を表示しています。
Navigate a new leadership role using Michael Watkins' First 90 Days 30/60/90 framework. Use when someone says "I just started a new role", "I'm starting as a new manager", "I joined a new company as a leader", "I was just promoted", "how do I onboard as a leader", "what should I do in my first 30 days", "I inherited a team", "I need a 90 day plan", or "I'm new to this team". Also trigger when someone describes feeling overwhelmed in a new leadership role, unsure where to start, or tempted to make changes too quickly before they've listened. Applies to first-time managers, leaders joining new companies, and leaders moving into new functions or teams within the same company.
日本語の概要は準備中です。原文の説明を表示しています。
Write unit and integration tests. Use when the user says "write tests for this", "add test coverage", "how do I test this", "TDD", "red green refactor", "unit test this function", "test this module", "I need tests for", or has code that lacks tests - even if they don't explicitly say "write tests".
日本語の概要は準備中です。原文の説明を表示しています。
Document and prioritize technical debt. Use when the user says "tech debt", "legacy code", "this code is a mess", "refactoring plan", "we need to clean this up", "paying down debt", "this is hard to change", "how do we fix this codebase", or has code that's difficult to understand or modify - even if they don't explicitly say "technical debt".
日本語の概要は準備中です。原文の説明を表示しています。