386 件 ・ 関連度順
概要と使いどころ
On-demand RAI planner reference pack covering Phase 1 capture, Phase 2 risk classification and the optional Mural board bootstrap, Phase 5 impact assessment, and Phase 6 review and backlog handoff.
日本語の概要は準備中です。原文の説明を表示しています。
Cross-platform PPC strategy planner for ecommerce businesses. Analyzes your product and margins, recommends the right advertising platforms (Google Ads, Meta Ads, TikTok Ads), calculates ROAS targets, allocates budget across channels, and generates platform-specific campaign briefs with ad copy and creative direction. Two modes: (A) Build — design a multi-platform ad strategy from scratch, (B) Optimize — audit existing cross-platform campaigns and reallocate budget. Works for Shopify, WooCommerce, standalone stores, and marketplace sellers expanding to external traffic. No API key required.
日本語の概要は準備中です。原文の説明を表示しています。
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.
日本語の概要は準備中です。原文の説明を表示しています。
Produce the Part 8 yearly planner: quarterly themes and monthly initiatives. "plan the whole year month by month"
日本語の概要は準備中です。原文の説明を表示しています。
Generate a weekly Instagram content plan from a theme, audience, and content pillars. Produces a per-day mix of Reels, carousels, single images, and stories, each with a hook formula, angle, posting time, and primary goal, plus a weekly saves-and-shares goal (the 2026 lever), a story cadence, and a balance check across saves, shares, comments, and follows. Use to plan a week instead of ad-hoc posting. Not for drafting one caption (use ig-caption-writer) or one carousel (use ig-carousel-planner).
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks tax-related questions, wants advice on deductions or tax savings, or needs expert guidance equivalent to a tax accountant (税理士) or life planner. Trigger phrases include: "税金について教えて", "控除は使える？", "確定申告の相談", "節税", "ふるさと納税の上限", "iDeCoの効果", "住宅ローン控除", "青色申告のメリット", "消費税はかかる？", "扶養に入れる？", "配偶者控除", "医療費控除", "法人成り", "経費になる？", "税率を教えて", "所得税の計算", "住民税", "社会保険料", "103万の壁", "130万の壁", "インボイス", "簡易課税", "税制改正", "開業届", "副業バレ", "白色申告", "税務調査", "特定支出控除", "予定納税", "中間納付".
Use Diffusion Planner for nuPlan autonomous-driving trajectory generation: prepare model-ready data, train or resume the diffusion model, configure closed-loop planning, and add differentiable collision or classifier guidance.
日本語の概要は準備中です。原文の説明を表示しています。
CERTIFIED FINANCIAL PLANNER professional providing comprehensive financial planning across all CFP Board practice domains. Integrates retirement, investment, tax, estate, insurance, and education planning following CFP Board Code of Ethics and Standards of Conduct. Use for holistic financial plans, cash flow analysis, net worth statements, insurance needs, estate planning coordination, education funding (529 plans), tax strategies, retirement projections, or CFP Board Practice Standards compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Your Personal Finance Manager for Canadians — an AI financial planning partner that conducts thorough financial interviews, builds complete plans, generates interactive dashboards, and provides ongoing coaching. Use this skill whenever someone asks about budgeting, saving, investing, debt strategy, retirement planning, tax optimization, government benefits, insurance, RRSPs, TFSAs, RESPs, CPP, OAS, or any aspect of personal finance in a Canadian context. Also triggers for "should I buy this?", "can I afford this?", financial check-ins, plan updates, life change impacts on finances, or any request to build or review a financial plan. Even if the user just says "help me with my money" or "I need a budget", this skill should activate. Canada-focused.
日本語の概要は準備中です。原文の説明を表示しています。
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for prompt-injection, retrieval poisoning, memory contamination, planner drift, MCP or tool-boundary abuse, and agent exfiltration challenges. Use when the user asks to analyze prompt injection, retrieval poisoning, memory contamination, planner drift, tool-argument corruption, or secret exposure caused by an agent chain. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
日本語の概要は準備中です。原文の説明を表示しています。
Use on any core for first-run planning intake — Phase 0 runs the vendored BMAD-METHOD planning shelf, shared by every core, and Phase 1 (mining `04-prd.md` into intent records plus the Add-ons/sync-and-remote-entities decision) is full-stack-app's and pwa-app's shared procedure — identical mechanics, a different decision at step 5/8. Phase 0 also defines compressed intake, the path a user's explicit "just build it" choice takes on full-stack-app, pwa-app, authored, and copywriting cores: one batched round of questions in place of the shelf, writing a thinned archive at the same paths so Phase 1 (or, on copywriting, that core's own mining step), `ux-planner`, and the Re-entry pass all keep their documented source. Also use for the Re-entry pass, which mines new scope into additional intents without re-running the shelf, on any core with a module axis to add an intent to (full-stack-app, pwa-app, authored) — landing-page has none, so its own new-scope path runs through `hedgehog-landing-loop`'s Correction Protocol instead. Invoked by the `planner` agent, which decides the path; don't run standalone. landing-page runs this skill's Phase 0 on first run, then mines the same archive through `hedgehog-landing-loop`'s own planning-intake section, that core's counterpart to this skill's Phase 1. copywriting runs this skill's Phase 0 the same way (full or compressed), then mines the same archive through `hedgehog-copywriting-loop`'s own planning-intake section into a what/audience/register brief — no module axis, so its own new-scope path runs through that loop's Correction Protocol rather than the Re-entry pass below. An authored core runs this skill's Phase 0, then `hedgehog-core-design`, then this skill's Phase 1 mining against the designed layer sequence. A brownfield adoption (`hedgehog-adopt`) never runs this skill's shelf at all — the drivers BMAD elicits are already settled facts of a repo that already exists.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end international trip planning: turns "I want to go to X for N days" into a verified, bookable plan — route skeleton across cities, flight price scans (international + domestic legs), train-vs-fly decisions, hour-by-hour daily timelines with opening hours, dwell times, holiday collisions and tappable turn-by-turn map links (小时级行程+地图导航+离线KML), hotel shortlists by neighborhood, budget rollup, and a booking checklist with deep links. Use this whenever the user asks to plan a trip, vacation, itinerary or honeymoon, compare flight dates/prices, pick between cities or routes, schedule a travel day hour by hour, fill a spare block of time ("I'm near X with 2 free hours"), turn a finished plan into a designed page (eight themed renders: illustrated / clay / noir / glass / journal / zine / splash / portal — 插画/黏土/夜航/玻璃/手账/Zine/闪屏/穿越版), or asks 旅行规划/行程安排/机票比价/去某国玩N天怎么安排/现在有空档干嘛/把行程做成好看的网页 — even if they only mention one piece (just flights, just hotels, or just navigation), the playbook and verification rules here still apply.
日本語の概要は準備中です。原文の説明を表示しています。
Use when legacy prompts or older framework flows reference `planner` and you need the modern runtime to resolve that capability cleanly.
日本語の概要は準備中です。原文の説明を表示しています。
Skill体系演进规划 Skill。基于CO-BUILD-LOG（决策轨迹）、PENDING-EXPERIENCES（踩坑模式）、PENDING-SKILLS（需求积压）和SYSTEM-BLUEPRINT（体系蓝图），主动分析Skill体系的演进方向——哪些Skill应该新建、哪些应该合并/拆分、哪些描述需要重写、哪些触发词需要调整、整体编排架构是否需要升级。对应产品侧的 product-evolution-planner。触发词：「Skill体系怎么演进」「Skill体系应该怎么完善」「有没有新的Skill需要建」「Skill体系演进建议」「主动分析Skill体系」「Skill体系下一步」。
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of an Environmental Restoration Planner — screening or comparing CERCLA/RCRA remedial alternatives against the nine evaluation criteria, building a life-cycle cost estimate for a Feasibility Study, scoping a stream or wetland restoration design against a reference reach, sizing compensatory mitigation credits, drafting a Statement of Work or Remedial Action Work Plan, or scoping a Five-Year Review for a site with land-use controls in place.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Business Continuity Planner — running a business impact analysis (BIA) to derive recovery time objectives, mapping process dependencies to find single points of failure, evaluating whether current recovery capability meets a process's maximum tolerable downtime, designing or debriefing a tabletop exercise, or building the cost-benefit case for a continuity investment.
日本語の概要は準備中です。原文の説明を表示しています。
Authoring and managing Agentforce agent definitions using the declarative Agent Script DSL (.agent files) and associated metadata types, including the Agent Script language for the new Agentforce Builder (hybrid-reasoning -> logic vs | prompt instructions, @actions/@subagent/@variables references, subagents). Use when creating agents in source control, writing or debugging Agent Script, debugging agent metadata, or understanding the metadata lifecycle of GenAiPlugin/GenAiPlanner/BotVersion types. Triggers: 'how do I deploy an Agentforce agent using source control', 'convert an agent topic to a subagent', 'what metadata types make up an Agentforce agent', 'agent test run command failing in CI pipeline', 'GenAiPlugin vs GenAiPlanner metadata relationship', 'Agent Script logic vs prompt instructions'. NOT for Apex-based agent actions — use agentforce/custom-agent-actions-apex. NOT for clicking the agent together in the Builder UI — use agentforce/agentforce-agent-creation.
日本語の概要は準備中です。原文の説明を表示しています。
Split a dirty working tree into single-concern Conventional Commits. The deterministic inventory.mjs helper groups dirty paths by concern (docs, source + paired test, config, governance); main context refines the grouping and presents a commit plan. Read-only until the user approves the plan — it never stages, never commits, never touches consent paths. Disjoint from the commit skill (Phase 11 executor): the planner proposes a split; the executor lands one consented commit. Use when a working tree has accumulated heterogeneous changes that should not land as one commit.
日本語の概要は準備中です。原文の説明を表示しています。
Propose the next dependency-ready sprint from the ALREADY-DECOMPOSED roadmap — standup's active sibling. Reads docs/roadmap-execution-plan.md + the memory backlog, computes per-task readiness from the roadmap's machine-readable status, orders with roadmap-planner's graph engine, and emits a proposed task-set (sprint-plan manifest shape) with per-feature done-criteria, excluding unready tasks and naming their unmet prerequisite. PROPOSES ONLY — the human confirms/edits before /triage routes it (typically to the `power` track). Distinct from `sprint-plan`, which decomposes a fresh vision.
日本語の概要は準備中です。原文の説明を表示しています。
harness-creator / plugin-dev-planner への引き渡しモードを判定したいとき、summary.json から A/B/C/D/E/P のいずれかを決定論的に確定したいときに使う。
dev-graph artifact を正規 path へ atomic 追加・差分更新したいとき、system-dev-planner の exact 13 phase task package を all-or-none 登録したいときに使う。
大きな自然文構想を feature・architecture・機能間依存へマクロ分解したいとき、ready feature の system-dev-planner package を atomic 登録・binding 別投影したいときに使う。
Use when the user asks to "keep the launch momentum going after launch week", "plan a changelog / release-notes cadence as GTM", or "is this update worth a relaunch"; produces a T+1→T+30 momentum plan — a launch-moment calendar (milestone / shipped-loop / badge moments only), announcement-tier routing (major = full-channel, medium = targeted, minor = changelog-only), a relaunch legitimacy call, spike-to-owned handoff briefs, and the next Tier-1 moment with launch-stacking spacing. Not for the 30-day content-reuse map or paid amplification execution — use content-amplifier; not for planning the next launch end to end — use launch-tier-planner. 抗第二周断崖/changelog-as-GTM/relaunch/下一发布时刻
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to "plan an influencer campaign", "build a campaign blueprint", or "launch a product with creators"; produces campaign objectives, platform and influencer-tier strategy, content requirements, a phased timeline, budget allocation, and KPI targets. Not for writing individual creator briefs — use brief-generator; not for the overall product-launch plan (tiering, calendar, press, community day) — use launch-tier-planner, which hands this skill the creator lane. A launch request that does not mention creators routes to the launch discipline, not here. 达人营销策划/种草方案
日本語の概要は準備中です。原文の説明を表示しています。