「plan」の検索結果

Independently assess an RPI plan without editing it. Use when an implementation-ready plan needs a credibility check or a revised plan needs its earlier findings reconciled.

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

Plan a Chinese company's entry into an overseas market (出海): choose the market with evidence, then plan entity, payments, localisation, compliance, channels and team for the first twelve months. Use when asked 出海计划, 我们要进入东南亚 / 中东 / 欧洲 / 美国市场, how should a Chinese company expand overseas, or a go-global plan. Produces a market scorecard, a twelve-month entry plan by workstream, the compliance and data checklist for the chosen market, and the top risks with mitigations. Bilingual output on request.

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

Produce a capacity planning document for a service covering traffic forecasts, resource requirements, and scaling strategy. Use when asked to plan infrastructure capacity, forecast resource needs, model traffic growth, define scaling strategy, or produce a capacity review for a service. Produces a structured capacity plan covering current baseline metrics, growth projections, resource requirements per tier, scaling strategy, cost projections, capacity triggers, and an infrastructure action roadmap.

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

Build a tiered classroom behavior intervention plan (BIP) for a K-12 student, grounded in the function of the behavior. Use when asked to plan a behavior intervention, address a disruptive or off-task pattern, write a BIP, or set up positive behavior supports. Produces a function hypothesis, prevention/antecedent strategies, teaching of a replacement behavior, a response plan for when it happens, and a simple data-tracking method — positive and skill-building, not punitive.

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

Plan tests for an API endpoint or service — functional, negative, and contract. Use when asked to test an API, write API test cases, plan REST/GraphQL endpoint testing, or validate an API contract. Produces an API test plan — per-endpoint cases (status codes, schema, auth, validation, errors), boundary/negative cases, contract checks, and non-functional notes — so the API is verified beyond the happy 200.

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

Systematic strategic planning framework for philosophy and interdisciplinary academic papers targeting preprint platforms (PhilArchive, arXiv, PhilSci-Archive). Use when users want to: (1) plan a paper on a specific topic, (2) identify research gaps and assess originality, (3) develop optimized paper outlines, (4) prepare for preprint submission, or (5) understand platform requirements and writing standards. Triggered by phrases like 'plan a paper on,' 'help me design a paper about,' 'identify research gaps in,' 'is this idea original,' or when users need structured research planning. The skill guides through three phases: Platform Analysis (identifying target venue and studying sample papers), Theoretical Framework (AI-driven literature search and gap identification), and Outline Optimization (structured design with reviewer-perspective self-assessment). Each phase includes quality evaluation standards and validation checkpoints. Output: optimized detailed outline ready for systematic writing (use with academic-paper-composer skill).

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

When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).

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

Strategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap. Use when user says "SEO plan", "SEO strategy", "SEO planning", "content strategy", "keyword strategy", "content calendar", "site architecture", or "SEO roadmap".

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

Trigger when: (1) User wants to create an educational/explainer video, (2) User has a vague concept they want visualized, (3) User mentions "3b1b style" or "explain like 3Blue1Brown", (4) User wants to plan a Manim video or animation sequence, (5) User asks to "compose" or "plan" a math/science visualization. Transforms vague video ideas into detailed scene-by-scene plans (scenes.md). Conducts research, asks clarifying questions about audience/scope/focus, and outputs comprehensive scene specifications ready for implementation with ManimCE or ManimGL. Use this BEFORE writing any Manim code. This skill plans the video; use manimce-best-practices or manimgl-best-practices for implementation.

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

Plan manipulator motion and generate trajectories in MATLAB. Use when the task involves moving a robot arm between configurations or poses — whether the user says "trajectory," "motion," "path," "move from A to B," or "plan." This skill applies regardless of whether the user explicitly mentions collisions or obstacles; if geometry exists in the workspace, collision safety is implicit. Triggers on: manipulatorRRT, manipulatorCHOMP, dlCHOMP, contopptraj, trapveltraj, collision-free path, motion planner, RRT, CHOMP, TOPPRA, path shortening, obstacle avoidance for manipulators, time-optimal trajectory, velocity limits, acceleration limits, occupancyMap3D, meshtsdf, collision objects as environment, trajectory between waypoints, joint interpolation, move between poses, constant velocity, trapezoidal profile, feed rate. Also triggers when a user has IK solutions or waypoints and needs to connect them — whether for time-optimal motion, constant-speed welding/cutting, or any other trajectory parameterization.

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

Discover related plans for the current task: same feature folder full depth, other features active-only, general-plans active. Like vc-context-discovery but for plan artifacts.

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

Create comprehensive business strategy with premise deconstruction, business model stress test, pricing, go-to-market plan, and competitive positioning. Runs a 4-layer premise audit before strategy, then generates a full market research report with SWOT, 4P, 10-point business model validation, and constraint analysis. Use when the user has an idea and needs a strategic plan, competitive analysis, pricing strategy, GTM plan, or says 'business plan', 'strategy', 'pricing', 'go-to-market', or 'competitive analysis'.

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

Orchestrate a configurable, multi-member CLI planning council (Codex, Claude Code, Gemini, OpenCode, or custom) to produce independent implementation plans, anonymize and randomize them, then judge and merge into one final plan. Use when you need a robust, bias-resistant planning workflow, structured JSON outputs, retries, and failure handling across multiple CLI agents.

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

Plan the MVP build from a PRD and an MVP scope, as a full development plan or an ultra-lean build spec, with the AI Product Development Toolkit's planning prompts.

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

Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align content production with broader brand and SEO goals. Triggers on content strategy, content plan, editorial strategy, content pillars, content calendar, editorial calendar, topical authority, topic clusters, content governance, content roadmap, content production. Also triggers when the user is about to start producing content without a strategic plan.

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

Discovers user intent and generates a structured, step-by-step plan for model customization workflows. This skill must always be activated alongside any other skill when the user's request relates to model customization — including fine-tuning, training, building, customizing, reviewing data, or getting advice on approach, regardless of domain. Do not skip this skill even if the immediate ask is narrow (e.g., reviewing data format or a single workflow step), because planning discovers the full scope of work needed. Also activate when the user wants to resume, continue, or modify an existing plan.

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

Redesign a blocked topic sequence into an interleaved plan with mixed practice across related topics. Use when planning units, homework schedules, or revision programmes.

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

Strategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap. Use when user says "SEO plan", "SEO strategy", "SEO planning", "SEO best practices for <topic>", "content strategy", "keyword strategy", "content calendar", "site architecture", "SEO roadmap", or asks for organic growth guidance without a specific URL.

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

Plans new macOS apps or analyzes existing projects. Creates comprehensive planning documents covering architecture, features, UI/UX, and tech stack. Use when planning a new macOS app or auditing an existing one.

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

Guides you through comprehensive iOS/Swift app planning and analysis. Use for new apps (concept to architecture) or existing apps (audit current state, plan improvements, evaluate tech stack). Covers product planning, technical decisions, UI/UX design, and distribution strategy.

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

Use when the user wants to run a full ad-campaign pipeline on top of Higgsfield Marketing Studio — 'create a campaign', 'build a content plan', 'run the content pipeline', 'generate 100 UGC videos', 'plan and schedule a launch', 'make a batch of ads from my product', or 'how much did this save vs traditional production'. Covers the 5-stage orchestration (Research → Plan → Generate → Publish → Report), the UGC-first 5-format campaign mix (UGC Entertainment, Street Interview, Unboxing, Product Review, ASMR), the even-split allocation math, button-driven onboarding, the per-batch generation gate, and the publish + cost-report tail (satellite). Defers all Marketing Studio API ground-truth (presets, params, hooks, avatars) to higgsfield-marketing-studio.

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

Create a 30-day social media content calendar for affiliate marketing. Triggers on: "create a social media calendar", "30-day content plan", "social media schedule", "content calendar for [product]", "plan my social posts", "social media strategy", "schedule my affiliate posts", "content plan for LinkedIn", "30 days of content", "social posting schedule", "what should I post this month", "write my social content", "create posts for LinkedIn X Facebook", "affiliate content calendar", "social media plan for my affiliate program".

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

Dung khi can lap ke hoach chi tieu quang cao cho mot ky — tinh nguoc tu doanh thu, phan bo theo kenh va tang pheu, ty le testing 30 scale 50 retarget 15 lookalike 5, va timeline ramp-up. Kich hoat khi user nhac 'media plan', 'plan ads thang toi', 'phan bo ngan sach quang cao', 'chay bao nhieu tien', 'chia budget cho kenh nao', 'ke hoach chay ads'. Khong dung cho — phan bo ngan sach marketing tong the ngoai ads thi dung skill 61-budget-planning; tinh CPL toi da thi dung skill 10-tinh-kpi-nguoc.

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

Dung khi da co ket qua audit va can lap plan content ky sau TU DATA chu khong doan — ty le 70 giu winner, 20 toi uu bien the, 10 thu nghiem moi, toi da 2 gia thuyet moi mot ky. Kich hoat khi user nhac 'next content plan', 'plan thang toi', 'content ky sau lam gi', 'dua vao data lap ke hoach', 'thang sau viet gi'. Khong dung cho — audit de biet cai gi work thi chay skill 39-content-audit truoc; xep lich dang theo ngay thi dung skill 01-lich-noi-dung.

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