「plan」の検索結果

Develop business continuity plans and impact analysis. Implement BCP testing and communication procedures. Use when building organizational resilience.

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

Implement disaster recovery strategies and runbooks. Configure RPO/RTO targets and failover procedures. Use when planning for business continuity.

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

Plan, build and quality-check a premium short commercial for a real business (roofing, property, ecommerce, B2B software) using AI-generated footage, code-built motion (HTML/GSAP), selective Three.js and an independent-critic "Gauntlet" loop. Use when asked to make a launch-style / SaaS-style video, business ad, explainer, sample reel or pitch video, or to review and improve one. Encodes motion principles distilled from 28 professional launch films, a quality bar, audio rules and a business-offer playbook.

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

Adversarial senior review of the spec before any code is written. Constructs a skeptical reviewer whose authority comes from the codebase, §R research, and live best-practice — then tries to REFUTE the spec, not rubber-stamp it. Every finding cites evidence (file:line or source); unverifiable ones are flagged. Survivors harden §V; the run ends in an explicit go / no-go gate. Triggers before building anything high-blast-radius, when the user says "review the spec", "red-team this", "is this plan sound", "senior review", or invokes /ck:review.

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

Calibrated interrogation of a fuzzy idea before it becomes a spec. Asks one question at a time, recommends an answer, and lands each answer in §G (goal) or §C (constraints) — unknowns parked as `?` items, never guessed. The cheapest place to kill a bad idea is before §T exists. Triggers when the user has a vague idea, says "grill me", "stress-test this", "challenge my plan", "interview me before I spec", or invokes /ck:grill. Defers the actual write to the spec skill.

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

Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.

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

Generate the post-EXECUTE closeout packet for a plan or phase. Includes archive-readiness classification, drift signal scoring, commit checkpoint recommendation, and move-on next-state recommendation.

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

Apply step-by-step analysis for complex problems with revision capability. Use for multi-step reasoning, hypothesis verification, adaptive planning, problem decomposition, course correction.

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

Create or update a product-discovery SPEC (requirements doc) for user review. Use when turning RESEARCH findings plus user intent into a reviewable requirements artifact before INNOVATE/PLAN.

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

Documentation and extension workflows derived from local slash commands (docs, explanation, issues, prototypes, tutorials, MCP design review).

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

Author or revise a cloud-api-operations recipe (config/source/skills/cloud-api-operations/references/recipes/). Encodes why the long tail of control-plane capabilities is deliberately NOT wrapped as MCP/CLI tools, the API-first admission test for whether a capability deserves a recipe, the negative and positive lists, the fixed recipe structure, the writing rules distilled from writing-for-agents, the user-facing copy red lines, and the product regeneration/verification pipeline. Also routes contributors (and their agents) to the contribution flow and the pre-PR self-test protocol in references/contributing.md. Use when adding a recipe, judging whether a scenario belongs in the recipe set, updating the recipes index, re-checking existing recipes against the admission test, or onboarding someone who wants to submit one.

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

Use when medium-to-large changes need explicit requirements, technical design, and task planning before implementation, especially for multi-module work, unclear acceptance criteria, or architecture-heavy requests.

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

Code learning and audit framework. Analyze any codebase — new, legacy, or AI-generated — and produce educational explanations or architectural audits. Use when the user wants to understand WHAT and WHY behind any code, not just accept it.

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

Understand this repository quickly before making changes. Use for architecture discovery, ownership mapping, command selection, and initial implementation planning.

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

Discover when you are most active and most productive with Claude Code by bucketing sessions and events into hour-of-day and day-of-week bins from their timestamps, then flagging peak versus low-output windows. Uses the session list, per-session events, and analytics daily trends. Use when planning a schedule or deciding when to do deep work versus lighter tasks.

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

Compile a month-over-month retrospective from Agent Monitor data — sessions, cost, token volumes, completion rate, top projects by working directory, and notable shifts versus the prior month. Uses daily_sessions/daily_events (365d) from analytics, the session list, and the pricing cost breakdown. Use when doing a monthly retrospective or planning the month ahead.

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

Break down Claude Code costs using the Agent Monitor pricing engine. Shows per-model costs (input, output, cache_read, cache_write at $/Mtok rates), per-session costs, daily trends, and compaction baseline token recovery. Use when analyzing spending, comparing model costs, or planning budgets.

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

Suggest concrete optimizations for Claude Code usage based on historical session data. Covers cost reduction, speed improvement, error prevention, and workflow efficiency. Use for data-driven optimization planning.

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

Review a business plan from the perspective of the named target customer. Asks: would they actually pay this price for this solution today? Outputs a verdict with one of four modes — PAY NOW / PAY WITH FRICTION / WOULDN'T PAY / WRONG ICP. Use when the user has a defined ICP and pricing and wants to stress-test whether the value prop survives contact with reality. Triggered by: 'customer review', 'would they pay', 'pricing reality check', '客户视角', '会付费吗'.

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

Review a business plan from the perspective of a hostile devil's advocate. Asks: what kills this in month 6? What's everyone politely not mentioning? Outputs a verdict — EXISTENTIAL RISK / SOLVABLE RISKS / LOW-RISK / WRONG QUESTION. Use after the investor/customer/operator reviews are done, as the final gauntlet before committing real time and money. Triggered by: 'skeptic review', 'devil's advocate', 'what would kill this', 'red team this', '泼冷水', '杀手在哪'.

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

Use when video content needs to be extracted as text: pasted YouTube links or IDs, requests to transcribe, summarize, quote, translate, convert video to text, or extract information from video content. Also use when a user shares a video URL without explanation and wants to know what it says. Not for uploads or account management.

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

Orchestrate iOS screenshot automation with xcodebuild/simctl for build-run, AXe for UI actions, JSON settings and plan files, Koubou-based framing (`asc screenshots frame`), and screenshot upload (`asc screenshots upload`). Use when users ask for automated screenshot capture, AXe-driven simulator flows, frame composition, or screenshot-to-upload pipelines.

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

Turn books, PDFs, slides, documents, web pages and text into a source-grounded knowledge base, interactive learning HTML and Markdown in English or Chinese. Use for learning, summaries, explanations, review, quizzes, relationship maps, saving reusable methodology files, retrieving or comparing accumulated methods, and applying them to a real problem. 将材料转为可追溯知识库与交互学习页，支持中英文、关系图、方法论保存/检索/比较及应用；区分材料依据、推断与外部核验。

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

Use when explicitly asked to run a live or plan-only application test for a published Scenario skill.

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