「draft」の検索結果

Bootstrap a Claude-assisted on-call for this channel/repo: discover the available connectors, mine incident history into draft triage playbooks, interview the human for policy, validate against held-out incidents, and install the scheduled routines. Use when the user wants to "set up on-call", "bootstrap the on-call kit", "onboard this channel", or has just installed the oncall-kit plugin. Five gated phases — never run more than one phase per turn, and never activate anything before Phase 4 sign-off.

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

Use when an agent is asked to draft, rewrite, edit, review, polish, copyedit, simplify, humanize, or create written prose, including creative writing, essays, posts, scripts, speeches, emails, documentation, product copy, and other style-sensitive text. Apply George Orwell's six rules and ASD-STE100 Simplified Technical English as a plain-English discipline while preserving the user's intended meaning, audience, tone, and explicit constraints.

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

Lightweight standalone design spec for AI coding agents: codebase scan → bounded clarify pass (3–5 questions, not a grill) → reviewed design doc written to docs/plans/ → independent scored review → stop. No task board, no build. Use when you want a spec to discuss, hand off, or review before committing to implementation. Chains into absolute-work when ready to build. Triggers on "absolute spec", "write a spec", "spec out this feature", "draft a design doc", "I want a spec to hand off / review, don't build it yet".

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

Refine a Stage2 NeurIPS rebuttal draft into polished, reviewer-facing prose in the author's style; preserve factual grounding, optionally prepend a courteous opening phrase, and normalize tables/code/formulas into Markdown.

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

Refine a Stage2 ARR (ACL Rolling Review) rebuttal draft into polished, reviewer-facing prose in the author's style; preserve factual grounding, optionally prepend a courteous opening phrase, and normalize tables/code/formulas into Markdown.

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

Refine a Stage2 ICML rebuttal draft into polished, reviewer-facing prose in the author's style; preserve factual grounding, optionally prepend a courteous opening phrase, and normalize tables/code/formulas into Markdown.

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

Refine a Stage2 ICLR rebuttal draft into polished, reviewer-facing prose in the author's style; preserve factual grounding, optionally prepend a courteous opening phrase, and normalize tables/code/formulas into Markdown.

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

Remove AI-generated writing patterns from rebuttal prose to make it sound natural, direct, and authentically human-authored. Use when a Stage 2 refined draft or Stage 4 follow-up response reads too formulaic, robotic, or "GPT-like". Supports academic English.

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

Condense Stage 3 combined discussion content into compact markdown context for Stage 4 multi-round follow-up drafting.

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

Refine a Stage 4 follow-up response using condensed prior discussion context, current follow-up question, and the user's draft.

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

Use when drafting or revising internal technical design docs, review notes, architecture writeups, or sharing posts in Chinese, especially when the tone should stay evidence-backed, calm, and suitable for peers or leaders rather than marketing or literary writing.

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

Use Xquik to fetch X (Twitter) data or act through a connected account. It covers search, profiles, followers, replies, threads, timelines, media downloads, bulk exports, trends, monitors, signed webhooks, draws, posts, likes, follows, DMs, and AI analysis of posts (sentiment, brand mentions, news, market signals, viral score, custom labels). Also use for hashtag or @handle tracking when no other network is named, Xquik MCP setup, pricing, and X API comparisons. Skip data from other social networks, code that stays on the official X API (such as tweepy with an X developer bearer token), official X widget implementation, and content drafting or analysis without an API task. Not affiliated with X Corp.

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

Design multi-touch outbound email sequences with personalized messaging, timing cadences, and conversion-aware copy for prospecting or re-engagement. Use when the user needs a coordinated sales campaign across several touches; use email-drafting for a single message or reply.

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

Draft Terms of Service documents for web applications, SaaS platforms, and digital marketplaces. Use when the user requests terms of service generation or provides relevant inputs for this workflow.

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

Think and work like an expert Agricultural Engineer. Use when a task calls for Agricultural Engineer judgment. Reasons from mass, energy, and momentum balances on variable biological media through ET-based scheduling, psychrometric grain-drying balances, ASABE D497 draft estimates, EPANET pipe networks, and RTK-GNSS/ISOBUS precision-ag validation while treating soil compaction, clogged drip emitters, grain-bin hotspots, GPS drift, and uncalibrated yield monitors as first-class failure modes.

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

Plan, prompt, iterate, edit, migrate, and quality-check still-image work made with Midjourney's documented website and Discord interfaces. Use for Midjourney model and parameter selection, image/style/Omni references, Draft or Conversational workflows, typography-aware production, privacy and rights review, or troubleshooting a Midjourney image pipeline; do not use it to invent or automate an unsupported Midjourney API.

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

Designs Bayesian clinical trials including Phase I dose-finding (BOIN, CRM, EWOC, mTPI-2), meta-analytic-predictive (MAP) priors with robust mixtures for external data borrowing, EXNEX for basket trials, hierarchical models for safety AE (Berry-Berry), Bayesian platform trials (I-SPY 2, GBM AGILE, REMAP-CAP), and posterior probability stopping rules. Covers FDA Bayesian Devices Guidance (2010), FDA Bayesian Methodology in Drugs Draft (January 2026), BOIN Fit-for-Purpose qualification (December 2021), and Project Optimus dose-optimisation. Use when designing dose-finding studies, platform trials, or sensitivity analyses with informative priors.

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

Designs adaptive clinical trials including group-sequential (O'Brien-Fleming, Pocock, Lan-DeMets spending), sample-size re-estimation (blinded Friede-Kieser, unblinded Cui-Hung-Wang, Mehta-Pocock promising zone), seamless Phase 2/3 with treatment-arm selection, population enrichment, and response-adaptive randomisation. Covers FDA 2019 Final Adaptive Designs Guidance, FDA 2022 Master Protocols, and ICH E20 Step 2b/3 draft (June 2025, NOT final). Use when planning interim analyses, sample-size re-estimation, or master/platform-trial designs.

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

Sector-specific Plain Language standard for legal communication (ISO 24495-2:2025). Applied during contract drafting, license review, and legal/compliance writing.

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

Transform vague product ideas into evidence-anchored problem statements for PRD v0.1 Spark. Triggers on starting new products/features, validating market opportunities, drafting PRD Why sections, or requests like "frame the problem", "define pain points", "write problem statement", "start v0.1", "what problem are we solving". Outputs structured problem tables with CFD evidence IDs.

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

Cut a new TMDb release — work out the next SemVer version from the evidence, do the pre-tag housekeeping a tag would otherwise freeze in place, draft release notes, then tag and publish the GitHub release. Presents the version (with its reasoning) and the full notes for approval and STOPS; nothing is tagged or published until you say go.

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

Adversarially review the current implementation plan with three independent critic subagents, reconcile their findings into a consensus, and apply the agreed feedback to the plan. Use after drafting a plan (in plan mode or a plan/design doc) and before starting implementation, or whenever the user asks to pressure-test, critique, or harden a plan.

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

Короткие русскоязычные посты для Telegram, LinkedIn, Instagram и других соцсетей: пост с нуля, пост из статьи, анонс в канал, переписывание первой строки, усиление хука и финала. Use this skill whenever the user asks to write, rewrite, draft, shorten, or improve a Russian social media post, Telegram channel post, LinkedIn post, Instagram caption, channel announcement, post from an article, or first-line hook. Триггеры: «пост в телеграм», «пост для канала», «пост в LinkedIn», «пост в Instagram», «короткий пост», «напиши пост», «анонс в канал», «пост из статьи», «первая строка не цепляет», «перепиши пост». Для статей и лонгридов см. skill statya; для лендингов и продающих страниц — promo; для интерфейса — ux-copy.

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

Редактура текстов на русском языке по методу Людмилы Сарычевой — от смысла к словам, а не наоборот. Use this skill whenever the user asks to edit, review, improve, shorten, or polish any Russian-language text — articles, posts, emails, landing copy, docs. Триггеры: «отредачь», «отредактируй», «почисти текст», «сократи», «перепиши по-человечески», «убери канцелярит», «сделай проще», «причешите текст», «дай фидбек на текст», «разбери мой текст», «слишком водянисто», «звучит как робот». Also trigger when the user pastes a Russian draft and asks what's wrong with it or how to make it better. Для написания текста с нуля см. skill statya; для текстов интерфейса — ux-copy.

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