1.2万 件 ・ 関連度順
概要と使いどころ
Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Write press releases for product launches, funding announcements, partnerships, executive hires, and milestones using the Inverted Pyramid (AP journalism) and Ogilvy on Headlines (David Ogilvy, Ogilvy on Advertising). The lede answers Who/What/When/Where/Why in 40 words or fewer. The headline selects the right audience and promises a specific benefit. Use when the user asks for a press release, media release, news announcement, PR for X, launch announcement, funding announcement, or "write a press release". Reads brand voice and positioning from knowledge/. For pitching it to a journalist, see pr-pitch-writer. For the customer story behind it, see case-study-writer.
日本語の概要は準備中です。原文の説明を表示しています。
Capture learnings from a campaign, launch, sprint, or initiative using Five Whys (Taiichi Ohno, Toyota Production System) for root cause analysis and Start-Stop-Continue for action planning. Append reusable insights to knowledge/learnings.md so future runs of the OS get smarter. Use when the user asks for a retro, retrospective, post-mortem, "what did we learn", "campaign wrap-up", "lessons learned", or after a campaign or launch ends. Critical feedback loop that makes the OS compound over time. For the numbers review itself, see kpi-review. For planning the next campaign, see campaign-brief.
日本語の概要は準備中です。原文の説明を表示しています。
Decompose large epics into sprint-ready sub-epics using 9 splitting patterns. Use this skill when: - A spec is approved and you need to break a large feature into estimable work items for engineering - You want to split an epic that is too large for a single sprint - You need sized sub-epics with story point estimates for sprint planning - You are preparing for engineering handoff and need to identify work packages
日本語の概要は準備中です。原文の説明を表示しています。
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
日本語の概要は準備中です。原文の説明を表示しています。
Maintain a centralized living risk register across projects. Use this skill when: - You need to create or update a risk register for a project or feature - You want to consolidate risks from individual specs into one register - You need to review and update risk status, mitigations, and owners - You want a cross-project risk view
日本語の概要は準備中です。原文の説明を表示しています。
Synthesize sprint retrospective notes into categorized action items and patterns. Use this skill when: - You have sprint retro notes (raw text, meeting transcript, or structured notes) to process - You need to identify recurring patterns across multiple retros - You want categorized action items with owners and deadlines from retro discussions
日本語の概要は準備中です。原文の説明を表示しています。
Generate structured weekly or fortnightly status updates for leadership and stakeholders. Use this skill when: - You need to prepare a weekly or fortnightly status report - You want to summarize recent progress across git commits, tickets, and spec changes - You need a formatted update ready for Slack, email, or a stakeholder meeting - You want multi-project updates in one report
日本語の概要は準備中です。原文の説明を表示しています。
Plan a marketing campaign end-to-end using Allan Dib's Before/During/After framework (The 1-Page Marketing Plan). Produces a phase-specific campaign brief with goal, audience, message, channels, assets, timeline, budget, and success metrics. Use when the user asks to plan a campaign, brief a campaign, "we need a campaign for X", launch plan, GTM plan, marketing plan for <product>, demand gen plan, or any multi-channel marketing initiative. Reads ICP, services, and KPIs from knowledge/. For a full quarterly strategy rather than one campaign, see marketing-plan scope in positioning-doc and kpi-review. For the content schedule inside the campaign, see social-calendar. For the post-campaign review, see retro.
日本語の概要は準備中です。原文の説明を表示しています。
Write a high-performing LinkedIn post in the user's brand voice using Hook-Story-Offer (Russell Brunson) and the Curiosity Gap hook method (George Loewenstein). Every post starts by selecting a named hook formula - specific number + surprising result, contrarian statement, personal confession, direct challenge, or before/after. Use when the user asks for a LinkedIn post, LinkedIn update, LinkedIn content, "post for LinkedIn", thought-leadership post, founder post, or short professional social content. Reads brand voice and ICP from knowledge/ so output sounds like the company, not generic AI. For long-form opinion pieces, see thought-leadership-writer. For the monthly posting plan, see social-calendar. For turning one asset into many posts, see content-repurposer.
日本語の概要は準備中です。原文の説明を表示しています。
Write marketing content in the user's brand voice using PAS (Problem-Agitate-Solution) and AIDA (Attention-Interest-Desire-Action) copywriting frameworks. Use when the user asks to write a LinkedIn post, blog article, email, ad copy, landing page section, social post, newsletter, or any short-to-medium form marketing content. Reads brand voice and ICP from knowledge/ so the output sounds like the company, not like generic AI. For improving copy that already exists, see copy-review. For a landing page specifically, see landing-page-writer. For a LinkedIn post, see linkedin-post. For long-form POV, see thought-leadership-writer.
日本語の概要は準備中です。原文の説明を表示しています。
Write a data pipeline design document. Use when the user says "pipeline design doc", "document this pipeline", "pipeline architecture doc", "data flow document", "how does this pipeline work", "design doc for ETL", "pipeline spec", or needs to capture the architecture, data flow, and operational details of a data pipeline - even if they don't explicitly say "design doc".
日本語の概要は準備中です。原文の説明を表示しています。
Create Jira tickets from meeting notes, user stories, or quick lists. Use this skill when: - User says "create tickets", "make Jira tickets from", "push to Jira" - User has meeting action items to convert to tickets - User has user stories from a spec to push to the backlog - User wants to batch-create tasks, stories, or bugs
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Environmental Economist — valuing a non-market environmental good (clean air, a wetland, an endangered species) for a benefit-cost analysis, building a regulatory impact analysis (RIA) for a pollution rule, sizing natural resource damages after a spill or contamination event, or picking a discount rate for a policy with cost and benefit streams decades apart.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Engine and Other Machine Assembler — following the specified multi-stage torque sequence for a multi-bolt joint rather than tightening bolts to final value in convenient order, measuring bearing clearance directly rather than confirming free rotation by hand, verifying critical clearances on the actual assembled stack-up rather than trusting individually-in-tolerance components, or testing sub-assemblies before final integration rather than only at final test.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Electrical and Electronic Engineering Technologist/Technician — bench-testing a prototype board against a power or timing spec, isolating a resistive fault in a power path with node-to-node voltage-drop measurements, checking whether an oscilloscope's own bandwidth is limiting a rise-time measurement before trusting it, running a power-supply load-regulation sweep, or evaluating ESD-event provenance and IPC-A-610 acceptance on a returned unit.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Electrician — sizing a service panel upgrade with an NEC load calculation, troubleshooting a tripping breaker or dead circuit systematically, checking wire gauge/ampacity and voltage drop for a circuit run, resolving a code-vs-inspector interpretation dispute, or deciding when a job (aluminum wiring, knob-and-tube, undersized service) exceeds the immediate scope.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an embalmer — assessing a case's decomposition stage and preservation difficulty, calculating an arterial-fluid dilution ratio for a specific case condition, choosing a restorative-art approach for trauma or discoloration, or working through a bloodborne-pathogen exposure-control decision.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a rotary drill operator (driller) — diagnosing a drilling break or kick warning sign, running well-control shut-in and kill-mud-weight calculations, setting trip margin and swab/surge limits before pulling out of hole, optimizing weight-on-bit and RPM against mechanical specific energy, or reviewing a rig-floor near-miss.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Electromechanical Equipment Assembler — verifying shaft/coupling alignment directly rather than trusting an initial functional test that only confirms the device runs, applying fastener torque to spec with a calibrated tool rather than by feel, routing wire to account for the equipment's full range of motion rather than its static assembled position, or distinguishing electrical from mechanical root cause when a device malfunctions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an electric-motor and power-tool repairer — reading a megohmmeter/polarization-index test to catch a winding fault before failure, deciding rewind vs. replace on a failed induction motor, isolating a bearing fault from a broken-rotor-bar fault, judging brush/commutator wear on a universal motor, or evaluating whether a rewind was actually done to spec.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a cytotechnologist — screening a gynecologic (Pap test) slide and applying Bethesda System criteria, assessing non-gynecologic specimen adequacy (FNA rapid on-site evaluation, body fluid, brushing) against the relevant reporting system, deciding whether a finding can be signed out independently or must be referred to a pathologist, or auditing screening quality metrics (ASC:SIL ratio, rescreen concordance, workload compliance). A reasoning aid, not a substitute for a certified cytotechnologist or pathologist signing out an actual case.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Nutrition and Dietetics Technician, Registered (NDTR/DTR) — translating a physician's diet order into a texture/therapeutic tray specification, triaging a nutrition-screening or intake-decline signal for RDN escalation, auditing a tray line or food-safety log against a threshold, or drawing the line between routine dietetics work and a nutrition-diagnosis call that belongs to the supervising RDN.
日本語の概要は準備中です。原文の説明を表示しています。