「planning」の検索結果

Use when an ad account needs a systematic CONFIGURATION audit — 84 checkpoints across account, campaign, ad set, ad, tracking, and optimization, scored into a Health Score out of 100, quick wins ranked by impact, regional benchmarks, and a dropshipping checklist, covering Meta, Google, and TikTok. Trigger on 'ads audit', 'audit my ad account', 'is my Meta setup correct', 'health score for the account', 'review my Google Ads', 'we inherited this account and it is a mess'. Not for — diagnosing why the numbers moved this week, see `03-performance-eval-global`; planning fresh budget, see `54-media-plan-global`; rebuilding the campaign hierarchy, see `52-account-structure-global`.

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

Use when a LIVE campaign needs a new asset the same day — creative fatigue, CTR decay, climbing frequency, or a new angle to test: stripped-down input, duplicate the winning creative and change only what is listed, a one-page template, and a hard SLA so the designer ships in 2-4 hours. Trigger on 'quick brief', 'need an asset fast', 'creative fatigue', 'swap the creative today', 'frequency is too high', 'the ad is dying and we need a new one'. Not for — planning assets before launch, see `41-campaign-asset-list-global`; a full concept brief with time to spare, see `42-image-brief-global`; resizing an existing master, see `50-asset-resize-global`; raising budget on a winner, see `55-scaling-ads-global`.

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

Use when a PAID MEDIA plan is needed — work backward from revenue to max CPA and required budget, split spend across channels, funnel stages, and campaign types, build a ramp-up timeline, set KPI targets per channel, and prepare a contingency plan. Trigger on 'media plan', 'paid media budget', 'how much should I spend on ads', 'channel mix for the campaign', 'plan the ad budget', 'we have 10k a month and no plan'. Also use when a budget number exists and nobody has decided where it goes. Not for — the pure revenue-to-budget math, see `10-reverse-kpi-global`; the whole marketing budget including non-paid, see `61-budget-planning-global`; the next period plan built from results, see `57-next-ads-plan-global`.

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

Break a plan, spec, or conversation into dependency-aware, independently verifiable tickets. Use explicitly when the user wants work sliced for local planning or an issue tracker.

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

Explores codebase structure, affected files, blast radius, related tests, and local conventions for a focused topic. Use when review or planning needs structural lookup without bloating main context.

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

PTES-aligned penetration testing methodology for backend, frontend, and mobile. Provides attack taxonomy, exploit techniques per vulnerability class, and platform-specific test matrices. Use when executing pentest workflow, planning security assessments, mapping attack surfaces, or building threat models.

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

Execute multi-task implementation plans by dispatching a fresh implementer subagent per task with independent review gates. Use when implementing plans, executing multi-task PRs, or transitioning from planning to implementation.

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

Validates cyber exercise authorization, scope, exclusions, runtime controls, expiry, stop and restart gates. Use when planning or reviewing authorized security activity, scope drift, or unsupported execution environments.

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

Scores a coding task on Spread, Novelty, and Centrality (SNC 0-6) and maps the tier to autonomy, verification depth, review mode, reviewers, model tier. Use when sizing a fix or feature before planning, choosing fast vs deep review, or deciding whether HARD STOP approval is required.

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

Drafts bounded cybersecurity engagement plans with objectives, scope, exclusions, roles, authorization, runtime controls, evidence, stop criteria, and restart gates. Use when preparing an exercise or assessment plan before execution.

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

End-to-end academic paper writing workflow. Takes a research repository and produces a publication-ready LaTeX manuscript for top ML/AI conferences (NeurIPS, ICML, ICLR, ACL, AAAI, COLM). Covers repo understanding, structure planning, section drafting, citation management, anti-AI polishing, and conference formatting. Triggers on "write paper", "draft paper", "scholar writing", "paper writing workflow".

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

Research ideation workflow from literature search to research planning. Triggers on "brainstorm research ideas", "identify research gaps", "conduct gap analysis", "start research project", "conduct literature review", "define research question", "select research method", "plan research", "research ideation".

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

Implement small Phoenix changes without planning — add validations; Use for single-file edits under 50 lines.

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

Use when debugging how a value or request reaches Elixir code, finding who calls a function, or planning a signature…

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

Implement small Phoenix changes without planning — add validations, update routes, fix components, create migrations. Use for single-file edits under 50 lines.

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

Use when debugging how a value or request reaches Elixir code, finding who calls a function, or planning a signature change. Builds the call tree with mix xref callers instead of reading files one by one.

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

Implement small Phoenix changes without planning — add validations, update routes, fix components, create migrations. Use for single-file edits under 50 lines.

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

Use when debugging how a value or request reaches Elixir code, finding who calls a function, or planning a signature change. Builds the call tree with mix xref callers instead of reading files one by one.

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

Deliver a large, cross-domain Phoenix feature or complete end-to-end system through planning, implementation, verification, and review. Use when several coordinated workflows or contexts must ship together. NOT for an existing plan; use /phx:work.

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

Creates a lesson plan, student-facing materials, and observation template. Load this skill BEFORE asking the teacher any clarifying question about grade, subject, topic, standard, or timing. Use when a K-12 teacher needs a math, ELA, science, or social studies lesson built from scratch — even if grade, subject, or topic isn't yet stated. Do NOT load for grading, a rubric, assessment feedback, a quiz, or a standards lookup — answer those directly. Triggers on explicit requests (lesson plan, mini-lesson, unit plan, daily plan) and implicit teacher intent: "I'm teaching long division to 5th graders," "need to teach photosynthesis tomorrow." Core signal: teacher needs new instructional content created. A new lesson that asks for differentiated, tiered, or leveled materials is still ONE planning request — this skill produces those materials inside the lesson package; do not also invoke k12-lesson-differentiation. Not for differentiating an existing lesson (use k12-lesson-differentiation) or passage rewrites.

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

Tracks and manages album ideas including brainstorming, planning, and status updates. Use when the user wants to add, review, or organize their album idea backlog.

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

Creates visual concepts for album artwork and generates AI art prompts. Use during planning for concept discussion, or after all tracks are Final for actual artwork generation.

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

Output rules for all agents - concise, scannable, actionable. Based on Matt Pocock's planning principles.

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

用于 Workflow Planning 阶段的占位算子。当前 Skill 库不存在满足用户需求的业务 Skill 时，使用本算子保持 DAG 数据流完整，等待后续生成真实 Skill 后替换。

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