「drafting」の検索結果

Builds a new Claude Code agent (subagent) from scratch through a relentless, evidence-based interview that walks the agent's design tree decision-by-decision — entity fit, domain focus and vocabulary, role identity, anti-patterns, description, model tier, tools, and self-containment — then reviews the finished agent against the plugin-building guidance and applies every fix it finds. Use when creating, authoring, scaffolding, designing, or drafting a new agent or subagent. Does not build a skill or slash command — use skill-builder. Does not serve, vendor, or refresh the authoring guidance itself — use guidance.

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

Generate a PR description from the current branch's changes against a GitHub PR, using the gh CLI. Use when writing, drafting, or updating pull request descriptions, PR summaries, or PR bodies. Does not review code or post review comments — use code-review for local review or post-code-review-to-pr for posting a review to GitHub.

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

Turn vague or partially formed AI, computer-science, data-driven, and engineering-method research directions into evidence-grounded, falsifiable, paper-ready Research Idea Briefs through heuristic questioning, staged confirmation, literature positioning, novelty attack, and method-figure planning. Use when the user needs to clarify a research idea, formalize inputs/outputs/objectives/constraints, frame background and motivation, select 3-5 anchor papers, identify a defensible gap, derive 2-3 contributions, stress-test novelty, or design an input-to-output method framework and core-paper figure. Also trigger on requests such as 明确科研 idea、启发式梳理 idea、互动追问科研问题、梳理论文创新点、定义研究任务、找对标论文、把研究方向变成论文方案、画方法框架图. Do not use as the primary workflow for running experiments, exhaustive systematic reviews, drafting full manuscript sections, or polishing finished prose.

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

Draft professional, empathetic customer-facing responses adapted to the situation, urgency, and channel. Use when responding to customer tickets, escalations, outage notifications, bug reports, feature requests, or any customer-facing communication.

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

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

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

Generate personalized outreach messages using Common Room signals. Triggers on 'draft outreach to [person]', 'write an email to [name]', 'compose a message for [contact]', or any outreach drafting request.

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

ACTIVATE when preparing for board meetings, creating board decks, drafting board materials, developing executive summaries for directors, writing talking points, crafting board agendas, addressing governance matters, preparing for investor questions, or managing board communication. Critical for any board-facing materials, shareholder communication, or governance compliance.

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

ACTIVATE when drafting all-hands speeches, investor updates, quarterly letters to stakeholders, press statements, CEO announcements, crisis communications, customer updates, or any mission-critical communication to employees, investors, customers, or media. Executive communications require persuasion, clarity, emotional intelligence, and alignment with company values and strategy.

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

Triage a GitHub issue using diagnostics archives and logs. Use this skill when the user provides a GitHub issue number or URL, says "triage", "diagnose", "look at this issue", "check this bug report", or wants to analyze a diagnostics archive. Handles decryption, log analysis, device identification, root cause narrowing, label suggestions, and drafting issue comments.

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

Write outbound promotional copy for a product or project: launch and update posts for community platforms and social media, store page descriptions and short blurbs, landing page headlines and calls to action, press-style announcements, and the naming of a product for another language or market. Covers what may be disclosed publicly, keeping claims traceable to shipped changes, and writing a headline that carries information instead of hype. Use when drafting or revising anything aimed at people who do not use the product yet, and when deciding whether a link, key, price, or unreleased detail can appear in public copy.

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

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

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

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 privacy-policy language and a review checklist tailored to a business model, data practices, and relevant jurisdictions. Use when the user requests a privacy policy or needs to map disclosures for GDPR, CCPA, or similar frameworks; do not use it to guarantee legal compliance.

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

Draft a professional, audience-aware email or reply with calibrated tone and a clear call to action. Use when the user needs one message, response, follow-up, support note, or meeting request; use sales-email-sequences for a coordinated multi-touch outbound campaign.

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

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

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

Provisional task skill for organisational plain language implementation (based on ISO/CD 24495-4, committee draft). Activates for plain language gap analysis, policy drafting, review workflow design, and organisational readiness for the future published standard. Does not activate for ordinary writing, rewriting, or reviewing of individual documents.

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

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.

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

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.

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

Use when the user wants to start or reposition a Xiaohongshu account but is asking "what should I post" before clarifying monetization, timing, personal IP direction, or trust path. Trigger phrases: "小红书定位", "不知道做什么赛道", "怎么变现", "个人IP", "账号方向", "XHS positioning", "monetization first". Do not use for drafting a specific post; use topic or copy skills after positioning is clear.

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

Use when the user wants WorkBuddy or another agent to remember an account's positioning, voice, boundaries, data, trust assets, personal IP story, and content rules across sessions. Trigger phrases: "账号档案", "记住我的账号", "写入记忆", "人设垂直", "信任名片", "brand profile", "account memory", "style guide". Do not use for one-off post drafting unless profile data is missing.

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

Strip AI writing tells from Rove's user-facing prose — README, the docs/ pages that sync to docs.rove.run, landing copy, and release notes. Use when the user says "unslop", "洗一下文案", "这读起来像 AI 写的", or after drafting any user-facing page. Adapted for this repo from cursor/plugins pstack/skills/unslop.

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

Use when the user wants to start or reposition a Xiaohongshu account but is asking "what should I post" before clarifying monetization, timing, personal IP direction, or trust path. Trigger phrases: "小红书定位", "不知道做什么赛道", "怎么变现", "个人IP", "账号方向", "XHS positioning", "monetization first". Do not use for drafting a specific post; use topic or copy skills after positioning is clear.

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